You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucy.apache.org by Logan Bell <lo...@gmail.com> on 2012/05/04 04:07:11 UTC
[lucy-dev] 0.3.1 Release
Hey guys,
I know earlier in April there was a thread going around to release 0.3.1 of
Lucy. However, I haven't seen a vote for a release yet nor any further
comment on this. I would be happy to volunteer to do this, unless someone
else was already planning on getting the release started? I just need
instructions on the appropriate way of doing this and whatever the process
is, I'll be happy to do it.
Let me know either way, I'm anxious to start using 0.3.1.
Cheers,
Logan
Re: [lucy-dev] 0.3.1 Release
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, May 4, 2012 at 6:13 AM, Peter Karman <pe...@peknet.com> wrote:
> looks like that stuff didn't get moved from the incubator space:
>
> http://lucy.apache.org/download.html
>
> links to
>
> http://www.apache.org/dist/incubator/lucy/KEYS
>
> etc
Yeah, according to the Incubator's graduation guidelines, you're not supposed
to move your incubating release artifacts -- just delete them after you make
a release as a TLP:
http://incubator.apache.org/guides/graduation.html#transfer
5. Distribution mirrors
After you have a release at your new home (/dist/${project}/ area),
remove any distribution artefacts from your old
/dist/incubator/${project}/ area. Remember from the mirror guidelines
that everything is automatically added to archive.apache.org anyway.
The KEYS file is special, since that's the only item in our dist area not tied
to a specific release. We'll need to append Logan's public key and then copy
the file to the new location. Nothing else should migrate.
> Not sure if that requires infra help or not to move.
We need someone with infra permissions to perform the
`mkdir /www/www.apache.org/dist/lucy` incantation on people.apache.org, so
I've opened a ticket:
https://issues.apache.org/jira/browse/INFRA-4745
However, we can still move forward while waiting for infra to complete that
task. As a workaround, Logan can make the modified KEYS file available from
his home directory via <http://people.apache.org/~logie/KEYS>.
As an aside, it seems that we have not been as fastidious as we could have
been about zapping old releases. (That includes yours truly, since I didn't
zap 0.2.0 after releasing 0.2.1.) Apache policy is to have only the most
recent release for a given line in the dist area, and we should try to be
better about that going forward.
Marvin Humphrey
Re: [lucy-dev] 0.3.1 Release
Posted by Peter Karman <pe...@peknet.com>.
Logan Bell wrote on 5/4/12 1:00 AM:
> Righto. I read through the documentation, generated/published my gnupg key,
> and generated my commands.txt file. However on the first step in
> commands.txt it mentions that I should publish to
> http://www.apache.org/dist/lucy/KEYS, however that url gives me a 404. The
> document location on people.apache.org doesn't seem to exist as well /www/
> www.apache.org/dist/lucy.
>
> Should I reach out to infra to help solve this or did this move to
> somewhere else post graduation?
>
looks like that stuff didn't get moved from the incubator space:
http://lucy.apache.org/download.html
links to
http://www.apache.org/dist/incubator/lucy/KEYS
etc
Not sure if that requires infra help or not to move.
--
Peter Karman . http://peknet.com/ . peter@peknet.com
Re: [lucy-dev] 0.3.1 Release
Posted by Logan Bell <lo...@gmail.com>.
Righto. I read through the documentation, generated/published my gnupg key,
and generated my commands.txt file. However on the first step in
commands.txt it mentions that I should publish to
http://www.apache.org/dist/lucy/KEYS, however that url gives me a 404. The
document location on people.apache.org doesn't seem to exist as well /www/
www.apache.org/dist/lucy.
Should I reach out to infra to help solve this or did this move to
somewhere else post graduation?
Thanks,
Logan
On Thu, May 3, 2012 at 8:18 PM, Marvin Humphrey <ma...@rectangular.com>wrote:
> On Thu, May 3, 2012 at 7:07 PM, Logan Bell <lo...@gmail.com> wrote:
> > I know earlier in April there was a thread going around to release 0.3.1
> of
> > Lucy. However, I haven't seen a vote for a release yet nor any further
> > comment on this. I would be happy to volunteer to do this, unless someone
> > else was already planning on getting the release started?
>
> Eh, Nick's been too busy writing awesome code to follow through on the RM
> business... You're hired!
>
> (Perhaps we can persuade Nick to serve as RM for 0.4.0, which will have a
> ton
> of his new code in it.)
>
> > I just need instructions on the appropriate way of doing this and
> whatever
> > the process is, I'll be happy to do it.
>
> The first phase of getting a release ready is a collective, community
> responsibility (so that we share the load and don't overburden the RM):
> take
> care of all the tasks listed here:
>
> http://wiki.apache.org/lucy/ReleasePrep
>
> I've now completed all of them:
>
> * The RAT report is still wedged, but as this is the 0.3.x branch and no
> new files have been added since 0.3.0, we're all good. (For the
> record,
> I opened a JIRA ticket today and hope to get the buildbot un-wedged:
> <https://issues.apache.org/jira/browse/INFRA-4741>).
> * The issue tracker is clean.
> * Copyright notices are up-to-date.
> * The CHANGES file has a new entry (date still to be filled in by RM).
> * LICENSE and NOTICE are fine (no changes since 0.3.0 that would require
> mods).
> * The 0.3.x branch passes tests for me on OS X, Cygwin, Strawberry Perl
> and ActivePerl/MSVC.
> * The test_valgrind target passes on OS X.
>
> The next steps are for the Release Manager. The guide is here:
>
> http://wiki.apache.org/lucy/ReleaseGuide
>
> From a high level, here are the stages of creating a release:
>
> 1. Branch and tag the release candidate within version control.
> 2. Build and stage the release artifacts.
> 3. Vote.
> 4. Publish.
> 5. Announce.
>
> The specifics of each stage are covered in release_commands.pl.
>
> Most of the work now involves running commands generated by a script:
>
> $repos/devel/bin/release_commands.pl
>
> However, since this will be your first time as RM, the ReleaseGuide also
> lists
> some reference materials you may want to look over.
>
> So, look over the ReleaseGuide wiki page and run release_commands.pl --
> then feel free to either proceed or to ask questions here or on #lucy_dev!
>
> Marvin Humphrey
>
Re: [lucy-dev] 0.3.1 Release
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Thu, May 3, 2012 at 7:07 PM, Logan Bell <lo...@gmail.com> wrote:
> I know earlier in April there was a thread going around to release 0.3.1 of
> Lucy. However, I haven't seen a vote for a release yet nor any further
> comment on this. I would be happy to volunteer to do this, unless someone
> else was already planning on getting the release started?
Eh, Nick's been too busy writing awesome code to follow through on the RM
business... You're hired!
(Perhaps we can persuade Nick to serve as RM for 0.4.0, which will have a ton
of his new code in it.)
> I just need instructions on the appropriate way of doing this and whatever
> the process is, I'll be happy to do it.
The first phase of getting a release ready is a collective, community
responsibility (so that we share the load and don't overburden the RM): take
care of all the tasks listed here:
http://wiki.apache.org/lucy/ReleasePrep
I've now completed all of them:
* The RAT report is still wedged, but as this is the 0.3.x branch and no
new files have been added since 0.3.0, we're all good. (For the record,
I opened a JIRA ticket today and hope to get the buildbot un-wedged:
<https://issues.apache.org/jira/browse/INFRA-4741>).
* The issue tracker is clean.
* Copyright notices are up-to-date.
* The CHANGES file has a new entry (date still to be filled in by RM).
* LICENSE and NOTICE are fine (no changes since 0.3.0 that would require
mods).
* The 0.3.x branch passes tests for me on OS X, Cygwin, Strawberry Perl
and ActivePerl/MSVC.
* The test_valgrind target passes on OS X.
The next steps are for the Release Manager. The guide is here:
http://wiki.apache.org/lucy/ReleaseGuide
From a high level, here are the stages of creating a release:
1. Branch and tag the release candidate within version control.
2. Build and stage the release artifacts.
3. Vote.
4. Publish.
5. Announce.
The specifics of each stage are covered in release_commands.pl.
Most of the work now involves running commands generated by a script:
$repos/devel/bin/release_commands.pl
However, since this will be your first time as RM, the ReleaseGuide also lists
some reference materials you may want to look over.
So, look over the ReleaseGuide wiki page and run release_commands.pl --
then feel free to either proceed or to ask questions here or on #lucy_dev!
Marvin Humphrey