Status for the 1.0 Beta 3 release
Hi developers, Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7 Thus we have 28 issues fixed in Beta 3. There are 61 remaining and planned in Beta 3, 28 in Beta 4 and 9 in RC1. Total = 97 before 1.0 Seen our manpower I think we can assume we can do 25 issues per 2 weeks releases (Marta is not going to be available much in Feb 2007 as she'll be working on other stuff). 97 / 25 == 4 releases. We have 2 currently planned (Beta 4 and RC1). Thus we have 2 questions to answer: 1) Do we release Beta 3 today? 2) How do we fix all issues for 1.0 final? Do we release Beta 3 today ----------------------------------- My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0 The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes. Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow. Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours. How do we fix all issues for 1.0 final --------------------------------------------- Looking at what we fixed in Beta 1, 2 and 3, I still believe we should focus more on fixing only important bugs and move out improvements and nice to have stuff. I believe we need to review again the current issues tasked for 1.0 and move those that are not important bugs. Also we should be careful not to create new issues for 1.0 if they are not bugs. Let's do this sorting and let's post back here. If it still doesn't fit in the planned Beta 4 and RC1 then we might need to include another Beta 5. WDYT? Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire. http://fr.mail.yahoo.com
Hi Vincent ! I agree to your opinion. We still have many issues for 1.0 I think we should plan for B5 or increase the time for B3 and B4 ( We should plan for B5 and release B3 for now. ) I'll assign some issues for me and working in it for B4 and B5 ( if we plan for B5). Best regards ! On 1/22/07, Vincent Massol <[email protected]> wrote:
Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
There are 61 remaining and planned in Beta 3, 28 in Beta 4 and 9 in RC1. Total = 97 before 1.0
Seen our manpower I think we can assume we can do 25 issues per 2 weeks releases (Marta is not going to be available much in Feb 2007 as she'll be working on other stuff).
97 / 25 == 4 releases. We have 2 currently planned (Beta 4 and RC1).
Thus we have 2 questions to answer: 1) Do we release Beta 3 today? 2) How do we fix all issues for 1.0 final?
Do we release Beta 3 today -----------------------------------
My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0
The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours.
How do we fix all issues for 1.0 final ---------------------------------------------
Looking at what we fixed in Beta 1, 2 and 3, I still believe we should focus more on fixing only important bugs and move out improvements and nice to have stuff. I believe we need to review again the current issues tasked for 1.0 and move those that are not important bugs. Also we should be careful not to create new issues for 1.0 if they are not bugs.
Let's do this sorting and let's post back here. If it still doesn't fit in the planned Beta 4 and RC1 then we might need to include another Beta 5.
WDYT?
Thanks -Vincent
___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
-- You receive this message as a subscriber of the [email protected] 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
On Jan 22, 2007, at 1:28 PM, Vincent Massol wrote:
Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
[snip]
Do we release Beta 3 today -----------------------------------
My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0
The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours.
[snip] Ok. I have received only 1 answer from Nam so far... Please continue to provide answers on the other part of the mail, i.e. the part about the general 1.0 release. I'll go ahead with my plan and release beta 3 today. Please shout if something is not working in beta 3 (but please shout quickly ;-)). Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire. http://fr.mail.yahoo.com
Hi all, It's already late for the b3 release, so we should make it as soon as possible. Unfortunately, there have been few issues solved for this release, so the release notes won't be as large as for the previous ones. I guess we all had other stuff to do. Since we are so close to the 1.0 release, I say we move non-critical issues to 1.1, thus the number of issues for 1.0 will be reduced. But there are still too many issues for just one more beta, so I guess we'll need b5. Also, I don't agree with the branching policy (make a branch 3 days before the release). I suggest we make a 1.0 branch now, and any experimental code, or changes that do not fix a 1.0 issues, should go in the trunk, while 1.0issue related code should go both in the 1.0 branch and the trunk branch. Sergiu On 1/25/07, Vincent Massol <[email protected]> wrote:
On Jan 22, 2007, at 1:28 PM, Vincent Massol wrote:
Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
[snip]
Do we release Beta 3 today -----------------------------------
My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0
The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours.
[snip]
Ok. I have received only 1 answer from Nam so far... Please continue to provide answers on the other part of the mail, i.e. the part about the general 1.0 release.
I'll go ahead with my plan and release beta 3 today. Please shout if something is not working in beta 3 (but please shout quickly ;-)).
Thanks -Vincent
___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
-- You receive this message as a subscriber of the [email protected] 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
On Jan 25, 2007, at 9:59 AM, Sergiu Dumitriu wrote:
Hi all,
It's already late for the b3 release, so we should make it as soon as possible.
Unfortunately, there have been few issues solved for this release, so the release notes won't be as large as for the previous ones. I guess we all had other stuff to do.
Since we are so close to the 1.0 release, I say we move non- critical issues to 1.1
I agree but we need to identify them. I've identified those potential: 684 683 615 602 601 70 ? 570 ? 563 531 404 405 378 ? Let me know if you agree to move them to 1.1 As you can see this is far from enough to reduce substantially the # of issues for 1.0 so we need to find more. Please suggest others here. Thanks -Vincent
, thus the number of issues for 1.0 will be reduced. But there are still too many issues for just one more beta, so I guess we'll need b5.
Also, I don't agree with the branching policy (make a branch 3 days before the release). I suggest we make a 1.0 branch now, and any experimental code, or changes that do not fix a 1.0 issues, should go in the trunk, while 1.0 issue related code should go both in the 1.0 branch and the trunk branch.
Sergiu
On 1/25/07, Vincent Massol < [email protected]> wrote:
On Jan 22, 2007, at 1:28 PM, Vincent Massol wrote:
Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
[snip]
Do we release Beta 3 today -----------------------------------
My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0
The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours.
[snip]
Ok. I have received only 1 answer from Nam so far... Please continue to provide answers on the other part of the mail, i.e. the part about the general 1.0 release.
I'll go ahead with my plan and release beta 3 today. Please shout if something is not working in beta 3 (but please shout quickly ;-)).
Thanks -Vincent
______________________________________________________________________ _____ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
-- 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
-- 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
On Jan 25, 2007, at 9:47 AM, Vincent Massol wrote:
On Jan 22, 2007, at 1:28 PM, Vincent Massol wrote:
Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems everyone was busy and not much work has been done for beta 3. Here's what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
[snip]
Do we release Beta 3 today -----------------------------------
My personal preference is to continue doing bi-weekly releases as: 1) It trains us to do releases and improves our release process 2) It gives a rythm which is good for us and for our users. I believe this is extremely important 3) It allows us to iron out migration issues 4) It allows our users to report issues as soon as they happen rather than reporting them at the end when we're close to releasing 1.0
The possible downsides: 1) Too many releases for our users. I don't think this is valid as we have release notes and our users do not have to upgrade. They can decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll create a branch for Beta 3 in a few hours.
[snip]
Ok. I have received only 1 answer from Nam so far... Please continue to provide answers on the other part of the mail, i.e. the part about the general 1.0 release.
I'll go ahead with my plan and release beta 3 today. Please shout if something is not working in beta 3 (but please shout quickly ;-)).
Change of plan. I'm postponing the release of Beta 3 by a few days (hopefully before beginning of next week). Reasons: * Ludovic found some instabilities in the Panels. We need that fixed before we release. * I've been tasked on other stuff for a few days that take priority. I'll keep you posted. Thanks and sorry -Vincent ___________________________________________________________________________ Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire. http://fr.mail.yahoo.com
participants (3)
-
Phung Nam -
Sergiu Dumitriu -
Vincent Massol