On 22/01/2016 10:02, Julian Reschke wrote: > > 1) Do we need to schedule a new stable Jackrabbit release? Right now > we use 2.11.3 which is labeled "unstable release". Right. Forgot about that. We have two options: branch yet again jackrabbit, always use trunk only from now on.
As we're going towards a maintenance hell in terms or version I'm for using only trunk for jackrabbit. So having only 2.11.x. If we branch we'll have to maintain as of now: JR - 2.2, 2.4, 2.6, 2.8, 2.10, 2.12, trunk Oak - 1.0, 1.2, 1.4, trunk > > 2) Once we have a new branch, we'll have to maintain three stable old > branches. We need to figure out a end-of-life strategy for Oak 1.0 > sooner or later. (Which reminds me we need to do that for a few > ancient Jackrabbit branches as well). the topic is quite intricate, specially for Oak. If I restrict the discussion to JR and by looking at the last updates from our downloads page I can see: - OCM 2.0.0 (10-July-2012). Do we still maintain this project? There were a recent email about it. - Jackrabbit 2.2.13 (04-October-2012) - Jackrabbit 2.4 (Oct 24, 2013) - Jackrabbit 2.6.5 (December 2nd, 2013) - Jackrabbit 2.8 (June 4th, 2015) - Jackrabbit 2.10.1 (May 21st, 2015) IMO we should drop the support for 2.2 and 2.4 at least. Ideally 2.6 as well. thoughts? Davide
