+1 It makes sense.
2012/7/20 Mickael Istria <mist...@redhat.com> > Hi all, > > So it is now clear that there are some issues with Eclipse 4.2: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=385527 > Some patches were already contributed ( > https://bugs.eclipse.org/bugs/show_bug.cgi?id=381683#c2 ) but it seems > like some of them break compatibility with 3.x stream. I am a bit > pessimistic with the ability to support both 3.x and 4.2 at the same time > (I'd be glad if someone could convince me of the contrary). > What about dropping support for 3.x starting from the next version > (currently 2.0.6, but we should probably change that to 2.1.0 to highlight > the breakage). So people using 3.x platform could still use 2.0.5, whereas > people using Eclipse 4.2 would use 2.1.0. > We can also think, if necessary, of publishing a 2.0.6 versions compliant > with 3.x in case of critical fix or major improvement that make us feel > this deserves a build for 3.x too. > > What do you think? > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> > My blog <http://mickaelistria.wordpress.com> - My > Tweets<http://twitter.com/mickaelistria> > > _______________________________________________ > swtbot-dev mailing list > swtbot-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/swtbot-dev > >
_______________________________________________ swtbot-dev mailing list swtbot-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/swtbot-dev
