Le 8 mai 07 à 12:38, David Chisnall a écrit : > On 5/7/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: > >> After that I would like to have an extra release between 0.2 and 0.3, >> this intermediate release would be numbered 0.2.5. >> The aims of this release would be bug fixes and refined UI for the >> whole environment as it is now. > > I am not sure why this is a 0.2.5, rather than a 0.3. To me, 0.2.5 > should be a bug-fixing release on 0.2, without new features, but if > we go this route now then we are going to end up having to maintain > two trees for a bit (new features, and bug fixes).
Bug fixes only release would be 0.2.1 I think. 0.2.5 could be numbered 0.3… then 0.3 would become 0.4. I'm fine with this choice too. >> Main tasks would be: >> - polished UI for all applications > > And consistent. After the 0.2 release, I suggest we all spend some > time running the LiveCD and noting down inconsistencies and bits of > bad UI. Agreed. >> - cleaned WildMenus (menu support should be perfect at this time) > > It seemed to be working last time I used it, but working better is > always good :) Exactly (tear-off feature is broken for example). >> - stable Io + Spot reintroduced > > How much effort is this? Fixing a single bug in theory and cleaning Spot code a bit. The Io memory corruption bug I discussed with you one time on silc. >> - SystemConfig (related to the previous one) >> - both UI and API consistency for menulets by finishing >> ServicesBarKit >> - fully working IconKit >> - better website > > Better website is definitely worth doing. I've tweaked it a bit, but > it could use some more work. We need something on the front page > that really shows people we are an active project. This is more an > attitude thing than a design issue though. People need to start > updating the news section, not just the blog, because new visitors > see news immediately and don't see the blog. It would be good if we > could have something on the front page saying 'n commits in the last > 7 days' or similar, to let people know the code is still evolving. It looks more lively than gnome.org though. But less than kde.org ;-) We could replicate blog entry headlines on the front page (below News or in the left column). >> - better framework documentation > > Yup. I would like to make up-to-date and accurate documentation a > requirement for moving something into stable, at some point if not > right now. I'm fine with such drastic measure, I just love documentation :-). But it's may be too extreme right now if you take in account some recent modules already in stable don't respect code style and I initially put code style conformance as a condition for any recent modules to be moved into stable. OPMLKit is neither documented or conform to coding style to take an example. Also documentation is less critical for some frameworks than others. For example, if CollectionKit is documented, having BookmarkKit documented isn't be critical at all. Cheers, Quentin. _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
