From: Tim L. <guy...@gm...> - 2012-04-06 10:14:47
|
Brian Matherly wrote > > On 1/26/12, Benny Malengier <[hidden email]> wrote: >> I believe we should start the push for 3.4. > >> >> Step 1: Brian, can you make branch 3.4, <snip> > > I can do that any time. But typically, we don't create the maintenance > branch (3.4) until the code is "feature complete" in trunk. That way there > are only stability changes and bug fixed going in to the maintenance > branch. So if we expect to be feature complete by Feb 12, I think that > would be the day to make the 3.4 branch. I will wait until the 12th unless > there is a good reason to branch sooner. > >> Suggestions: >> no new features anymore 12 feb (so only bug fix in 3.4 after that) >> string freeze: 26 feb >> >> If we can cleanup the roadmap of 3.4 then in March, we can aim for a >> beta release end of March. >> >> Looking at the roadmap, we should also do a 3.3.2 before that. > What is the current state? Jérôme has done a fantastic job on bug triage (many thanks to him), but it has meant that quite a few things that are really either feature requests or annoyances that have existed for a long time have crept into the roadmap (except [1]) since your messages in January 2012. Given that there has been a string freeze since 26 Feb, no new features or major fixes have been introduced since then, so is it now time to progress the release? Is there any appetite for doing 3.3.2? Given apparent shortage of resources, I would be inclined not to proceed with that. Tim. [1] 5656 and 5667 are genuinely new bugs on the new features, I have fixed the first and will do the second soon. -- View this message in context: http://gramps.1791082.n4.nabble.com/prepare-gramps-3-4-tp4329757p4537071.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |