Re: Preparation for 1.0 release

Thanks for the outline, Alan. This looks good to me.

On Oct 27, 2003, at 1:02 PM, Alan Humpherys wrote:
> We've been working on the 1.0 release for quite some time now, and 
> 0.32 is getting a bit long in the tooth.  I was talking with Jason 
> last night, and we both felt that it was important to make a big push 
> to get 1.0 out to the world.
>
> Also, there are some bugs in 0.32.g that need fixed immediately:
>
> With that in mind, I propose that we do the following:
>
> 1) November 1 - (0.32.h)
>      Release 0.32.h containing:
> 	- Fix for 10.1 crash upon connection to MSN
> 	- Proper flags to connect to Jabber-SSL (build issue)
> 	- Fix for hang during MSN connection on some systems.
>
>     Jason would take the lead on this release.

In addition, any high value/low risk bug fixes would be eligible for 
this release. Let me know if anything comes to mind.

> 2) November 7 - (1.0 UI Freeze)
>     Get 1.0 to a UI frozen state with as many bugs fixed as possible.
> 	- This includes all strings & NIBs
>     Release a 1.0 preview (alpha) to the members of the mailing lists.
>
> 3) November 21 - (Localized Beta Refresh)
>     Complete all localizations (this gives 2 weeks from the UI freeze)
>     Fix all 1.0 Blocker bugs
>     Fix as many 1.0 candidate bugs as possible
>     Release a 1.0 preview refresh (Beta) to the members of the mailing 
> lists.
>
> 4) December 5 - (1.0 FCS)
>     Fix issues found during alpha/beta testing
>     Fix all 1.0 candidate bugs (unless deferred)
>     (Likely to have one or more Beta refresh builds during this time.)
>     Update website and help documentation for 1.0
>
> =======================
>
> With that schedule in mind, here are some questions that I need 
> answered:
>
> Developers (especially the core team)
> 	Can you get the UI/strings complete on your features/fixes by 
> November 7? (2 weeks!)

I can complete the Colors pref in that time (and the removal of Colors 
from other pref panes). I would like to have some sort of Themes pref 
as well which hopefully I can do in time for 1.0. In order to meet the 
schedule we may need to postpone some of the pref reorg changes that 
were discussed.

> 	Can you contribute significantly to fixing the 1.0 bugs by November 
> 21? (4 weeks!)
> 		We have:
> 			18 blocker bugs
> 			49 candidate bugs
> 			50 bugs we are deferring
> 			(perhaps more will be entered)

I will be able to work on Fire in the evenings and weekends over the 
next few weeks.

> Localizers
> 	Do you have the time to localize Fire between November 7 and November 
> 21 (2 weeks!)
>
> Can each of you who plan on assisting with this effort please respond 
> with your availability so that we can plan accordingly?
>
> (By the way, Graham, we are not planning on your Conversation branch 
> being a part of 1.0)
>
> Also, we would like to use the bug/feature trackers on sourceforge to 
> track progress on fixing these issues.  Please take a look at the bugs 
> in the 1.0 Candidate and 1.0 blocker groups and take ownership of the 
> ones you are going to work on. (There are a lot still assigned to 
> 'nobody') If you don't know how to use that bug tracker, please 
> contact me and I can help.

-Jason



-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/