lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Logan Bell <>
Subject Re: [lucy-dev] 0.3.1 Release
Date Fri, 04 May 2012 06:00:03 GMT
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, however that url gives me a 404. The
document location on doesn't seem to exist as well /www/

Should I reach out to infra to help solve this or did this move to
somewhere else post graduation?


On Thu, May 3, 2012 at 8:18 PM, Marvin Humphrey <>wrote:

> On Thu, May 3, 2012 at 7:07 PM, Logan Bell <> 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:
> 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:
>      <>).
>    * 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:
>    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
> Most of the work now involves running commands generated by a script:
>    $repos/devel/bin/
> 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 --
> then feel free to either proceed or to ask questions here or on #lucy_dev!
> Marvin Humphrey

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message