On 2016-01-21 09:23, Davide Giannella wrote:
Hello everyone,
as we're approaching to a year since we released Oak 1.2 here's a
proposal of soft-dates for releasing 1.4. With soft-dates I mean they
could shift a bit around depending on issue needs.
The team already went through the exercise of scheduling what's not so
important for 1.6.
# Major Feature Freeze - 1st February - Oak 1.3.15
Progressive commit slow down and risk-control starting after 1.3.15 cut.
# 1.4 Branching - 29th February - Oak 1.4.0 - Oak 1.5.0
Branching of 1.4, release 1.4.0, release 1.5.0. They should all be the
same code from an Oak perspective.
From here on we'll resume the regular bi-weekly unstable cut (1.5.x) and
a stable cut every 3 weeks (1.0, 1.2, 1.4).
Cheers
Davide
+1 in general.
Comments:
1) Do we need to schedule a new stable Jackrabbit release? Right now we
use 2.11.3 which is labeled "unstable release".
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).
Best regards, Julian
