Thanks Chuck. I had a look at a some of the below late last week but I'll be following a somewhat simpler bespoke process for this cpp release, Justin can restore order when he returns.
Robbie On 15 June 2015 at 14:12, Chuck Rolke <[email protected]> wrote: > Justin has notes on the process. > > Release process steps and notes > > > https://drive.google.com/open?id=1ML8twg28315eSyVmn-Qo455Gr6mlxrQl05Wg-otawpE > > Release history > > > https://drive.google.com/open?id=1HC916R-9Tbg9X2boOYBH6XroiXoQZwnJXwCm7Y5C99A > > Recent release pages - For finding out how it was done before > > https://cwiki.apache.org/confluence/display/qpid/0.32+Release > https://cwiki.apache.org/confluence/display/qpid/0.30+Release > https://cwiki.apache.org/confluence/display/qpid/0.28+Release > > Quirk - The tool Justin uses to generate the releases > > http://www.ssorj.net/projects/quirk.html > > Qpid site code - For updating the website for new releases; see the > "Generating release content" section > > http://svn.apache.org/repos/asf/qpid/site/README > > ----- Original Message ----- >> From: "Gordon Sim" <[email protected]> >> To: [email protected] >> Sent: Friday, June 12, 2015 11:37:16 AM >> Subject: Re: qpid-cpp release? >> >> On 06/12/2015 04:13 PM, Robbie Gemmell wrote: >> > On 12 June 2015 at 10:50, Gordon Sim <[email protected]> wrote: >> >> On 06/12/2015 10:31 AM, Robbie Gemmell wrote: >> >>> >> >>> Some other things that have come to mind: >> >>> >> >>> - What is the version going to be, 33.0 ? >> >> >> >> >> >> Personally I'd be inclined to just stick with the existing convention, >> >> i.e. >> >> 0.34. However I'm not too bothered about the version number, so whatever >> >> gets the most support is fine with me. >> >> >> > >> > In the interests of getting something out promptly, lets just go with >> > 0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34' >> > >> > I will spin an alpha today from trunk. We can create a branch later if >> > needed, but I'd e happy to just tag from trunk if noone is actually >> > planning any commits deemed unsuitable for the release. >> >> Sounds good! Thanks Robbie! >> >> >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
