COmanage Developers List

[Benn Oshrin <>]

Given Scott is on vacation, I'll be in LA, and Heather is probably just
plain exhausted, let's skip Friday's call.

Instead, please assemble a list of JIRA issues that you think should be
blockers for 0.9.4 and then 1.0.0. My current thought is to finish up
CO-310 and a few other small/critical/low hanging issues and then tag
0.9.4 probably mid-to-late next week. If there's anything you want
included before I tag, be sure to include it in your list, or flag it as
a Blocker in JIRA.

The theme of 0.9.4 is "it's been almost 4 months, it's time to tag".

For 1.0.0, I'd like to keep the scope fairly small. My primary task will
be "installation simplification", as well as any fixes that shake out of
0.9.4 or are sponsored by a client. I'm thinking we could tag 1.0.0 as
early as mid July.

The theme of 1.0.0 is "it's been almost 5 years, it's time to tag".

Anything you don't enumerate in a list for 0.9.4 or 1.0.0 will probably
get swept into the FUTURE bucket.

Post-1.0.0, we'll adopt semantic versioning. We'll do patch releases as
needed based on whatever bugs we've identified. For minor versions,
perhaps we can use our dev meetings to review the backlog (ie: FUTURE)
and scope and prioritize issues based on funding or other pressing
needs. It's not really clear what a major version is for us yet...
probably Cake 3.

Comments on the overall strategy are also welcome.

Thanks,

-Benn-