LGTM
I don't think Android N is going to change that much like you said. 

Let's move forward as usual , create a branch 6.x on main repo and start that 
release stream

Start landing features from the list below and have a board to track was left. 
When it's done it's done when ever that's it and we release regardless of 
official date of Android N (it might along or be bit after)

And as normal process we need to care and feed both branches (master & 6.x) 
having them green and CI testing as Android N builds come out. 

Any plugins need a 6.x branch corresponding to cordova-android@6.x branch, I 
don't think so but is good to ask. 

- Carlos
@csantanapr

> On May 24, 2016, at 4:07 PM, Joe Bowser <bows...@gmail.com> wrote:
> 
> I picked September because it's after when Android N is released.  The
> items on the list don't depend on each other.
> 
> Also, we use semver so us breaking an API or making a major breaking change
> means a major bump.  Not all of these are API breaking, and in fact only
> the Android Studio project structure and the Thread-Safe bridge breaks
> stuff.
> 
> I don't want to make a 6.0 and a 7.0 for the two major breaking changes and
> would rather group the two together since they're both related but not
> dependent.
> 
> 
>> On Tue, May 24, 2016, 12:58 PM Carlos Santana <csantan...@gmail.com> wrote:
>> 
>> Why the Sept. date?
>> 
>> Because Android N actually exists in August  sometime, but I don't have a
>> solid date.
>> 
>> 
>> All these items depend on each other and will take until Sept. to get it
>> implemented?
>> 
>> No, but
>> 
>> Each of them break APIs that required a major bump version?
>> 
>> Can we implement one first let's say June call it 6.0 and continue
>> releasing each month or as features get implemented 6.1, 6.2, etc. .
>> 
>> Which will be the first one that make most sense to implement? New Studio
>> Project?
>> 
>> - Carlos
>> @csantanapr
>> 
>>> On May 24, 2016, at 1:43 PM, Joe Bowser <bows...@gmail.com> wrote:
>>> 
>>> Hey
>>> 
>>> Since Google IO didn't really throw any new features at us, and since
>>> Google hinted at Android N being released at the end of August, do people
>>> think that aiming for a Cordova-Android 6.0.x release in September with
>> the
>>> following features makes sense:
>>> 
>>> * Android Studio project structure
>>> * Android N Multi-Window Support
>>> * Thread-Safe bridge by default
>>> * Cordova-Android as a distributable APK
>>> 
>>> I know that we had an earlier thread about this, but now that IO is over,
>>> we should probably ramp things up now that we know that we're not waiting
>>> until November for a new version of Android to land.  The biggest change
>> is
>>> the Android Studio project structure, and everything else has been
>> sitting
>>> in branches for months ready to be merged in.
>>> 
>>> Also, I know a lot of people are waiting for the change to version
>> numbers
>>> where we don't magically generate version numbers for arch-neutral APKs
>> as
>>> well as other script changes to the build, so I think we should do
>> another
>>> Cordova release to address those issues soon.
>>> 
>>> Thoughts?
>>> 
>>> Joe
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to