[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    CVS HEAD reminder / 3.0 feature plan / time schedule
From:       Dirk Mueller <mueller () kde ! org>
Date:       2001-11-05 16:00:31
[Download RAW message or body]

Hi, 

I've split the 3.0 feature plan in 3 categories now: 

- "TODO": still nothing there
- "in progress": working implementation, main parts implemented,
   checked in, needs still polishing / bugfixing
- "Finished": Can be considered completed and stable. 

I've also removed unclear entries (commented them out). If you are affected, 
please correct the parts I mentioned in the comment above it and _ask_ _me_ 
to readd it again. Thanks!

Please keep the entries you added up to date yourself. That means moving 
them to "status yellow" or "green" as appropiate. If you have a clear 
timeframe, like "needs 2 weeks", please add this information. 

Note: Entries that are still "red" by middle/end of December _might_ be 
dropped from the feature plan if necessary!

Regarding time schedule: 

- We're planning preparation of a Beta release by the end of the month. 

  This has the following implications: 
    - Please try to change / add necessary i18n strings as early as 
      possible. This helps those translation teams that really have a 
      lot to do for 3.0 (changed / improved BiDi support). Late
      string changes makes them unhappy, remember that :). However
      string changes are still allowed after Beta1, don't panic (yet). 

    - Please try to get the bigger changes that might break things
      in early enough. There is one week planned for stabilizing the
      code base for Beta1 release though, but a week is really short
      so things should be working smooth before already.  

    - The status of CVS around Beta1 will decide on whether or not
      we need a second (third) Beta. We can't switch to "RC"-status
      if not all "red" items are gone and almost all "yellow" ones
      are close to completion. 


Did I forget something?

Thanks for reading,


Dirk

[prev in list] [next in list] [prev in thread] [next in thread]