RC1/1.0 release and strategy going forward
Hi, I'd like to propose the following: * Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot). WDYT? Thanks -Vincent
On 4/6/07, Vincent Massol <[email protected]> wrote:
Hi,
I'd like to propose the following:
* Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot).
1. How about the 2.0 branch? 2. I think the 1.0 branch should be preserved after 1.1, but providing only CRITICAL updates. 3. We definitely don't want a distinct branch for 1.1, as the experience with 1.0 proved that it can create only problems. We don't have enough developers to work on two-three branches. WDYT?
Thanks -Vincent
Sergiu -- http://purl.org/net/sergiu
On Apr 6, 2007, at 3:32 PM, Sergiu Dumitriu wrote:
On 4/6/07, Vincent Massol <[email protected]> wrote: Hi,
I'd like to propose the following:
* Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot).
1. How about the 2.0 branch?
That's different. Either we do the changes inside the trunk progressively or we do a complete new version from scratch (which I tend to think is the most feasible solution - That'll be the topic of another email :)). In any case if it's done as a complete rewrite it would be done on its branch (actually there's already a 2.0 branch in SVN).
2. I think the 1.0 branch should be preserved after 1.1, but providing only CRITICAL updates.
Possibly. We can always revisit this when the time comes.
3. We definitely don't want a distinct branch for 1.1, as the experience with 1.0 proved that it can create only problems. We don't have enough developers to work on two-three branches.
Right... Thanks -Vincent
To be more precise here are some proposed dates: - 1.0 RC1: 16/Apr/07 - 1.0 final: 23/Apr/07 - 1.0.1: 07/May/07 - 1.1 B1: 21/May/07 - 1.1 final: not defined Please all committers answer on my previous email and this one to ensure we're all on the same page and all agree on the way forward... Thanks -Vincent On Apr 6, 2007, at 3:17 PM, Vincent Massol wrote:
Hi,
I'd like to propose the following:
* Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot).
WDYT?
Thanks -Vincent
I think that it's not nice to plan 1.0.1 so soon... It means that we already know there are bugs, and we're releasing a buggy product anyway. Also, I don't know if we can count on a 1.1 release so soon. We currently lack the power to push things so fast. Remember, only you (Vincent) and Nam are going to work on the core in the next few weeks/months. On 4/6/07, Vincent Massol <[email protected]> wrote:
To be more precise here are some proposed dates:
- 1.0 RC1: 16/Apr/07 - 1.0 final: 23/Apr/07 - 1.0.1: 07/May/07 - 1.1 B1: 21/May/07 - 1.1 final: not defined
Please all committers answer on my previous email and this one to ensure we're all on the same page and all agree on the way forward...
Thanks -Vincent
On Apr 6, 2007, at 3:17 PM, Vincent Massol wrote:
Hi,
I'd like to propose the following:
* Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot).
WDYT?
Thanks -Vincent
Sergiu -- http://purl.org/net/sergiu
On Apr 6, 2007, at 10:07 PM, Sergiu Dumitriu wrote:
I think that it's not nice to plan 1.0.1 so soon... It means that we already know there are bugs, and we're releasing a buggy product anyway.
But we do know of these bugs! They're the ones we won't have time to do for the 1.0 final. I don't see any issue with that and it would certainly be much worse to try to hide bugs... Of course we need to fix all the bugs we consider critical for the 1.0 final but we shouldn't stop it because we still have bugs or we will never release it...
Also, I don't know if we can count on a 1.1 release so soon. We currently lack the power to push things so fast. Remember, only you (Vincent) and Nam are going to work on the core in the next few weeks/months.
WDYM by "so soon"? Do you mean the 3 months timeframe? My POV is that 1.1 doesn't have to be a revolution and if it only boasts, say, 5 new features, it still warrants a release. Thanks -Vincent PS: It's not only Nam and me. It's also everyone submitting patches and potentially all the current committers! :-) I'm also 100% sure we'll get some other new people who'll contribute.
On 4/6/07, Vincent Massol <[email protected]> wrote: To be more precise here are some proposed dates:
- 1.0 RC1: 16/Apr/07 - 1.0 final: 23/Apr/07 - 1.0.1: 07/May/07 - 1.1 B1: 21/May/07 - 1.1 final: not defined
Please all committers answer on my previous email and this one to ensure we're all on the same page and all agree on the way forward...
Thanks -Vincent
On Apr 6, 2007, at 3:17 PM, Vincent Massol wrote:
Hi,
I'd like to propose the following:
* Release RC1 by end of next week with as many important bugs fixed as possible * Wait for 1 week after RC1 is released and declare RC1 to be 1.0 final is no critical/blocking bugs are found * Dedicate the XWIKI 1.0 branch to contain ONLY bug fixes going forward * Put new features/improvements ONLY on trunk * Release 1.0.1 2 to 3 weeks after 1.0 is released with bug fixes * Define a roadmap for 1.1 in term of what we want in it. It should be achievable within 3 months. * Change the version on trunk to be 1.1-beta-1 and release after 2-3 weeks. Increase to 1.1-beta-2 and repeat, etc. till we either reach something close so the initial roadmap for 1.1 in term of features or we reach the 3 months delay. In any case, release 1.1 at that time. * I propose to NOT create a branch for 1.1 till the final 1.1 is released and when it is I propose we don't release 1.0.x releases any more and instead release 1.1.x bug fixes releases (we don't have enough manpower to support more than 2 releases in parallel, it's already going to stretch us a lot).
WDYT?
Thanks -Vincent
Sergiu -- http://purl.org/net/sergiu
-- You receive this message as a subscriber of the xwiki- [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/ wws
participants (2)
-
Sergiu Dumitriu -
Vincent Massol