The Windows build process is not 100% automatable right now, nor has it ever been. There's a bunch more work necessary to make that happen. Ideally, someone would offer to help me with this.
The actual *publish* of an approved final build should still be a manually invoked process, especially because it requires individual credentials to be used to push the release to the Apache mirrors, and for the Windows binary, there is a manual Symantec signing process (though I'm informed the latter can be automated through a SOAP API [ugh]). We also need to manually say "this is the one" after the lists have gone through acceptance testing. -Joan ----- Original Message ----- > From: "Robert Kowalski" <[email protected]> > To: [email protected] > Sent: Friday, December 16, 2016 1:55:45 PM > Subject: [PLANNING] CouchDB 2.1 > > Hi, > > I wanted to test the waters regarding a CouchDB 2.1 release. Since > 2.0 > a few new features and many bug fixes have landed. > > I know its holiday season soon and I wanted to kick off the > discussion > about a release date for 2.0.1 or 2.1.0. > > One thing that worries me (correct me if I am wrong): I think > releasing CouchDB depends much on Joan and Jan right now, which is > bad > (bus factor etc). > > I don't know much about the internals of the build process for our > releases, but I would volunteer to automate the (jenkins?-)build for > snaps. > > Best, > Robert >
