As long as "go back to #3" means feature-freeze-bug-squashing, it sounds like a good plan. You could iterate on additional RCs quicker depending on the open issue(s) and dev availability.
On Tue, Dec 22, 2015 at 1:53 AM, Misagh Moayyed <[email protected]> wrote: > Fellow Devs, > > > > Thought I provide a quick status update on the 4.2 dev line prior to the > nearing release candidate: > > > > 1. 63 issues closed, 111 pull requests closed since Sep 19 2015. > > 2. Tentative RC1 release date is Sunday Dec 27. > > a. 3-month iteration for a minor release. > > b. This may have to be delayed by a couple of days to finalize 1-2 > pending issues but so far, it seems like we are on schedule. > > 3. Wait about 4 weeks after RC1 to cut the next release, whether > that would be the GA or RC2. If GA, stop. Else, go back to #3 > > 4. Moving towards 4.3. Roadmap outlined on the wiki. > > > > All agreeable? > > > > Misagh > > -- > You received this message because you are subscribed to the Google Groups > "CAS Developer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/. > -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
