On Dec 19, 2007 4:33 PM, Rajarshi Guha <[EMAIL PROTECTED]> wrote: > On Dec 19, 2007, at 10:30 AM, Egon Willighagen wrote: > > I just blogged about the current state of the CDK 1.0.x branch in my > > blog [1]. Based on these results, I will release (unless someone else > > want to step in as release manager. Please, please, please...) CDK > > 1.0.2 somewhere over the holidays... > > Nice analysis. Can't release be (partially) automated?
Partly, yes. Small part though... Things that cannot be automated: - creation of a ChangeLog - making sure modules are stable (you know the rules) - fixing the first two lists of [1] - making an announcement (and post to -user, FreshMeat, ...) - check that it builds from the .tar.gz and the .zip - check if JUnit gives the same results when starting from those two - upload to SF And I'm sure I am forgetting a number of things... But true, some of the release managers work is already done. Checking the state of the branch. That's not automatable either. Egon 1.http://cheminfo.informatics.indiana.edu/~rguha/code/java/nightly/bugs.html -- ---- http://chem-bla-ics.blogspot.com/ ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
