Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: <CD0B1C3E.14E03%fil@adobe.com>
References: 
 <CAOBL_k5P=dKT_mo0arKfu6Z8s_FYx0tfwGx=qr6uv=H2dO3U1Q@mail.gmail.com>
	<CD0B1C3E.14E03%fil@adobe.com>
Date: Thu, 3 Jan 2013 11:40:42 -0800
Message-ID: 
 <CADVgkyM=DBb-hNhk7xAeKZdw2hTgdPpk8+dBQ1O3dEhjzd=3Tg@mail.gmail.com>
Subject: Re: content for 2.4?
From: Brian LeRoux <b@brian.io>
To: dev@cordova.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Joe: think API audits should start after we remove the APIs from core
so we can version plugins independently.

Fil: yes, that'd be awesome.

Marcel: first priority for the long view on 3.x is a light core w/ no
APIs. The tools aren't there yet to do this so continued work there in
2.4 needed. If you want to see the particular feature-set for a
release you can look in JIRA and whats been assigned. In Cordova the
committers assign their own issues (w/ our goals in mind). I would
imagine that 2.4 will have many bug fixes related to recent additions
like InAppBrowser which debuts this week (or so) in 2.3


On Thu, Jan 3, 2013 at 11:30 AM, Filip Maj <fil@adobe.com> wrote:
> I'd like to include cordova-cli into our full source release in 2.4.0.
>
> On 1/3/13 10:22 AM, "Joe Bowser" <bowserj@gmail.com> wrote:
>
>>I believe that 2.4.0 is the release where we refactor our APIs and
>>clean things up.
>>
>>On Thu, Jan 3, 2013 at 6:57 AM, Marcel Kinard <cmarcelk@gmail.com> wrote:
>>> Aside from bug fixes, are there ideas on what you think will be tackled
>>>for
>>> 2.4? I suspect at least some of you have ideas in your head that I
>>>haven't
>>> fully seen written here. I'm just looking for a high-level bullet list.
>>>I'm
>>> not looking for promises, instead just to set some rough expectations
>>>for
>>> Cordova consumers.
>>>
>>> I see the roadmap wiki page organized by quarter, but I'm looking for
>>> something more narrow to at least answer "What do we think the next
>>>version
>>> (2.4) will look like". When doing agile projects with my employer, I'm
>>>used
>>> to keeping a prioritized backlog which can be used to answer questions
>>>like
>>> this, but I don't see that in Jira. Thanks!
>>>
>>> -- Marcel Kinard
>