On Sat, Sep 17, 2016 at 10:10 AM, Matt Sicker <boa...@gmail.com> wrote:

> On 17 September 2016 at 11:13, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> >
> > From my experience, when I or someone finds any problem with an RC I
> > rolled, I sigh, cancel, and redo; but not before complaining to myself
> that
> > if there where not 50 steps to do a release, it would be less of a pain.
> >
> Is there a jira issue to address this? Or is it just spread across TODO
> comments in shell scripts right now?

Shell scripts? Jiras? Nah, everyone seems to roll their own process based
on a combination of the site pages [1] and wiki pages like "Using Nexus"
[2]. In addition, IIRC, some components have their own scripts and
specialized instructions. The site instructions are updated from time to
time, like instructions now that we have both git and svn in the picture.

IMO, some of the length of the process is due to the fact that we publish
binaries to BOTH our Nexus repository and to another set of folders. This
seems redundant IMO, one place for should be enough.


[1] https://commons.apache.org/releases/index.html
[2] https://wiki.apache.org/commons/UsingNexus

> --
> Matt Sicker <boa...@gmail.com>

E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
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

Reply via email to