commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@gmail.com>
Subject Re: [DISCUSS] Creating Project for Release Process Testing...
Date Thu, 10 Oct 2013 23:35:07 GMT
We're all still talking about the release process, but in all honesty I've
not done it for several years at Commons.  I think it would be immensely
helpful for those of us who have been at least part way through the process
fairly recently (Emmanuel, Gary, others?) to present your recollections of
what was difficult, so that we can have a real list of things to try and
address.

Matt


On Thu, Oct 10, 2013 at 10:46 AM, James Carman
<james@carmanconsulting.com>wrote:

> I need to have Matt start writing my emails. What he said! ;)  I'm too
> impatient to be so eloquent.
>
> On Thu, Oct 10, 2013 at 11:41 AM, Matt Benson <gudnabrsam@gmail.com>
> wrote:
> > Emmanuel,
> >   IMO this goes beyond the SCM question.  Commons releases are painful
> > (you've just been through the process; do you disagree?) and I submit
> that
> > this fact is the reason it takes so long for any of us to muster up the
> > courage to commit himself to diving into that process with no real idea
> > when he'll emerge.  Such a project would allow us to generalize and work
> > out the various "parts" that might be relevant to any Commons project and
> > could then serve as a cookbook to show how to address various situations.
> >
> > Matt
> >
> >
> > On Thu, Oct 10, 2013 at 10:34 AM, Emmanuel Bourg <ebourg@apache.org>
> wrote:
> >
> >> Le 10/10/2013 17:24, James Carman a écrit :
> >> > Why don't we create a real project that we can cut real releases on to
> >> > test our release procedures?  Perhaps we can set it up so that it
> >> > doesn't sync with central and just gets staged locally.  This way, we
> >> > can test out changes to the release process and see how they work.
> >> > Also, a new release manager can play around with that project and get
> >> > it right before diving into the real work.
> >>
> >> I'm not sure to see the need for this. There is no doubt Git is suitable
> >> for releasing our components. I just walked down the release process for
> >> JCI and besides for tagging I didn't have to interact much with SVN (I
> >> didn't use the Maven release plugin).
> >>
> >> With Git you would just have to create a branch, and push a commit that
> >> changes the version (1.0-SNAPSHOT -> 1.0). The rest of the procedure is
> >> the same.
> >>
> >> Emmanuel Bourg
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message