commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@gmail.com>
Subject Re: [RESULT] Release Proxy 1.0 (from rc4)
Date Wed, 27 Feb 2008 17:01:05 GMT
On Wed, Feb 27, 2008 at 4:48 PM, James Carman
<james@carmanconsulting.com> wrote:
> On 2/27/08, Niall Pemberton <niall.pemberton@gmail.com> wrote:
>
> > On Wed, Feb 27, 2008 at 4:11 PM, James Carman
>
> >  >  I've done this.  But, when you go to the "releases" section of the
>  >  >  commons site, it says that  proxy has not had a release yet.  What
>  >  >  sets all of that up?
>  >
>  >
>  > The site is in commons-build
>  >    http://svn.apache.org/viewvc/commons/proper/commons-build/trunk/
>  >
>  >  ...and the download pages are generated using xslt. So you have to
>  >  update commons-build\downloads\download.xml and then re-generate those
>  >  pages - instructions here:
>  >   http://svn.apache.org/repos/asf/commons/proper/commons-build/trunk/downloads/README.txt
>  >
>
>  This stuff should be added to our instructions.

Yes, although I'm hoping that now commons-build-plugin has been
released that will be adopted for generating the download pages - I'm
planning to raise that once that plugin is in a release of
commons-parent (hopefully version 8 which is being voted on now). If
it is then it becomes simpler (just running "mvn commons:dowload-page"
in the component project)

>  >  I've updated it for proxy 1.0 and uploaded a new version of that page
>  >  - should be able to see it after the next sync
>  >   http://svn.apache.org/viewvc?view=rev&revision=631637
>  >
>
>  Thank you!  And, sorry for being such a PITA, but this is my first release.

np :)

>  Have we ever considered having devoted "release specialists" who know
>  all of this process and take care of all releases?  What I'm thinking
>  is that the project's release manager would get everything ready and
>  create the SVN tag.  Then, they'd propose a vote based on the tag.
>  Once the vote passes, the release specialist takes over.  They know
>  how to do all of the building (with src and javadoc jars in the bin
>  distribution), signing, hashing, copying, deploying, updating the
>  commons site, etc.  Then, it's back to the release manager to do the
>  announcement.  I wouldn't mind being one of these release specialists
>  once I learn the ropes.  I just think that this might help us get
>  releases out the door more often.  I know that I postponed releasing
>  proxy for quite some time because the whole process seemed quite
>  daunting to me.  It's really not that bad, if you know what all the
>  steps are.  Very few of us actually know all of the steps, though.

Like everything here it needs volunteers willing to take that role. If
I have spare cycles at the time, I would be willing to do some
releases and I don't mind being asked.

Niall

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message