Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of reinstein.mike@gmail.com
 designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADVgkyPw1RGOUijaa0oyD5+tD3hQCEptbv9LScPrJjnsfBBY4A@mail.gmail.com>
References: 
 <CAM-DUcNnHUFqBm3-uDyLwetrHWrK2Amc+RvVJwerFcWjKkSxnw@mail.gmail.com>
	<CC91FE04.F2B1%fil@adobe.com>
	<CAM-DUcNCB2CZCDT-=OnzCAoaRYiTE7Zni9oBWWCgqFv+z_ccPQ@mail.gmail.com>
	<CADVgkyPw1RGOUijaa0oyD5+tD3hQCEptbv9LScPrJjnsfBBY4A@mail.gmail.com>
Date: Thu, 4 Oct 2012 13:36:41 -0400
Message-ID: 
 <CAM-DUcNfCKKbHU4vivF=dqmPfadmEUe=9Xdb6SeRWKgeGpS1pA@mail.gmail.com>
Subject: Re: moving towards semantic versioning for cordova?
From: Mike Reinstein <reinstein.mike@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54ee4eac04d3204cb3f328d

--bcaec54ee4eac04d3204cb3f328d
Content-Type: text/plain; charset=ISO-8859-1

> I don't think we have the luxury of knowing when something breaks

Granted, and that's not something we can really fix. *However, we can
identify when our API changes in breaking ways*.

-Mike

On Thu, Oct 4, 2012 at 6:37 AM, Brian LeRoux <b@brian.io> wrote:

> I personally don't think semver really did fix anything in ruby-land
> (but thats my opinion). Ruby has a crummy package system.The only one
> worse is Pythons.
>
> Anyhow, I added a little bit about our releases in the wiki [1] and a
> much longer post to the phonegap blog [2] to help folks better
> understand the rational. To echo Fil, I don't think we have the luxury
> of knowing when something breaks given the cat and mouse nature of the
> project relationship to mobile operating system vendors.
>
> [1] http://wiki.apache.org/cordova/CuttingReleases
> [2]
> http://phonegap.com/2012/04/12/rolling-releases-how-apache-cordova-becomes-phonegap-and-why/
>
> On Wed, Oct 3, 2012 at 11:44 PM, Mike Reinstein
> <reinstein.mike@gmail.com> wrote:
> > I certainly don't meant to rehash something that has been discussed
> > ad-nauseam. Nor am I advocating we change how often we release. I think
> the
> > key distinction is picking a version number that indicates breaking
> change,
> > compatible changes/new features, vs patches. Semantic versioning
> provides a
> > clean way to do specify this. In npm and ruby land, this has largely
> fixed
> > dependency hell, and has led to more reliable code re-use.
> >
> > Just a thought.
> >
> > http://semver.org
> >
> >
> > On Wed, Oct 3, 2012 at 5:37 PM, Filip Maj <fil@adobe.com> wrote:
> >
> >> This discussion again :)
> >>
> >> http://apache.markmail.org/thread/l2et3r5v35efprgd
> >>
> >>
> >> With a point release coming out every month or so that limits us to
> being
> >> able to "break" things every 10 months or so. With changing SDKs (see
> iOS
> >> 4.2, 5, and 6) sometimes we need to break things, like, asap.
> >>
> >> Other times we break things because we are assholes (from our users'
> point
> >> of view, at least :P )
> >>
> >> On 10/3/12 2:21 PM, "Mike Reinstein" <reinstein.mike@gmail.com> wrote:
> >>
> >> >I'm wondering if anyone else has given thought towards adopting
> semantic
> >> >versioning for our releases. In terms of making plugin development and
> >> >version adoption less painful, this might be a good move. Thoughts?
> >> >
> >> >-Mike
> >>
> >>
>

--bcaec54ee4eac04d3204cb3f328d--