This doc is a really great summary: thank you Michal (and everyone else for the input). Super agree with starting from positive goals Marcel.
I've been asking around other Apache projects (Jackrabbit and Sling) and the Gentoo Linux guys. This problem is hard. The good news is: we're not the only ones that have run into it. The general consensus I'm getting back is to pin the versions sort of like we used to do. So the CLI is version 4 and then so are the platforms. This means "artificial" tagging of the repos in scenarios where one is ready to ship and others are not. It also means keeping MASTER green and deploy-able at all times by working from feature branches so that a release tag is a trivial annoyance instead of a full regression testing cycle. Versions are quite specifically for issue tracking so keeping that as simple as possible means higher quality bug reporting and (hopefully) resolution. Anyhow: look fwd to the conversation. Feels like we're making some progress. On Tue, Oct 7, 2014 at 12:01 PM, Marcel Kinard <cmarc...@gmail.com> wrote: > On Oct 7, 2014, at 2:13 PM, Michal Mocny <mmo...@chromium.org> wrote: > > > "Do not confuse developers" goal hopefully covers your points about > communication and information > > It partially covers it. > > To be more explicit, I'm trying to turn a negative goal into a positive > goal. So instead of "how do we not mess this up" I'm going for "what are we > really trying to achieve". > > And I'm also trying to twist a cordova-dev goal into a cordova-user goal. > I don't think we know what the ideal user experience is, so it is hard to > talk about how to achieve that. > >
