El mié, 15-04-2009 a las 13:18 +0200, Chris Chabot escribió: > The php's release script doesn't do any signing yet, but if your willing to > send the instructions of the release signature standards are for apache I'd > be happy to build that in
http://www.apache.org/dev/release-signing.html describes the generic instructions, and http://incubator.apache.org/guides/releasemanagement.html is a incubator guide. The first one contains relatively detailed signing instructions. I don't have much experience in the incubator and how it differs from regular releases, but the second document should tell. Regards Santiago > > On Wed, Apr 15, 2009 at 1:11 PM, Santiago Gala <[email protected]>wrote: > > > El mar, 14-04-2009 a las 15:37 +0200, Chris Chabot escribió: > > > FYi the prefered packaging format for php-shindig is generated by the > > > shindig/php/make-release.sh file. > > > > > > in the 1.0.x branch it's version is currently set on 1.0, so just > > executing > > > it will give you the appropriate php-shindig-1.0.0.{tar.bz2,.tar.gz,zip} > > > files. > > > > > > I'll do a final test on them once you guys are release ready too, but in > > > principle the 1.0.x branch & release script have been ready since nov > > last > > > year, so I don't expect any surprises on that end > > > > > > > Is there provision for signing the releases? I can sign the keys of > > whoever is going to do it if we get some out of band, remote way to > > verify identity WRT keys signature. > > > > Regards > > Santiago > > > > > -- Chris > > > > > > On Tue, Apr 14, 2009 at 2:19 PM, Vincent Siveton <[email protected] > > >wrote: > > > > > > > I guess the plan should be: > > > > * release discussions: done by this thread > > > > * prepare the release: mvn release:prepare which tags the code > > > > * make the release: mvn release:perform which pushes (signed) > > > > artifacts to repository.apache.org > > > > * stage the generated Maven documentation > > > > * propose a vote on this list: mail should include the urls and the > > > > closed/left issues. > > > > * ask Incubator PMC for the release > > > > * publish and announce the release > > > > > > > > Anything else? > > > > > > > > If everybody is agree with this plan, I could try to start the process > > > > this week. > > > > > > > > Cheers, > > > > > > > > Vincent > > > > > > > > 2009/4/13 Ian Boston <[email protected]>: > > > > > Being a release newbie with a desire to step into the unknown, what > > needs > > > > to > > > > > be done ? > > > > > presumably, build some artifacts, sign them, put them somewhere, > > agree > > > > that > > > > > they should be the release, and then tell the incubator list we want > > to > > > > > release them ? > > > > > > > > > > Ian > > > > > > > > > > On 13 Apr 2009, at 21:52, Kevin Brown wrote: > > > > > > > > > >> None of those 3 issues are actually release blockers. No feature > > request > > > > >> is > > > > >> ever a release blocker unless that feature was explicitly identified > > as > > > > >> critical for the release at the beginning. > > > > >> > > > > >> On Mon, Apr 13, 2009 at 1:39 PM, Adam Winer <[email protected]> > > wrote: > > > > >> > > > > >>> I don't think we should wait for any of those issues. Release, and > > > > >>> release again. > > > > >>> > > > > >>> -- Adam > > > > >>> > > > > >>> > > > > >>> On Mon, Apr 13, 2009 at 1:20 PM, Vincent Siveton < > > [email protected]> > > > > >>> wrote: > > > > >>>> > > > > >>>> Hi Ian, > > > > >>>> > > > > >>>> 2009/4/13 Ian Boston <[email protected]>: > > > > >>>>> > > > > >>>>> I hate to bring it up again, but is it time to do a release on > > the > > > > >>>>> 1.0.x > > > > >>>>> branch ? > > > > >>>> > > > > >>>> I am agree with you. > > > > >>>> According Jira [1], we have 3 issues left and according the board > > > > >>>> report, we plan to do a release of 1.0.x in this quarter. > > > > >>>> So, could we fix them and make a release soon? Ping me if devs > > need > > > > >>>> help. > > > > >>>> > > > > >>>> Cheers, > > > > >>>> > > > > >>>> Vincent > > > > >>>> > > > > >>>> [1] > > > > >>> > > > > >>> > > > > >>> > > > > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310741&fixfor=12313553 > > > > >>>> > > > > >>> > > > > > > > > > > > > > > > > > >
