Arrrrgh.... It turns out I do not have karma to undertake this release Stian!
lmcgibbn@LMC-032857 /usr/local/incubator-commonsrdf/commons(master) $ svn ci -m "Add lewismc to Commons KEYS" Sending KEYS Transmitting file data .svn: E195023: Commit failed (details follow): svn: E195023: Changing file '/usr/local/incubator-commonsrdf/commons/KEYS' is forbidden by the server svn: E175013: Access to '/repos/dist/!svn/txr/13444-bif/release/commons/KEYS' forbidden svn: E175002: Additional errors: svn: E175002: PUT of '/repos/dist/!svn/txr/13444-bif/release/commons/KEYS': 403 Forbidden As Champion I do not have commit karma for the repository or for adding my KEY to the KEYS file at https://dist.apache.org/repos/dist/release/commons/KEYS Are you able to take the roll of release manager? Sorry about that. Lewis On Wed, Apr 27, 2016 at 9:16 AM, Stian Soiland-Reyes <[email protected]> wrote: > Hurray! > > Agreed that Commons RDF should be pretty straight forward. > > On 27 April 2016 at 15:50, Lewis John Mcgibbney > <[email protected]> wrote: > > Hi Stian, > > Yes I am happy to be release manager. I think I will have time tonight to > > run a release. > > I'll get you on list if it goes hellishly... however it looks pretty > > straight forward so it should be OK. > > Thanks > > > > On Mon, Apr 25, 2016 at 10:43 AM, Stian Soiland-Reyes <[email protected]> > > wrote: > >> > >> Hi - are you still OK to be Release Manager? > >> > >> Let me know if you have any questions! We can have a chat by Skype if > you > >> like. > >> > >> https://taverna.incubator.apache.org/community/releasing might be a > >> more readable approach - just substitute "taverna" with "commonsrdf" > >> > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: Stian Soiland-Reyes <[email protected]> > >> Date: 21 April 2016 at 07:39 > >> Subject: Re: Next Release for Commons RDF > >> To: dev <[email protected]> > >> > >> > >> Great if you want to have a go, Lewis! > >> > >> Agree we should document the release process. > >> > >> https://commons.apache.org/releases/ > >> > >> Should generally work, e.g. > >> > >> Try a mvn clean deploy of the snapshot first to see if you have Nexus > >> permissions. > >> > >> mvn -Prelease release:prepare > >> mvn -Prelease release:perform > >> > >> Make sure version number is 0.2.0-incubating > >> > >> Tag should include -RC1 > >> > >> Then you Close the repo in Nexus. > >> > >> After build, target should contain > >> apache-commons-rdf-0.2.0-incubating.tar.gz/.zip and .asc .sha1 .md5: > >> which you can push with svn to the dist.apache.org area > >> dev/incubator/commonsrdf/ > >> > >> And then a VOTE email here with the checksums, commit id and URLs of > >> dist and staging repo. > >> > >> I don't think you need to stage a website for this RC as our site and > >> javadoc is already made from 0.2.0-SNAPSHOT. > >> > >> We have not used the commons build plugin to update download pages etc > >> yet, (I'm not sure if it works outside the commons dist area) so those > >> steps we can do manually. > >> > >> On 19 Apr 2016 5:09 a.m., "Lewis John Mcgibbney" > >> <[email protected]> wrote: > >> > > >> > Hi Stian, > >> > > >> > On Sat, Apr 16, 2016 at 5:16 AM, < > >> > [email protected]> wrote: > >> > > >> > > > >> > > From: Stian Soiland-Reyes <[email protected]> > >> > > To: dev <[email protected]> > >> > > Cc: > >> > > Date: Sat, 16 Apr 2016 13:15:48 +0100 > >> > > Subject: Re: Next Release for Commons RDF > >> > > +1 > >> > > > >> > > If we can settle on Quad (pull request 19) - then we can include > that > >> > > as well which makes a nice release - otherwise let's just do a point > >> > > release with the smaller improvements. > >> > > > >> > > >> > I would be favorable to a point release 0.2? > >> > > >> > > >> > > > >> > > > >> > > The parser API branch need a bit more work to settle, so I would not > >> > > want to delay a release for that. > >> > > > >> > > >> > Agreed. > >> > > >> > > >> > > > >> > > > >> > > I can be RM unless you want to have a go, Lewis? > >> > > > >> > > >> > Is the process documented anywhere? If not then it would be good to > >> > capture > >> > it this time around. I have no objection to being a RM, however if you > >> > made > >> > the 0.1 release and are able to document how 0.2 should be done then I > >> > would prefer that. > >> > Thanks > >> > Lewis > >> > > >> > > >> > > > >> > > > >> > > On 15 April 2016 at 05:43, Lewis John Mcgibbney > >> > > <[email protected]> wrote: > >> > > > Hi Folks, > >> > > > I've seen quite a bit of activity recently which is nice. > >> > > > Is there any appetite for a release? > >> > > > Thanks > >> > > > Lewis > >> > > > > >> > > > -- > >> > > > *Lewis* > >> > > > >> > > > >> > > > >> > > -- > >> > > Stian Soiland-Reyes > >> > > Apache Taverna (incubating), Apache Commons RDF (incubating) > >> > > http://orcid.org/0000-0001-9842-9718 > >> > > > >> > > > >> > > > >> > > >> > > >> > -- > >> > *Lewis* > >> > >> > >> -- > >> Stian Soiland-Reyes > >> Apache Taverna (incubating), Apache Commons RDF (incubating) > >> http://orcid.org/0000-0001-9842-9718 > > > > > > > > > > -- > > Lewis > > > > -- > Stian Soiland-Reyes > Apache Taverna (incubating), Apache Commons RDF (incubating) > http://orcid.org/0000-0001-9842-9718 > -- *Lewis*
