@cordova.apache.org dev@cordova.apache.org
Sent: Wednesday, October 16, 2013 9:02 AM
Subject: Re: Tag 2.9.1
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc...@gmail.com wrote:
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy
Subject: Re: Tag 2.9.1
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc...@gmail.com
wrote:
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy plugin
changes, not new features (new device OS capability such as iOS 7
!
--
Dan Moore
Developing with Cordova CLI
https://leanpub.com/developingwithcordovacli
From: Brian LeRoux b...@brian.io
To: dev@cordova.apache.org dev@cordova.apache.org
Sent: Wednesday, October 16, 2013 9:02 AM
Subject: Re: Tag 2.9.1
/developingwithcordovacli
From: Brian LeRoux b...@brian.io
To: dev@cordova.apache.org dev@cordova.apache.org
Sent: Wednesday, October 16, 2013 9:02 AM
Subject: Re: Tag 2.9.1
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc
Moore
Developing with Cordova CLI
https://leanpub.com/developingwithcordovacli
From: Brian LeRoux b...@brian.io
To: dev@cordova.apache.org dev@cordova.apache.org
Sent: Wednesday, October 16, 2013 9:02 AM
Subject: Re: Tag 2.9.1
yes
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy plugin
changes, not new features (new device OS capability such as iOS 7 is considered
a new feature)
- stop backporting anything to 2.9 when 3.5 comes out
If so, should this be spelled out
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc...@gmail.com wrote:
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy plugin
changes, not new features (new device OS capability such as iOS 7 is
considered a new
, 2013 9:02 AM
Subject: Re: Tag 2.9.1
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc...@gmail.com wrote:
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy plugin
changes, not new features (new device OS capability
, 2013 9:02 AM
Subject: Re: Tag 2.9.1
yes and yes!
On Wed, Oct 16, 2013 at 9:49 AM, Marcel Kinard cmarc...@gmail.com wrote:
So my intepretation of these comments is:
- backport fixes to 2.9 for serious platform breakages and easy plugin
changes, not new features (new device OS capability
One question about this that was not answered. When does back-porting end?
I'm not sure what we promised for 2.9.x support going forward...
On Tue, Oct 15, 2013 at 1:16 PM, Jesse purplecabb...@gmail.com wrote:
Okay, I am actively working on back-porting plugin fixes into 2.9.1 for
WP7, WP8,
Decide what is completely broken in your platform, that is reasonable to
fix, and fix it.
No promises ... just fix what we can, and document that it is fixed. I
think...
@purplecabbage
risingj.com
On Tue, Oct 15, 2013 at 3:10 PM, Shazron shaz...@gmail.com wrote:
One question about this that
Nothing is completely broken in iOS 7, although with iOS 7 issues that is
debatable. If we keep patching 2.9.x no one will move on to 3.x... (at
least for iOS). There has to be an ending...
On Tue, Oct 15, 2013 at 4:53 PM, Jesse purplecabb...@gmail.com wrote:
Decide what is completely broken
I would not add iOS7 support.
I would consider adding any plugin changes if it is not too difficult to do
so.
@purplecabbage
risingj.com
On Tue, Oct 15, 2013 at 4:56 PM, Shazron shaz...@gmail.com wrote:
Nothing is completely broken in iOS 7, although with iOS 7 issues that is
debatable. If
3.5
(Or six months.)
But ya, what Jesse said.
On Tuesday, October 15, 2013, Jesse wrote:
I would not add iOS7 support.
I would consider adding any plugin changes if it is not too difficult to do
so.
@purplecabbage
risingj.com
On Tue, Oct 15, 2013 at 4:56 PM, Shazron shaz...@gmail.com
I think we need to just have everyone go through their work over the
past month and see if they missed backports. I didn't actually have
very much missed, and I just backported the File plugin in the 2.9.1
branch. Of course, with backporting, we need more people to look at
what was in 3.1.0 and
Yes, now that 3.1.0 is out the door, we can do this.
Sent from my iPad
On Oct 7, 2013, at 10:36 AM, Joe Bowser bows...@gmail.com wrote:
I think we need to just have everyone go through their work over the
past month and see if they missed backports. I didn't actually have
very much missed,
As soon as we are done with 3.1.0 it would be a good time to go back and
back-fill for a 2,9,1 release.
Who's with me?
Do we need to do an RC? If so, a quick one?
Cheers,
Jesse
@purplecabbage
risingj.com
Have we done RCs for minor releases before? I don't recall any for 3.0.1 to
3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1.
Not that it's a bad idea; I just don't think it's a formality that has been
observed in the past.
How much back-fill are you expecting?
On
Nope, I don't think we've ever done minor rc's, this is a bit more of a
significant release though.
Back-fill would just be putting all the updated plugin native code back
into each platform, as well as making sure any relevant js changes went
back into cordova-js before being tagged+built. Kind
Right. I wasn't sure if there were 10 issues to backport or 150. If there
are only a few isolated fixes to apply, then I'd be comfortable with just
applying them, testing and releasing. If there are a ton of fixes, which
might have overlapping effects, then lets spend a day or so with a tagged
rc
20 matches
Mail list logo
