automazione wrote:Sorry Bob but.. quite dangerous and confusing if Servoy allows to modify more than one release.
Agreed that a release is a release and by definition needs to be locked. I apologize for my ignorance with Servoy sso disregard if I'm off base. What I'm referring to here is like a "branch" in a source code control system like CVS or RCS. The idea is that you can continue to make releases in one branch of a "solution", i.e. 1.1, 1.2, etc. while also developing additional branches of the same solution and making releases there like 2.0, 2.1, etc. You can also share code so when you fix a bug in the "1" branch, you can also patch the same code in the "2" branch with little effort making maintenance easier. It's still the same "solution" just different major versions. Anyway, this is complicated stuff and probably not useful for everyone all the time so I'd put it down the priority list in the "nice to have" category.