KPopupMenu will have to be replaced also. I have a new class for popupmenus with titles with all sorts of cool stuff like multiple title label items, gradients, and pixmaps, but it requires a newer Qt than the standard 10/9 snapshot. When we move to a newer one I'll commit it. It does support the same API as the old KPopupMenu, but using it is discouraged. There is a insertTitle() method instead. Waldo Bastian wrote: > > Hiya, > > This weeks topics: > > * kdelibs is feature frozen as of today. This means that no new > features should be added. Changes which affect the API of any of the > libs in kdelibs should be discussed on kde-core-devel first. > Excemptions are granted to: > - Mathias Hoelzer-Kleupfel for adding a new kcontrol module > header to kdecore. > - Matthias Ettrich for finishing the session management API. > > New features can be added and further extensions to the API of > kdelibs can be made after KRASH has been released. > > GOAL OF THE KRASH (1.89) RELEASE > ================================ > > * Stabilize development. > * Offer third party developers a convenient way to become familair with > Qt2.x / KDE 2.x > > REMARKS > ======= > > KRASH will be alpha quality software. It is not recommended to use > KRASH for daily work. Although the API of KRASH should be relatively > stable, CHANGES will be made to it before the final KDE 2.0 release. > It is not recommended to release applications based on this release. > Distributors should NOT SHIP this release without providing a stable > and complete version of KDE as well. > > CURRENT STATE > ============= > > 2. kdelibs is feature frozen. No new features should be added. Changes > to the API should be discussed on kde-core-devel first. > > NEXT MILESTONE > ============== > > 2. Feature freeze kdebase & koffice in _2 WEEKS_ from now. (15-11-99) > > CONTENTS OF THE RELEASE > ======================== > > The following packages will be included in KRASH: > * kdelibs > * kdebase > * koffice > > RELEASE SCHEDULE 1.89 > ===================== > > 1. When: NOW > What: Determine what has to be done API-wise before 1.89 can be released. > What: Determine what will be released with 1.89 > > 2. When: 1 Nov '99 > What: Feature freeze kdelibs. > > 3. When: 15 Nov '99 > What: Feature freeze kdebase. > > 4. When: 15 Dec '99 > What: Release of 1.89 (kdelibs + kdebase only) > > --- Everything unfrozen > > THINGS TO SOLVE FOR 1.89 > ======================= > > None. > > AFTER 1.89 > ========== > > After 1.89 has been released all packages will be unfrozen. Goal is > to start with a 1.90 release directly after 1.89. This means that > with releasing 1.89 kdelibs will be unfrozen and that after 1 month > kdelibs will be feature frozen for 1.90. > > CHANGES TO THE RELEASE SCHEDULE > =============================== > > If you foresee problems with the above schedule, have additions or have > questions about the schedule, please contact Waldo Bastian (bastian@kde.org). > > Changes made to release schedule will be announced on the KDE development > mailinglists. Once a week the status of the release will be posted > to the KDE development mailinglists. > ------------------------------------------------------- -- Daniel M. Duley - Unix developer & sys admin. mosfet@mandrakesoft.com mosfet@kde.org mosfet@jorsm.com