community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian>
Subject Re: How can we support a faster release cadence?
Date Fri, 14 Feb 2014 18:01:53 GMT
Hey Alex, some answers inline:

> But what is Cordova's plan if a major defect is found too late for the
> "schedule"?

We use branches so cherry picking features in, and out, of release branches
happens on occasion. Its pretty easy and clean w/ git to do this.

> Would you skip a release?

No. Though we have delayed them. And that happens fairly often. We're not
crazy restrictive about the timing. We *aim* for 10 MINOR releases (with 10
companion rc candidates) and 1 MAJOR a year. Other projects, with larger
communities than ours, have to segment into separate channels on a 6 week
cadence. I could see Cordova getting there someday if this mobile thing
continues to grow.

This is just talking about our platforms. We have other assets like plugins
and our command line interface which can see weekly incremental updates. In
other realities I participate in we ship daily. Revision control,
continuous integration, and rigor in testing make this sort of thing not
only possible but financially desirable for commercial web properties.

> And what if something more subjective comes up like a some user showing up
> at the last minute and saying they don't like the usability or name of
> something and a grass roots movement grows around it.

Oh, those sorts of things happen and are welcome. If its good we'll do it.
If it doesn't fit we won't. That diversity makes open source the better
model, to me.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message