Jackrabbit Oak 0.1 release plan (Was: [jr3] Release roadmap)

[Jukka Zitting <ju...@gmail.com>]

Hi,

Now that we have the basics for Oak in place, it's time to start
setting some milestones. My proposal for the first one, as discussed
earlier, is:

On Thu, Feb 23, 2012 at 3:15 PM, Jukka Zitting <ju...@gmail.com> wrote:
> * 0.1 - March 2012
>  * Basic JCR and HTTP interfaces (Hello, World!)
>  * In-memory storage (no-need for persistence yet)
>  * Runnable jar for easy deployment
>  * Integration tests to verify the above

That should be pretty easy to achieve, especially since we're using
the existing microkernel work as a starting point. The main point at
this point is to get us to the habit of releasing early and often.

Given the branding concerns of the term Oak alone, we'll be using
(Apache) Jackrabbit Oak to refer to the release.

I propose we target the last week of March for this release, which
gives us two weeks to flesh out any missing details. Let's use the
"0.1" version label in Jira to record the more detailed set of
functionality that should be included in this release.

Does anyone want to volunteer as the release manager? This would be a
good opportunity for us to broaden RM experience within the Jackrabbit
PMC.

BR,

Jukka Zitting

Re: Jackrabbit Oak 0.1 release plan (Was: [jr3] Release roadmap)

[Julian Reschke <ju...@gmx.de>]

On 2012-03-08 17:38, Alex Parvulescu wrote:
> I'd like to volunteer for the role of RM.
>
> I never did this before, but I'm willing to give it a go if you guys are ok
> with it.
>
> best,
> alex

+1!

Re: Jackrabbit Oak 0.1 release plan (Was: [jr3] Release roadmap)

[Alex Parvulescu <al...@gmail.com>]

I'd like to volunteer for the role of RM.

I never did this before, but I'm willing to give it a go if you guys are ok
with it.

best,
alex


On Thu, Mar 8, 2012 at 1:59 PM, Jukka Zitting <ju...@gmail.com>wrote:

> Hi,
>
> Now that we have the basics for Oak in place, it's time to start
> setting some milestones. My proposal for the first one, as discussed
> earlier, is:
>
> On Thu, Feb 23, 2012 at 3:15 PM, Jukka Zitting <ju...@gmail.com>
> wrote:
> > * 0.1 - March 2012
> >  * Basic JCR and HTTP interfaces (Hello, World!)
> >  * In-memory storage (no-need for persistence yet)
> >  * Runnable jar for easy deployment
> >  * Integration tests to verify the above
>
> That should be pretty easy to achieve, especially since we're using
> the existing microkernel work as a starting point. The main point at
> this point is to get us to the habit of releasing early and often.
>
> Given the branding concerns of the term Oak alone, we'll be using
> (Apache) Jackrabbit Oak to refer to the release.
>
> I propose we target the last week of March for this release, which
> gives us two weeks to flesh out any missing details. Let's use the
> "0.1" version label in Jira to record the more detailed set of
> functionality that should be included in this release.
>
> Does anyone want to volunteer as the release manager? This would be a
> good opportunity for us to broaden RM experience within the Jackrabbit
> PMC.
>
> BR,
>
> Jukka Zitting
>

Re: Jackrabbit Oak 0.1 release plan (Was: [jr3] Release roadmap)

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Mar 8, 2012 at 1:59 PM, Jukka Zitting <ju...@gmail.com> wrote:
>> * 0.1 - March 2012
>>  * Basic JCR and HTTP interfaces (Hello, World!)
>>  * In-memory storage (no-need for persistence yet)
>>  * Runnable jar for easy deployment
>>  * Integration tests to verify the above

I think we're mostly done with all these items (I'd like to be further
with the last bit, but let's catch up in time for 0.2), so it's time
to cut the 0.1 release. I propose we cut the release candidate and
start the vote tomorrow on Friday.

Alex, you think you'd be up to the challenge? We'll need to replicate
the release build bits from /jackrabbit/trunk/pom.xml and then just
follow the steps from
http://jackrabbit.apache.org/creating-releases.html. I can help walk
you through it all. Or if you're busy I can take care of the 0.1
release so everything's in place for you to take over for later 0.x
releases.

BR,

Jukka Zitting