There is one big, crippling bug in the released plugman: If you add a capability with Xcode 5, you can no longer plugman.prepare, and therefore not rebuild your app.
I don't think releasing them separately is a good idea. I'm prepared to wait until 3.2 to release both, but only if that's less than a week away. Otherwise I propose releasing both today, targeting 3.1 still, and then we can do another release with Cordova 3.2. Josh, we can do a release of just the tools whenever they're ready, so there's not much to be gained by spending an extra week fixing a dozen more bugs. We might as well release now, fix more bugs, and release again next week. Braden On Fri, Nov 8, 2013 at 1:15 PM, Steven Gill <stevengil...@gmail.com> wrote: > With 3.2 looming, it might be better to release plugman along with 3.2. > That way we don't tell our users to update now, and again when 3.2 comes > out. Unless of course the fix in plugman is critical. > > > On Fri, Nov 8, 2013 at 10:04 AM, Marcel Kinard <cmarc...@gmail.com> wrote: > > > I was reminded of > > http://wiki.apache.org/cordova/VersioningAndReleaseStrategy which says > it > > is weekly, with cli and plugman together. Works for me. > > > > On Nov 8, 2013, at 12:18 PM, Marcel Kinard <cmarc...@gmail.com> wrote: > > > > > What is the trigger for doing a plugman release? As needed per > > bugs/features, or should it be at the same time as cli? I'd suggest the > > latter, since cli has either a pseudo-dependency or real dependency > > (depending on how you look at it) on plugman. > > > > >
