I'm reviewing the rules. I generate a lot of preview releases (never to be voted on) for clients.
For that, I stop after "Generate the Release". I can expand the docs; to close a release you click its checkbox and choose "close" from the toolbar. At that point, you provide a name, "Apache Tapestry 5.4-beta-xx preview release". For a beta release, skip the "Update JIRA and generate release notes" step. Hope that helps! On Wed, Apr 8, 2015 at 1:31 AM, Jochen Kemnade <jochen.kemn...@eddyson.de> wrote: > Howard? > > > Am 22.03.2015 um 09:40 schrieb Jochen Kemnade: > >> I could still use some help here. >> >> Am 03.03.2015 um 18:58 schrieb Jochen Kemnade: >> >>> Hi, >>> >>> I think it's time for a new beta and it's time for me to become familiar >>> with how to do that. >>> I think my machine is configured correctly now, I can build, sign and >>> upload the archives to Nexus (i.e. just did so: orgapachetapestry-1052). >>> But I'm not sure what to do next. >>> Yes, I've read the instructions at >>> https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Process, >>> but I'm not sure, which part of that applies to public releases only. >>> Do I just need to create a git tag and close the release in Nexus? >>> >>> Jochen >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com @hlship
