Re: [argouml-dev] Upcoming releases - the path towards 0.22

[Michiel van der Wulp]

Hi Linus,   There is one problem: I'd like to continue working with Andrea for the Google SOC in the same way: Andrea attaches a patch to an issue (defect or enhancement) and I check and commit.   Starting alpha releases now, would block this - initially only for enhancements, later also for defects.   Is there a way to prevent this?   On the other hand, if there is no way around, then the sooner the better (and limited to a short period, too).   Regards, Michiel       ----- Original Message ----- From: Linus Tolke To: dev@argouml.tigris.org Sent: Monday, June 12, 2006 12:13 AM Subject: [argouml-dev] Upcoming releases - the path towards 0.22 Hello all!   I just created an announcement for the 0.21.3 release. I have sadly neglected to write announcements for the past releases.   The plan is to now, soon (tomorrow or actually today), enter the alpha phase before the 0.22 release. The beginning of the alpha phase means that no more enhancements or changes will go into the 0.22 release, just defects fixed.   Are we ready for this?   I noticed that there is one P1 defect, the issue 4256. It is a blocker also for the 0.22.alpha1 release so that will have to be fixed. We then have 14 P2 defects. All of them will have to be fixed before we enter beta-state.   Our options are: Go ahead tomorrow and start working with the intensive alpha/beta release schedule towards 0.22. Put the 0.22.alpha1 off for a couple of days. Introduce a 0.21.4 release in 2 weeks deferring the alpha/beta and 0.22 releases about 3 weeks. Notice that if there are too many P2 defects that we don’t solve in time for the betas, then the release will be deferred anyway. We need to have the “right amount” before leaving the 0.21 release suite.   What shall we do? It all comes down to how much work is left to get 0.22 in shape. If I am to make the release 0.22.alpha1 tomorrow, I will do it on the evening so we have around 19 hours to decide this before I go ahead and embark on the first option.   Let me know where you think we are and what we should do.               /Linus   ******************************************************************* Linus Tolke [EMAIL PROTECTED]    [EMAIL PROTECTED] *******************************************************************   No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 11/06/2006

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 11/06/2006


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]