Mailing-List: contact lucy-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: lucy-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Mattmann, Chris A (388J)" <chris.a.mattmann@jpl.nasa.gov>
To: "lucy-dev@incubator.apache.org" <lucy-dev@incubator.apache.org>
Date: Mon, 22 Nov 2010 15:51:51 -0800
Thread-Topic: [lucy-dev] 0.1-incubating release timeline?
Thread-Index: AcuKoDxatmlm6Oy1TWi8chf0Pd0qbw==
Message-ID: <942CCA46-45E2-4F5D-8727-4989E97B20C2@jpl.nasa.gov>
References: <0158239F-406E-4487-ABCA-4846267C9A5C@jpl.nasa.gov>
 <20101122015131.GA4532@rectangular.com>
In-Reply-To: <20101122015131.GA4532@rectangular.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [lucy-dev] 0.1-incubating release timeline?

+1 to the below, with the exception of implementing the branding requiremen=
ts. I don't think that's mandatory for a release...it's really independent =
of it (though mandatory).

Cheers,
Chris

On Nov 21, 2010, at 5:51 PM, Marvin Humphrey wrote:

> On Sun, Nov 21, 2010 at 09:55:43AM -0800, Mattmann, Chris A (388J) wrote:
>> Hey Guys,
>>=20
>> I may be way off here, but it seems like:
>>=20
>> 1. the code has been ported to ASLv2
>> 2. the Software Grant is in place
>> 3. issues are getting resolved and work is being done
>=20
> Sounds like we need a TODO list.  Here's what I can think of:
>=20
> Mandatory:
>=20
>    * Either resolve <https://issues.apache.org/jira/browse/LEGAL-86>
>      favorably or replace JSON::XS and Parse::RecDescent.
>    * Review other CPAN dependencies (these were enumerated in a comment o=
n
>      LUCY-121 at <http://s.apache.org/kQ>).
>    * Work out release numbering mechanics (Perl version numbers are
>      complicated).
>    * Fully implement ASF branding requirements. =20
>    * Tighten up the code base a bit.  (Ensure that the "test_valgrind" bu=
ild
>      target passes, fix a couple portability issues, etc.)
>    * Adapt the "dist" build target for Apache release.  (Right now it tar=
gets
>      a CPAN release and has a few other problems.)
>    * Establish a "rat" build target so that we can demonstrate to any
>      interested Incubator PMC member that we have accounted for the licen=
sing
>      of all files.  (Otherwise RAT will flag our sample US constitution
>      files, the Snowball C files, etc.)
>=20
> Optional:
>=20
>    * Publish HTML export of documentation on website.
>    * Migrate website to new Apache CMS.
>    * Work out TextType/FullTextType/StringType refactor.=20
>    * Move some classes around (all Analyzers underneath LucyX?  Nothing u=
nder
>      LucyX?  Factor SnowballStopalizer out of Stopalizer?)
>=20
> It would be nice to have docs hanging off of our homepage, the way that
> <http://www.rectangular.com/kinosearch/docs/devel/> hangs off the KinoSea=
rch
> homepage.  It's not mandatory because as soon as we upload to CPAN we can
> point people at <http://search.cpan.org/perldoc?Lucy> (see
> <http://search.cpan.org/perldoc?KinoSearch> for reference.)  However, I d=
o
> believe that an inviting, clean web presence is an important recruitment =
tool,
> and I would like to at least revisit the website prior to release.
>=20
> The refactoring isn't mandatory because of our unstable trunk policy.  It=
's a
> nice-to-have because if we get to it before initial release there would n=
ever
> be any mindspace occupied by FullTextType and StringType within the
> Lucyverse... but we can put off such things for now.
>=20
>> That said, how far are we off from a 0.1-incubating release? Would it be
>> fair to say within a month?=20
>=20
> If LEGAL-86 gets resolved favorably and we can continue to use JSON::XS a=
nd
> Parse::RecDescent, then yes.  If we have to replace them, probably not.
>=20
> I thought LEGAL-86 was pretty much a gimme -- I'm under the impression th=
at
> other Apache projects have specified Perl-licensed CPAN prerequisites as
> system dependencies, which is what LEGAL-86 formally requests.  Since it =
has
> gone unresolved, though, I've started working up replacement components b=
ased
> on the Lemon parser generator.
>=20
> We'll have to ditch JSON::XS eventually anyway, since no other host langu=
age
> binding will be able to use it.  However, I would prefer to address repla=
cing
> it after the 0.1-incubating release, since it's known and stable and I'm =
not
> in a hurry to muck with something that Just Works.
>=20
> Parse::RecDescent is a build-time-only dependency -- it's needed by
> Clownfish::Parser.  (It is also referenced in a Cookbook recipe which we =
can
> zap if need be.)  Since Clownfish generates platform-independent C code, =
we
> have the option of shipping the autogenerated C files and omitting Clownf=
ish
> -- working around the Parse::RecDescent dependency.  However, my preferen=
ce
> would be to ship Clownfish.
>=20
>> I think if that's the case, I can help clean up JIRA and get stuff organ=
ized
>> for a release. I'd even volunteer to be the release manager if someone
>> trained me on how to build, test and package up the system.
>=20
> Peter and I should probably start a ReleaseTODO wiki page, like most Apac=
he
> projects seem to have.
>=20
> The release manager will need enough Perl-fu to install a couple CPAN
> prerequisites and will need to be on a Unixy OS for now.  Lucy should bui=
ld
> and test fine for them.  From my perspective, the difficulties in prepari=
ng
> our first release all have to do with unfamilar Apache rituals.  The pack=
aging
> should be handled seamlessly by the "dist" build target once it is repair=
ed
> and adapted, so the RM will not have a lot to do there.
>=20
> Marvin Humphrey
>=20


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++