---
title: "Comment by Lukasz Wasylow on \"Part 5: SQLcl Project (It will forever change your Database & APEX deployments)\" | Hashnode"
description: "Hi How do you manage versions in multi developer environment? So two or more people working in different branches on different features?"
url: "https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939"
---

[Discussion](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17)

Comment [Part 5: SQLcl Project (It will forever change your Database & APEX deployments)](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17)

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939)

Hi How do you manage versions in multi developer environment? So two or more people working in different branches on different features?

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-67583c322074d7fb5ce4d2a3)

I recommend watching this office hours video: [youtube.com/watch](https://www.youtube.com/watch?v=EM3_2Dd3LOs.Guys) from Oracle show examples of when 2 developers are working on different tickets in the same environment.

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-675853bf8fa794a00bc03a3a)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) Thank you, I did have a watch. One thing I'm still unsure is that on demo they working on main which often is protected so running `project release` is hard. However running that in branch does not allow multiple developers working together as each branch would essentially cut its own release and hence my question about managing this. Or did I misunderstood the process and missing something? Thanks in advance.

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-67588771c3451339a7a2cc59)

[Lukasz Wasylow](https://hashnode.com/@baalowy) If you will "project export", then indeed, you will export everything. So a solution would be e.g.:

1.  Developer 1 is working on some changes in the database, and periodically, he exports only his changes to a branch, let's say branch "feature1."
2.  Developer2 is working on his changes on the "feature2" branch and exports his changes.

"project export -o OBJECT\_NAME"

At the end, their changes are merged:

-   feature1 into e.g. branch "version\_2.0"
-   feature1 into branch "version\_2.0"

Then, the privileged user lets call him Release Guy execute the "project stage" command, then "project release" etc.

Does it answer your question? :)

[Lukasz Wasylow](https://hashnode.com/@baalowy)

[Dec 10, 2024](https://hashnode.com/posts/part5-sqlcl-project-it-will-forever-change-your-database-apex-deployments/67481c0939d14a483db14f17/comment/67582c6dfdc4fe065968f939#reply-67588e6c85550d72d611b478)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) It does, yes thank you :) Indeed it seem doable with a sort of git flow approach. Trunk based seems more complex. But I will try it out, looking for alternatives for flyway and this looked promising. Again thank you for the help and your time, much appreciated 🙏
