Hey all
About a year ago a bunch of work to make Wonder Java 7 compatible. But the branch is now 86 commits behind the master branch (Wonder 6).
I propose we:
1) Create a branch at the current head of master called Wonder_6 for 6-specific bug fixes going forward
2) Merge Wonder_7 branch into Master and then delete it.
3) Create the *first* release of Wonder 7 from Master
4) Work through as much of the current pull requests as possible, making sure they work well with Java 7, create a final Wonder_7 release
3) Create Wonder_7 branch for 7-specific bug fixes going forward
5) Use Master for ongoing modern java development until we transition to Wonder_9
If there are features that are added to the more modern branches but you can’t use them because you are limited to Java 6 or 7, then you will be allowed to create pull requests to bring those commits to older branches the the work to do so would be on the developer wanting the back-porting. Not on the original developer.
What does everyone say?
Dave
—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™
—————————————————————————————
David Avendasora
Senior Software Abuser
Nekesto, Inc.
Mit freundlichem Gruß,
René Bock
Software Engineering
--
salient doremus
salient GmbH
Kontorhaus - Lindleystraße 12
60314 Frankfurt Main
Fon +49 (0)69 - 650096 -0, Durchwahl: - 18, Fax: -70
http://www.salient.dehttp://www.doremus.com
http://www.openforms.de
Geschäftsführer: Peter Biler, Alexander Gerling, Lars Ohlerich
Amtsgericht Frankfurt Main, HRB 48693
// Neuer Schwung auf allen Endgeräten für den Automobilclub von Deutschland:
http://www.avd.de/