Menu
▾
▴
fire-localization
|
From: Alan H. <al...@us...> - 2003-10-27 21:05:29
|
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
|
|
From: Jason T. <tow...@ma...> - 2003-10-28 04:17:05
|
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 |
|
From: Paul B. <len...@ma...> - 2003-11-02 19:52:12
|
My replies are inside the quoted text ----------Original Message---------- On 10/27/2003 14:02, Alan Humpherys <al...@us...> 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) There is one "bug" that I haven't submitted because I'm not sure if the feature is functional yet. I'm using CVS code and building it on my machine. My icon (which I placed according to instructions) is not showing up to my buddies (though it shows up on my buddy list). In addition, the MSN and Yahoo! protocol fixes still haven't been applied to 1.0. I suppose we are aware of this? > Localizers > Do you have the time to localize Fire between November 7 and November 21 (2 weeks!) I certainly hope so. I have two four-day weekends coming up: Nov 6-9 and Nov 21-24. I definitely should be able to do this. I'm also hoping that for 1.0 there will be NO untranslated error messages. Yay! I think that if I'm able to do this then we need to start submitting Fire to some Russian Mac web sites. > 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 Paul |
|
From: Jason T. <tow...@ma...> - 2003-11-02 23:34:27
Attachments:
smime.p7s
|
On Nov 2, 2003, at 11:52 AM, Paul Borokhov wrote: >> 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) > > There is one "bug" that I haven't submitted because I'm not sure if > the feature is functional yet. I'm using CVS code and building it on > my machine. My icon (which I placed according to instructions) is not > showing up to my buddies (though it shows up on my buddy list). This feature only works with AIM Oscar... is that what you are using? > In addition, the MSN and Yahoo! protocol fixes still haven't been > applied to 1.0. I suppose we are aware of this? Yes, they have... are you saying that 0.32.h works for you but building your own version doesn't? Try updating to the latest CVS again. It seems to me that our CVS issues may have been addressed... I was able to see changes through anonymous CVS shortly after checking them in yesterday. -Jason |
|
From: Paul B. <len...@ma...> - 2003-11-03 00:45:43
|
Ok, here goes ----------Original Message---------- On 11/2/2003 15:34, Jason Townsend <tow...@ma...> wrote: > On Nov 2, 2003, at 11:52 AM, Paul Borokhov wrote: >>> 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) >> >> There is one "bug" that I haven't submitted because I'm not sure if >> the feature is functional yet. I'm using CVS code and building it on >> my machine. My icon (which I placed according to instructions) is >> not showing up to my buddies (though it shows up on my buddy list). > > This feature only works with AIM Oscar... is that what you are using? I've always been using Oscar, just checked now-yes I am. My icon shows up on my buddy list (I have myself in it) but on no one else's. I even signed on using iChat under a different SN and I couldn't see it. >> In addition, the MSN and Yahoo! protocol fixes still haven't been >> applied to 1.0. I suppose we are aware of this? > > Yes, they have... are you saying that 0.32.h works for you but > building your own version doesn't? Try updating to the latest CVS > again. It seems to me that our CVS issues may have been addressed... > I was able to see changes through anonymous CVS shortly after > checking them in yesterday. I checked out fresh code and those protocols are now working > -Jason Paul |
Thanks for helping keep SourceForge clean.
X