Also discussed is eliminating the "even/odd" release numbering system.
I propose instead that we keep the main tree usable and stable and
passing all tests at all times (like Drizzle does), and development
and expermental features be in their own independent branches, and
they get merged into the main branch as they stablize.
Couple that with regular releases (every 2 weeks?), and get rid of
the "1.4 vs 1.5" discussion entirely.
On Aug 19, 2009, at 12:37 PM, Matt Ingenthron wrote:
Hi all,
Since a number of memcached contributors and client authors were in
one place at the Drizzle conference this week in Seattle we had a
short discussion about the release roadmap for stable and
development branches. I captured much of the discussion and it's
posted on the wiki:
http://code.google.com/p/memcached/wiki/DevelopmentRoadmap
It is prefaced with dormando's proposed release cycle, which I think
myself and Dustin have replied to. The roadmap items are also in a
proposal state, so if you have any thoughts, work you have in the
pipeline or things you'd like to see, please jump into the
conversation here on the list.
Thanks,
- Matt
--
Mark Atwood <http://mark.atwood.name>