On 2/27/08, Niall Pemberton <[EMAIL PROTECTED]> 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. > 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. 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. > > Niall > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
