> An automated build process (perhaps Gump/Alexandria, although that seems > to serve a different purpose) that would generate nightly builds off a > pure, unadulterated CVS of the source. A milestone build would just be > a particular nightly build that was moved into a "milestone" directory. > This would make it easy to i) generate milestones and release and ii) > keep track of the exact binaries we've distributed. All committers > would have necessary write access to the relevant directories, so any > committer could put out a milestone. Releases would basically be > handled identically to milestones. Having set this up in a commercial > environment (although we used Perforce and not CVS) I know that it's not > particularly difficult. Especially with Ant in the picture. But we can > hash this out later, after the current release is out the door.
As I've said before, if someone has a machine on which they can make *clean* builds (preferably linux, to preserve permissions) and can upload them to their home dir on cvs.apache, or grant me read access on their machine, I'd be quite happy to set up a cron job on my daedalus account to pull the build into the downloads site. The build process would ideally date-stamp the archive files to avoid confusion. I may yet be in a position to do this myself. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
