Martin Geisler <[EMAIL PROTECTED]> writes: > [yada, yada... boring release checklist... bla bla... :-)] > > If people could do this until *Wednesday*, then I'll see if I can > teach run.py to actually create a full tar.gz/zip file for > distribution, and then I hope we can put 0.4 out Wednesday evening.
Disclaimer: I have never tried to do releases in a team like this before, so let me know if you have any suggestions... I could imagine a system where we make a release on, say, the first Wednesday of each month. Then everybody would know and people can hurry up their code in the weekend before, commit on Monday and we'll all look at it on Tuesday before the (mostly automated) release will be done on Wednesday. Does that sound feasible? -- Martin Geisler
pgpNOC2AVh3VF.pgp
Description: PGP signature
_______________________________________________ viff-devel mailing list (http://viff.dk/) [email protected] http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
