Maintaning complex solutions

Classic Servoy
1

Hello,

I would like to discuss the following scenario and wonder if anyone has a bright idea. We have a solution up and running at customers’ sites. Once in a while something has to be fixed in the solution they use. On the other side, major new features etc. have to be developed, but not yet deployed.

The question is: what do you believe is the best setup? Just making a new release will not be good enough, since I have to fix bugs but cannot deliver the current (the devlopment) release.

Any ideas/experiences anyone?

Thanks
Patrick

2

Here’s a couple of things that I do:

  1. Use modules. This greatly simplifies things as you can fix “bugs” in the core functionality without affecting everything else.

  2. Make customizations using modules. Once you have a core module running - and a customer wants a modification - I will make those mods in a module.

  3. When starting revisions on released products (or modules) - I start with a new Servoy solution (export existing → import as a new name). That way I have a “frozen” build of the released product - but can continue my development on the “next” version.

Hope this helps.

3

Hi Patrick,

Good tips from Mr Cusick - bless his cotton socks !

I make some assumptions based upon wording in your post…however, if it is true that the fixes on the current system really are a ‘once in a while’ minor changes then is it feasible that you can:
1- Export the current solution
2- Import this second solution under a new name to be hosted in parallel with the original solution
3- Continue to develop and test the new solution online
4- Apply the minor amends to the current solution and mirror these amends in the new solution

Or one more thought which may or may not float !?..
Having exported the current solution and imported as a new solution could you change these two solutions into modules and then create a host solution which would have both old and new solutions as modules within it and use this host solution to control secure access to either solution based upon whether they need to work real time in the current solution module or do beta testing in the new solution module

Just some brainstorming on a very warm evening - hope it helps

Cheers
Harry

4

Hello guys,

thanks for your answers. As far as modules are concerned, I think I am already “Mr. Modules”.

Basically, I wondered if there was a better way than

Apply the minor amends to the current solution and mirror these amends in the new solution

because, that in clear text, means: do it twice.

I don’t know if this could be thought of: modifiying an old release. Let’s say my productive system is release #5 and I am doing my “reasearch” on release #6. If I could do my minor changes in #5, I’d be fine. I don’t know, however, if the architecture of versioning could allow that…

Thanks
Patrick