Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: 
 <CAMT1KGNzt1rO9XH2B24G8oz=7gpyCUXe4-LGJZe5CTqNMq+ObA@mail.gmail.com>
References: 
 <CADVgkyMxM=+cRgN20dM2HBzqtFxohefn_ih_qod=WPnCQnTczw@mail.gmail.com>
	<CAMT1KGNzt1rO9XH2B24G8oz=7gpyCUXe4-LGJZe5CTqNMq+ObA@mail.gmail.com>
Date: Tue, 27 Mar 2012 15:17:40 -0700
Message-ID: 
 <CADVgkyMzCvAyc-BUTB8sygkrGFQUy_RSMOnN6oUcPGbvo7uLHw@mail.gmail.com>
Subject: Re: 1.7 1.8 1.9 2.0rc planning, priorities, and plugins
From: Brian LeRoux <b@brian.io>
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Bryce you think we start moving to >monthly sprints or just take on
less each sprint?

I'd rather we kept the release train style though perhaps move to odd
numbers fix bugs and even numbers are new features... though in the
case of other projects I rarely see this actually work as advertised.


On Tue, Mar 27, 2012 at 2:51 PM, Bryce Curtis <curtis.bryce@gmail.com> wrot=
e:
> Add to 1.6-1.7
> =A0- More focus on docs, guides, examples, maybe native plugin API
> =A0- Advanced notice of what's planned to be deprecated and when, then ge=
t
> community feedback before breaking compatibility
>
> 1.7
> =A0- CordovaView (Android)
>
> 1.6-2.x
> =A0- Emphasize testing to ensure no regression.
> =A0- Quality releases are more important than schedule.
>
> On Tue, Mar 27, 2012 at 4:36 PM, Brian LeRoux <b@brian.io> wrote:
>
>> The big theme this year has been migration to an architecture more
>> friendly to plugins with our ultimate goal of the end user being able
>> to compose their own version of Cordova with only the APIs they need.
>> Essentially our release would slowly strip down to webview+bridge and
>> then we'd maintain an official set of plugins separately (which are
>> comprised of the device apis we target today).
>>
>> From a high level to make this happen we need
>>
>> 1.6-1.7 March/April
>>
>> - a consistent js impl across platforms (almost there)
>>
>> 1.7-1.9 April/May/June
>>
>> - tooling for plugin package validation, installation, and removal
>> (andrew prototyping this)
>> - refactor of (possibly) coho to allow for composing a release of
>> particular plugins
>> - document correct procedure for generating a plugin or, better, have
>> a tool that does it
>>
>> 2.0.0rc1 July 15
>>
>> Post 2.x
>> - automate plugin discovery ala npm/cpan/rubygems/pypi/etc
>> - remove plugins to discreet repos and use discovery mechanism to
>> compose different releases
>>
>> * * *
>> How does that fit with your thoughts on Apache Cordova? Future
>> releases can target, with surgical precision, particular APIs by way
>> of plugin with a faster prototype cycle and we can then also start
>> looking at more polish type activities like bridge performance, test
>> automation and the such.
>>