[Netrexx-develop] Project way of working for NetRexx 5

[René J. <rvj...@xs...>]

As we now have a number of people possibly working on more or less breaking changes (hopefully only when they are in flight), I am personally going to start bundling my changes in feature branches; this is much easier and faster in git than it ever was in subversion and/or cvs, and it will shield us a bit against having changes ‘open’ for too long - or me spending whole nights because I broke something and wanting to fix it before you, the other developers, woke up. Which I did recently when breaking the whole thing by having Java 17 JVM classes dependent on a new ANT task that did not work - and then needing to fall back to Java 8 where the compiler did not work - long live git but I did not need the stress.

This does not mean you also have to, I am only am suggesting it. If you feature branch and rebase with master now and then (better: quite often), merging will be almost painless. This has not become more important than the cooperation on the code itself, you are free to keep committing to master; only be aware that it, from NetRexx 5 on, is not the standard or preferred way of working anymore. Of course your code contributions are more appreciated than any commit/merge procedure. When observed, however, we might have more stability for working on separate issues.

Best regards,

René.