Ben Hines and I have been working on improving the release process, at least from the technical point of view (creating the binary installer and so on). These improvements include a script Ben wrote to automate the creation of the binary installer, as well as various updates we have made to the HOWTO files in the scripts CVS module and its various subdirectories.
The scripts CVS module is, in my opinion, the best place to store checklists of any kind about the release process. In terms of timing of announements, though, we need to be careful. WIth this recent release, for example, we unfortunately kept finding little problems with the binary installer and we've replaced it on Sourceforge several times. So there needs to be a testing period before things are formally announced, I believe. As for giving explanations to the press about why a release was made, well, I hope that in the future we'll have a much more automated system and we'll simply be releasing on a regular basis. We don't have any way of keeping track of what major changes have been made between releases, though. The only way I can imagine that happening is if we set up some sort of Fink master ChangeLog someplace and ask package maintainers to make entries there reporting on significant updates of their packages. -- Dave ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
