23 Sep
2011
23 Sep
'11
3:36 p.m.
On Sep 23, 2011, at 3:27 PM, Sergiu Dumitriu wrote:
On 09/23/2011 04:10 AM, Vincent Massol wrote:
My only problem with that is that I don't like too much to leave some "unfinished
release" (the last release we did was 1.2RC1). Maybe it doesn't matter…
Thanks
-Vincent
Hi devs,
Fabio and Eddy are working on merging Jun's GSOC code in master for XEclipse and are
preparing for a release (could you send us a proposal guys?).
It seems that the last release of XEclipse was 1.2RC1 so it's a bit of a shitty
situation since normally so much change would have warranted a 1.3 release.
However I'm proposing that the next release be 1.2RC2 and when we've tested it
enough we then quickly release 1.2 final to get it over with.
The alternative is to:
- get the 1.2RC1 tag
- release it again as 1.2 final
- consider all Jun's changes to be 1.3M1
However that solution has 2 issues:
- it's more time consuming
- we're not 100% sure that the last 1.2RC1's quality was good enough to be named
1.2 final
WDYT?
My preferences goes to having Jun's code be in a 1.2RC2 release.
I wonder if the changes are big enough to warrant a 2.0 release instead.
I'd be in favor of releasing 2.0 RC1.