Jackrabbit 1.3.2 and 1.4 release planning

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

Hi,

I'm about to start working on the release plans for both Jackrabbit
1.3.2 and 1.4. I'll start by identifying issues in Jira to target
releases, and will follow up with more detailed release plans for both
releases later this week.

The 1.3.2 release will be a patch release from the 1.3 branch, and
will contain a set of new bug fixes from trunk. I expect to only
include fixes that have already been implemented and tested, but
please let me know if there's some high priority bug that's still
pending and you'd like to see it released soon. I'd like to push to
have the 1.3.2 release out already in early October.

The 1.4 release will be the next feature from Jackrabbit trunk. It
will contain all the recent work  on jackrabbit-core as well as both
the OCM and SPI layers as new release components. There are still a
number of issues open and I think I still need to open a few new
issues targeted for the release, so it might well be a few more months
before the release is ready. In any case I'd very much like to push
the release out during Q4 this year.

PS. We probably need to soon start making more comprehensive plans
also for the 2.0 release. At least we should come up with a plan on
what to do with Jackrabbit trunk after the 1.4 release. I'll follow up
on that once the 1.3.2 and 1.4 plans are more concrete.

BR,

Jukka Zitting

Re: Jackrabbit 1.3.2 and 1.4 release planning

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

Hi,

On 9/19/07, Julian Reschke <ju...@gmx.de> wrote:
> Sounds good to me. In particular, I think that once JCR2SPI has been
> integrated as a top-level project, we should try to work on reducing
> code duplication between it and the monolithic Jackrabbit.

+1 Something to keep in mind for post-1.4 planning.

BR,

Jukka Zitting

Re: Jackrabbit 1.3.2 and 1.4 release planning

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

Jukka Zitting wrote:
> ...
> The 1.4 release will be the next feature from Jackrabbit trunk. It
> will contain all the recent work  on jackrabbit-core as well as both
> the OCM and SPI layers as new release components. There are still a
> number of issues open and I think I still need to open a few new
> issues targeted for the release, so it might well be a few more months
> before the release is ready. In any case I'd very much like to push
> the release out during Q4 this year.
> ...

Sounds good to me. In particular, I think that once JCR2SPI has been 
integrated as a top-level project, we should try to work on reducing 
code duplication between it and the monolithic Jackrabbit.

BR, Julian

Re: Jackrabbit 1.3.2 and 1.4 release planning

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

Hi,

On 9/20/07, Esteban Franqueiro <ef...@bea.com> wrote:
> I would start by suggesting including the revisions that contain the
> fixes for JCR-862 (already commited by Jukka), JCR-962, JCR-978 and
> JCR-1082.

Thanks for the suggestions! JCR-862 and JCR-1082 are easy additions,
but JCR-962 and JCR-978 require more thought. More in a followup email
with the actual release plan.

BR,

Jukka Zitting

RE: Jackrabbit 1.3.2 and 1.4 release planning

[Esteban Franqueiro <ef...@bea.com>]

> I'm about to start working on the release plans for both Jackrabbit
> 1.3.2 and 1.4. I'll start by identifying issues in Jira to 
> target releases, and will follow up with more detailed 
> release plans for both releases later this week.
> 
> The 1.3.2 release will be a patch release from the 1.3 
> branch, and will contain a set of new bug fixes from trunk. I 
> expect to only include fixes that have already been 
> implemented and tested, but please let me know if there's 
> some high priority bug that's still pending and you'd like to 
> see it released soon. I'd like to push to have the 1.3.2 
> release out already in early October.

Sounds good to me too.
I would start by suggesting including the revisions that contain the
fixes for JCR-862 (already commited by Jukka), JCR-962, JCR-978 and
JCR-1082.
Regards,

Esteban Franqueiro
esteban.franqueiro@bea.com

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.