We should go for 8, doing a API break is hard enough to skip one and the new feature are really useful.
I also think the Java 8 will be supported for a long time because 9 will break many old things. Also, I strongly suggest to remove all methods with more than 3 parameters whenever it is possible when rewriting modules or methods cluster to use builder pattern. Samuel > Le 2015-05-01 à 09:20, David Avendasora <[email protected]> a écrit : > > Okay, since Java 7 is officially dead as of today, should we just jump > directly to Java 8? > > I’m fine with freezing Wonder 6 (feature-wise) as-is and making the current > Wonder 7 branch target Java 8. > > Any reason we *shouldn’t* do that? > > We can still do additional bug-fix releases of Wonder-6 for the next year or > so, but all new features and development go into Wonder 8. > > With that in mind, how about this for a plan: > > 3) Create new Wonder_6 branch from Wonder 6.1.3 release > 3) Merge Wonder_7 branch into master > 3) Make Wonder_7 Jenkins job build master branch, targeting Java 8 > 3) Process all the current pull requests into master to be included in > Wonder_7, only critical bug fixes will be merged into Wonder_6 > > To be clear, Wonder_7 isn’t *only* about targeting Java 8, it’s also removes > a lot of deprecated code and fixes long-standing bugs. **IT WILL BREAK > APPS**. The focus for Wonder 7 is to move forward. Backward compatibility > will be considered but it will not *automatically* have a higher priority > than fixing bugs. > > If we do this, Wonder_6 will be the stable branch. 6.1.3 will be the “stable” > release. > > Dave > > P.S. > I know I’m jumping in here. I’m not on the WOCommunity Board, and I don’t > want to be stepping on their toes, or on the toes of committers that have > been trying to push things forward over the past couple years. I *really* > appreciate all the hard work that has been put in by everyone and we wouldn’t > be even a shadow of the phenomenal community that we are without them! > > Right now, stagnation is our enemy. I laughed out loud at Chuck’s earlier > statement: "He was just indicating that it was an appropriate time for Wonder > to be updated for Java 7!” because it’s so true! However, I want to laugh > just as hard at the total absurdity of him saying: “Getting Wonder to Java 8 > couldn’t have been that hard. Dave Avendasora did it!” at WOWODC next year! > > >> On Apr 30, 2015, at 7:59 PM, Ramsey Gurley <[email protected] >> <mailto:[email protected]>> wrote: >> >> Sounds good to me. What is the ETA on step 3? ;-) Er, merging Wonder_7? >> >> On Apr 29, 2015, at 7:44 AM, David Avendasora <[email protected] >> <mailto:[email protected]>> wrote: >> >>> 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. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected] >>> <mailto:[email protected]>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >>> >>> <https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com> >>> >>> This email sent to [email protected] <mailto:[email protected]> > > ————————————————————————————— > WebObjects - so easy that even Dave Avendasora can do it!™ > ————————————————————————————— > David Avendasora > Senior Software Abuser > Nekesto, Inc. > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
