On 2 June 2016 at 23:15, Gary Gregory <garydgreg...@gmail.com> wrote: > On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter <brit...@apache.org> wrote: > >> Emmanuel Bourg <ebo...@apache.org> schrieb am Do., 2. Juni 2016 um >> 23:39 Uhr: >> >> > Hi all, >> > >> > A part of the release process is to update the web site. I wonder if >> > this could be simplified with a Jenkins job watching for the release >> > tags and building/uploading the new site automatically. That would make >> > one less thing to think about when releasing new versions. I suspect the >> > most difficult issue to solve is to let Jenkins publish the content >> > without compromising the security. >> >> >> > Thoughts? >> > >> >> I'm all for automation. The only problem I see is, that I usually publish >> the final site from a dirty working copy. This is because I don't put the >> release date into changes.xml until after the release. > > > I like to use the RC date for changes.xml (which I forgot to do when I > recently RM'd Commons CSV 1.4!) > > If the RC becomes the release, then you are done. If the RC does not, then > update the date again for the next RC. I think that is 'sane' step.
What I do if I remember is add 4-5 days to the start of the RC vote. This gives time for the vote plus publication delay. I can then time the announce for the correct date. But it's not too difficult to fix the website if necessary later. > Our Maven plugin could be changed to do this so it becomes a command line > thing instead of a manual edit. > > Gary > > However I have >> realized that for example maven central uses that date the RC was upload to >> the staging repo as the release date. We could simply adopt this and use >> that date in changes.xml and commit it to the release tag. >> >> I'm sure it would even be possible to let jenkins create site archives as >> we're currently doing for some components. >> >> I have no idea about the security implications of this proposal. >> >> Benedikt >> >> >> > >> > Emmanuel Bourg >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
