Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 bernd.fondermann@googlemail.com designates 209.85.215.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=wHerFwgAGehwQbZ/HBVlFW3sW7VbkXnECLnQ/eTeqHBAymnlLADtU2srzDdAE2ANSu
         CZ035EWSJG6A6nZwj8NinFq1qbdYiSE7GvgB4yqLwrAK8xy9yTre48MqbLVqKcC8Ol+M
         004mJ6QJLbpibnSzp0y27CY//kc5MoPWIFFyo=
MIME-Version: 1.0
In-Reply-To: <4CF595D6.4050701@gmail.com>
References: <4CF595D6.4050701@gmail.com>
Date: Wed, 1 Dec 2010 11:16:33 +0100
Message-ID: <AANLkTi=DqZQx2mFi6zQbUTGnFj+UNuH7sKwKYb81eHC3@mail.gmail.com>
Subject: Re: r0.1 tracking in JIRA
From: Bernd Fondermann <bernd.fondermann@googlemail.com>
To: isis-dev@incubator.apache.org, dan@haywood-associates.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Note from the peanut gallery: Please make sure that 'lead' is not
interpreted as 'having code ownership', or 'is telling/demanding how
that specific part of the project should evolve'. Leaving modules
explicitly without a shepherd could attract new people to jump in -
and growing community is one of the goals of Incubation.

Thanks,

  Bernd

On Wed, Dec 1, 2010 at 01:24, Dan Haywood <dkhaywood@gmail.com> wrote:
> All,
> Nour, Rob and myself had an skype call yesterday evening regarding an
> approach to manage the v0.1 release. =A0The plan we came up with was to u=
se
> JIRA, with a ticket for each main component (or group of components). =A0=
I'm
> posting this here for visibility/comments.
>
> The proposal for the 0.1 release is to create a JIRA ticket for each of t=
he
> following:
>
> Core (Lead: Dan Haywood)
> AppLib (Lead: Dan Haywood)
> Defaults (Lead: Dan Haywood)
> Alternatives: Bytecode (Lead: Dan Haywood)
> Alternatives: Embedded (Lead: Dan Haywood)
> Alternatives: ObjectStore: NoSQL (Lead: Robert Matthews)
> Alternatives: ObjectStore: SQL (Lead: Kevin Meyer)
> Alternatives: ObjectStore: XML (Lead: Robert Matthews)
> Alternatives: ProfileStore: XML (Lead: Robert Matthews)
> Alternatives: ProgModel: Groovy (Lead: Dan Haywood)
> Alternatives: ProgModel: Wrapper (Lead: Dan Haywood)
> Alternatives: Security: LDAP (Lead: Robert Matthews)
> Viewer: BDD (Lead: Dan Haywood)
> Viewer: DnD (Lead: Robert Matthews)
> Viewer: HTML (Lead: Robert Matthews)
> Viewer: JUnit (Lead: Dan Haywood)
> Viewer: Restful (Lead: Dan Haywood)
> Viewer: Scimpi (Lead: Robert Matthews)
> Viewer: Wicket (Lead: Dan Haywood)
>
> NB: this combines all the core components into a single ticket; all the
> default components into a single ticket, it excludes jpa objectstore,
> mongodb objectstore, and remoting.
>
> Each of these tickets will be used to track the status of:
> 1- Documentation (docbook PDF + site APT)
> 2- Review package names, Maven artifacts IDs, copyright notices.
> 3- For the alternatives and viewers, should have a module in the
> support/prototype project
>
> We also need a ticket for the archetype itself, to reverse engineer from
> support/prototype into an archetype.
>
> When all of these tickets are complete, then - in theory - r0.1 will be
> ready for release.
>
>
> If everyone is happy with this, then Nour has volunteered to enter these
> tickets into JIRA and to track the status through to v0.1 release.
>
> Cheers
> Dan
>
>
>