<snip>
The scripts CVS module is, in my opinion, the best place to store checklists
of any kind about the release process.
agreed.
In terms of timing of announements, though, we need to be careful. WIthI can only agree with that as well. I would never go and make an official announcement unless , in this case you DRM, told me that it was safe to do so. If there are errors in the distribution and we have to release several fix-ups that simply destroys our credibility and image and no project can afford that. We have to be absolutely sure about the things we are doing. My suggestion would be this:
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.
1.) Compile the binary installer
2.) release it to a selected few beta testers (around 50 I guess)
3.) Wait a week
4.) tell me it is ok to announce and I will handle it from there.
As for giving explanations to the press about why a release was made, well,I will try to explain, why I am so keen on getting ourselves positioned nicely in the current media.
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.
The more exposure Fink gets, the better for us. Not only because it draws attention, it also drives interest. This shall bring new people interested in Fink, in what we do and in the further development. I am not talking about sponsors or commercial interest, I am simply referring to the curiosity of mankind. We cannot afford to run expensive banner ads, therefore we will have to run our "ads" trough supplying content and announcement about major achievements to preferably large websites which have a big audience.
Porting KDE 3.1 final, Tomcat, Apache2 , Gnome and all the well known projects are per se an announcement worth, because it is our goal to bring the variety of Unix apps to Mac OS X and those applications are key applications to the UNIX world.
I would be more than happy if people started helping me to create more and better press work for Fink by using such a global change-log. I could live with a single change-log for each major package as well, that is no issue. I would be more than happy to even code a little web interface where you can leave me a message about a certain package and what has been accomplished with it. This could easily be linked to the pdb.
I think there is a lot of potential and we simply have to harvest it properly. I will admit that it is harder to do with a voluntary effort of many , that applying such mechanisms in a commercial company is much simpler, yet I refuse to believe that we cannot manage this. I went to school far too long to give up trying this fast. I know it sound a bit pathetic, yet hopefully it spurs you all on.
-d
- ❜ Fantasie ist wichtiger als Wissen.❛ - Albert Einstein
-------------------------------------------------------
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
