El Thursday, 20 de March de 2008 12:42:33 [EMAIL PROTECTED] escribió: > Well, for 0.3, the amount of changes is so great that it probably > doesn't make much sense to list them all. Rather, the release notes > should only contain a general description of the status; what doesn't > work, and what works only with hacks or experimental patches not in the > trunk yet.
I could write up release notes from a list of keywords. > For the followup releases, a listing of changes would make sense. But as > I already said, I don't think that can easily be obtained after the > fact. Rather, someone would need to track the mailing list (and perhaps > IRC), and note down all changes mentioned -- perhaps on a wiki page. If > things are unclear when putting together the release notes from that, > the one doing it would have to ask the develepers involved. Since the wiki is open, that could be done together. To do it efficiently, I'll need an account at the hurd box to be able to work directly on the git repository (instead of waiting minutes for my changes to be saved). I can't promise to spend more than one or two hours a week on it, but I hope that this will still help the hurd. Best wishes, Arne -- Unpolitisch sein Heißt politisch sein Ohne es zu merken. - Arne Babenhauserheide ( http://draketo.de ) -- Weblog: http://blog.draketo.de -- Mein öffentlicher Schlüssel (PGP/GnuPG): http://draketo.de/inhalt/ich/pubkey.txt
signature.asc
Description: This is a digitally signed message part.
