-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 w9ya wrote:
> > No comments on wikis. Or maybe better put; I had better not waste everyones > time on my impressions of wikis. Yes, since a lot of others realise the benefits, and contribute, regardless of the extra effort required to write good content on a wiki instead of flaming on a mailng list. Wiki's die when people don't show an interest ... > In any event; I think the timetable *needs* > to reiterated on the mailing list as "milestones" approach as stuff on a wiki > is easily "missed". Or, people can just check the release schedule every few days on their own when they know that a release may impact their own planning. >>and he also posted amessage to this list when Cooker Was Frozen... >>http://marc.theaimsgroup.com/?l=mandrake-cooker&m=106199249931465&w=2 > > > Well, the point was it need to be a message that said in advance that a freeze > was coming in (on let's say) two weeks. Something like that. There were, just not to this list. Any one with a real interest in freeze in main got one. > Sorry if that > wasn't clear, I guess I shouldn't have assumed everyone remembered the > essence of the previous threads on this. (A 1/2 a year ago or so.) > > >>>In any event, there are some packages like OO that should probably be >> >>upgraded >> >> >>>and given a chance to be tested well. A freeze announcement would have >>>allowed this to happen in a more controllable manner other than "oh well, >>>things are now frozen, no more changes, and this is the last testing >>>release". Put another way: Yes freezes are important, but I do agree that >>>some things need to be upgraded prior to a freeze and advanced >> >>announcement >> >> >>>of an upcoming freeze allows everyone involved in testing a chance to be >>>a part of these upgrades. >> >>OOo will be in RC2 according to Warly: >>http://marc.theaimsgroup.com/?l=mandrake-cooker&m=106206826212175&w=2 > > > Good. Again this is one example (and perhaps a poor one as it is being > upgraded). However I do not mean that every possible package should be > upgraded either. Of course, not, it's the role of the release manager to decide which ones do, and which ones don't. Warly obviously agreed to allow OO.o-1.1, but refused samba-3.0.0 (so samba3 will stay in contribs). Of course, this doesn't have to happen on public lists (since then the real issues often get lost). > Again, announcement(s) a week or two ahead would allow for > such things to happen more smoothly. Well, IMHO it's the maintainers responsibility to warn people of upcoming large upgrades, as I would have done if samba3 were accepted into main. Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/T1T4rJK6UGDSBKcRAjIvAKCANkW5/OjfK2XaqMbzxf+Ydy9argCgx3OO fNwReUzzy5Fc6qEmkbd1ThY= =I7Cl -----END PGP SIGNATURE----- ***************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *****************************************************************
