Re: Preparation for 1.0 release

What does everyone think of the Network Controller and it associated 
Prefpane?  It is mostly done, and I am sure that I can complete it 
before the FCS release (likely by the beta stage).  At the moment it is 
only missing the detection of the network change, but I know how to do 
this with the code that Eric sent me.  The UI portion is frozen though. 
  And of course testing, but I have already tested most of it.
Also, can anyone put this in the project for me?  I seemed to have lost 
my project builder in switching to Xcode.  Either that, or tell me how 
to get it back.  It may be better if someone else does it as I do not 
know how to actually add the pref pane properly to the list.  Whenever 
I display prefs, the network pref is in a second row and only the top 
20% of it is visible.  Everything needed is committed with the 
exception of a network pref pane icon.  I can concoct one if needed.

After it is in, I can commit my AIM changes that use this.  I have held 
off on my AIM updates since it would be a pain to separate it from the 
networkcontroller update.

Yeah, the Conversation branch is too young to make it into 1.0.  
Especially since it will have a sizable localization hit.  Maybe for 
1.1, 1.5, 2.0, whatever.

-----------------------------------------------------------------
Graham Booker		Texas A&M University
[email protected]	  Graduate Student in ELEN
------------------------------------------------------------------
On Oct 27, 2003, at 3:02 PM, Alan Humpherys wrote:

> Fire Development Team,
>
> 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.
>
> 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!)
> 	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)
>
> 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.
>
> Alan
>
>
>
> -------------------------------------------------------
> 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/
> _______________________________________________
> fire-development mailing list
> fire-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/fire-development
>



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/