My responses are inline
On Fri, Oct 18, 2013 at 8:37 AM, Mike Billau wrote:
> Hi. I ended up skipping my Spanish class and signing onto the Youtube
> broadcast. I took some longer note, feel free to skim through:
>
> https://docs.google.com/document/d/1IVyfFZ-kCIkg1Cnftxfm3viXHpxpJ2zdVa8B1CK0qU
Hi. I ended up skipping my Spanish class and signing onto the Youtube
broadcast. I took some longer note, feel free to skim through:
https://docs.google.com/document/d/1IVyfFZ-kCIkg1Cnftxfm3viXHpxpJ2zdVa8B1CK0qU0/(Was
going to paste them but they turned out a lot longer than I
remembered...)
I wan
p.m.)
>
>
> Review request for cordova.
>
>
> Repository: cordova-site
>
>
> Description
> ---
>
> 3.1 release blog post
>
>
> Diffs
> -
>
> /www/_posts/2013-10-01-cordova-31.md PRE-CREATION
> /www/css/_master.less 1
On Thu, Oct 17, 2013 at 7:05 PM, Michal Mocny wrote:
> My Short notes from meeting, longer emails to follow about some of these
> topics:
>
>
>
> CI/Medic brief description
>
>
> Summarize Mike's CordovaTests prototype
>
> -- Looks good, but do we support plugin.x
My Short notes from meeting, longer emails to follow about some of these
topics:
CI/Medic brief description
Summarize Mike's CordovaTests prototype
-- Looks good, but do we support plugin.xml ?
-- Jesse's alternative: test/ folder to have a plugin.xml that on
And here's the viewing link!
http://youtu.be/X3bUWVHeJJ0
On Thu, Oct 17, 2013 at 5:22 PM, Andrew Grieve wrote:
> Also, if you're having trouble connecting, I'll be on IRC.
>
>
> On Thu, Oct 17, 2013 at 5:22 PM, Andrew Grieve wrote:
>
>> Okay, for those who want to be able to talk:
>>
>>
>> htt
Also, if you're having trouble connecting, I'll be on IRC.
On Thu, Oct 17, 2013 at 5:22 PM, Andrew Grieve wrote:
> Okay, for those who want to be able to talk:
>
> https://plus.google.com/hangouts/_/a8df1213897c69821d177842af7d2bfbf948ef2b
>
> I'll post the viewing link closer to 5:30
>
>
> On
Okay, for those who want to be able to talk:
https://plus.google.com/hangouts/_/a8df1213897c69821d177842af7d2bfbf948ef2b
I'll post the viewing link closer to 5:30
On Thu, Oct 17, 2013 at 5:08 PM, Joe Bowser wrote:
> I meant that we'll be using my laptop here in Vancouver at the Regus
> space.
So, can I get an invite to the hangout? I'll be hosting it from the
Regus space in Vancouver.
On Thu, Oct 17, 2013 at 9:18 AM, Michal Mocny wrote:
> EST.
>
>
> On Thu, Oct 17, 2013 at 12:05 PM, purplecabbage
> wrote:
>
>> What time zone is this 5:30 PM occurring in? It was implied earlier that
>
I meant that we'll be using my laptop here in Vancouver at the Regus
space. Who is hosting the hangout?
On Thu, Oct 17, 2013 at 2:08 PM, Joe Bowser wrote:
> So, can I get an invite to the hangout? I'll be hosting it from the
> Regus space in Vancouver.
>
> On Thu, Oct 17, 2013 at 9:18 AM, Michal
EST.
On Thu, Oct 17, 2013 at 12:05 PM, purplecabbage wrote:
> What time zone is this 5:30 PM occurring in? It was implied earlier that
> this was EST, but not absolutely stated.
>
> Sent from my iPhone
>
> > On Oct 17, 2013, at 7:39 AM, Michal Mocny wrote:
> >
> > I don't know that the invite l
What time zone is this 5:30 PM occurring in? It was implied earlier that this
was EST, but not absolutely stated.
Sent from my iPhone
> On Oct 17, 2013, at 7:39 AM, Michal Mocny wrote:
>
> I don't know that the invite list was super useful last time.
>
> We will post the URL to the public st
t;Cordova plugin template create" CLI command yay. Night all.
i believe i've started something for that
https://issues.apache.org/jira/browse/CB-4886
>
> Sent from my Windows Phone From: Lucas Holmquist
> Sent: 17/10/2013 23:33
> To: dev@cordova.apache.org
> Subject: Re: Pos
y Windows Phone From: Lucas Holmquist
Sent: 17/10/2013 23:33
To: dev@cordova.apache.org
Subject: Re: Post 3.1 release committer & community meeting
Nope, just wondering if there was a sign up sheet like last time, i
didn't see one other than the doodle about the times
On Oct 17, 2013, a
I don't know that the invite list was super useful last time.
We will post the URL to the public stream here at 5:30 and post
instructions on how to join the stream for those who want to speak. Once
again we will be limited to 10, so please use the viewing-only option if
you can.
-Michal
On Th
Nope, just wondering if there was a sign up sheet like last time, i didn't
see one other than the doodle about the times
On Oct 17, 2013, at 10:31 AM, Michal Mocny wrote:
> Yes, is that a concern?
>
>
> On Thu, Oct 17, 2013 at 10:15 AM, Lucas Holmquist wrote:
>
>> will this also be a hangou
Yes, is that a concern?
On Thu, Oct 17, 2013 at 10:15 AM, Lucas Holmquist wrote:
> will this also be a hangout like last time
> On Oct 17, 2013, at 10:13 AM, Michal Mocny wrote:
>
> > Reminder, this is today.
> >
> >
> > On Wed, Oct 16, 2013 at 2:11 PM, James Jong
> wrote:
> >
> >> - Latest up
will this also be a hangout like last time
On Oct 17, 2013, at 10:13 AM, Michal Mocny wrote:
> Reminder, this is today.
>
>
> On Wed, Oct 16, 2013 at 2:11 PM, James Jong wrote:
>
>> - Latest updates / strategic direction on medic & CI
>>
>> -James Jong
>>
>> On Oct 15, 2013, at 11:30 AM, An
Reminder, this is today.
On Wed, Oct 16, 2013 at 2:11 PM, James Jong wrote:
> - Latest updates / strategic direction on medic & CI
>
> -James Jong
>
> On Oct 15, 2013, at 11:30 AM, Andrew Grieve wrote:
>
> > This is coming up this Thursday! What do people want to talk about?
> Here's
> > a cou
- Latest updates / strategic direction on medic & CI
-James Jong
On Oct 15, 2013, at 11:30 AM, Andrew Grieve wrote:
> This is coming up this Thursday! What do people want to talk about? Here's
> a couple to get us going:
>
> - Plugin registry download counts (Are these available yet)
> - Idea:
This is coming up this Thursday! What do people want to talk about? Here's
a couple to get us going:
- Plugin registry download counts (Are these available yet)
- Idea: Split cordova-cli-lib from cordova-cli on NPM (have cordova-cli and
phonegap-cli depend on cordova-cli-lib)
- Michal's work on CD
Alright, Looks like Thu 17 is the clear winner, with not a single person
having any complaints about that time.
Brian cannot make it until 6pm EST, but I'm going to schedule start time
for 5:30 for the inevitable hiccups and introductions and any agenda
overview etc. It will very likely be 6pm be
Okay, options are updated for the poll (http://doodle.com/2pmy2ptafmxsrna2)
For those who filled it out, sorry, you will need to do it again.
On Sun, Oct 6, 2013 at 7:27 PM, Michal Mocny wrote:
> Ugh Sorry that was a misreading of course. I'll set up a new doodle
> tomorrow morning.
> On 2013
Ugh Sorry that was a misreading of course. I'll set up a new doodle
tomorrow morning.
On 2013-10-06 1:52 AM, "Tommy Williams" wrote:
> +1 for post 16th for Joe availability.
>
> Also, thanks for thinking of Australia... One benefit of the time of year,
> the nasty time difference just got an hour
+1 for post 16th for Joe availability.
Also, thanks for thinking of Australia... One benefit of the time of year,
the nasty time difference just got an hour better today...
- tommy
On 5 Oct 2013 08:33, "Jesse" wrote:
> I filled it out, however, Joe is not available until after the 15th. Maybe
I filled it out, however, Joe is not available until after the 15th. Maybe
we should aim for the 16-18th as a window.
@purplecabbage
risingj.com
On Fri, Oct 4, 2013 at 3:09 PM, Michal Mocny wrote:
> http://www.doodle.com/2pmy2ptafmxsrna2
>
> I put a lot of options for time (sorry) since I wasn
http://www.doodle.com/2pmy2ptafmxsrna2
I put a lot of options for time (sorry) since I wasn't sure if we should be
europe or australia friendly this time.
There are also three options this time: yes, (yes), no, where the middle
option is supposed to be a "prefer not, but if need be, fine"
-Micha
11-15 sounds like the range to shoot for. I'll set up a doodle..
On Fri, Oct 4, 2013 at 4:48 PM, Joe Bowser wrote:
> I'm unavailable until after the 15th. I'll be at Big Android BBQ.
>
I'm unavailable until after the 15th. I'll be at Big Android BBQ.
Yes, let's do it.
I am unavailable until the 11th, but after that, let's hang.
(UTC-08:00) Pacific Time (US & Canada)
@purplecabbage
risingj.com
On Fri, Oct 4, 2013 at 1:12 PM, Andrew Grieve wrote:
> Sounds good! I was thinking the same thing :)
>
>
> On Fri, Oct 4, 2013 at 9:02 PM, Al Hardin
Sounds good! I was thinking the same thing :)
On Fri, Oct 4, 2013 at 9:02 PM, Al Harding wrote:
> Hi everyone,
>
> After the 3.0 release we had a successful Google Hangout session to discuss
> lots of topics.
>
> Now that 3.1 is out should we look at kicking off another Google Hangout
> for our
Hi everyone,
After the 3.0 release we had a successful Google Hangout session to discuss
lots of topics.
Now that 3.1 is out should we look at kicking off another Google Hangout
for our various locations?
Cheers,
Al
p.m.)
>
>
> Review request for cordova.
>
>
> Repository: cordova-site
>
>
> Description
> ---
>
> 3.1 release blog post
>
>
> Diffs
> -
>
> /www/_posts/2013-10-01-cordova-31.md PRE-CREATION
> /www/css/_master.less 1
: cordova-site
Description
---
3.1 release blog post
Diffs (updated)
-
/www/_posts/2013-10-01-cordova-31.md PRE-CREATION
/www/css/_master.less 1528178
/www/css/main.css 1528178
Diff: https://reviews.apache.org/r/14429/diff/
Testing
---
Thanks,
Andrew Grieve
visit:
> https://reviews.apache.org/r/14429/
> ---
>
> (Updated Oct. 2, 2013, 12:47 a.m.)
>
>
> Review request for cordova.
>
>
> Repository: cordova-site
>
>
> Description
> ---
>
> 3.1 release blog post
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14429/
> ---
>
> (Updated Oct. 2, 2013, 12:47 a.m.)
>
>
> Review request for cordova.
>
>
> Repository: cordova-site
&
: cordova-site
Description
---
3.1 release blog post
Diffs (updated)
-
/cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION
Diff: https://reviews.apache.org/r/14429/diff/
Testing
---
Thanks,
Andrew Grieve
---
3.1 release blog post
Diffs
-
/cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION
Diff: https://reviews.apache.org/r/14429/diff/
Testing
---
Thanks,
Andrew Grieve
gt; that
>>> >> is
>>> >> > > where we all the work done)
>>> >> > > - Follow steps on
>>> >> http://wiki.apache.org/cordova/StepsForPluginReleaseand
>>> >> > > publish these plugins on our registry. Thi
ork
>> >> > as
>> >> > > well.
>> >> > > - Update edge docs to refer to registry for plugin installation
>> (not
>> >> > sure
>> >> > > if this has been done)
>> >> > > - Update 3.0.0 docu
ption 2 from above is
> the
> >> way
> >> > > to go
> >> > > - Tag docs 3.1.0-rc1
> >> > >
> >> > > I volunteer to take the lead on getting the plugins released +
> tested
> >> > > (supposed to be today acco
n above?
>> > >
>> > >
>> > >
>> > >
>> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny
>> > wrote:
>> > >
>> > >> Just to be super duper clear: the reason to work on 'dev' branch of
>> &
> >
> > >
> > >
> > >
> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny
> > wrote:
> > >
> > >> Just to be super duper clear: the reason to work on 'dev' branch of
> > plugins
> > >> is not some proces
tools (specifically, the state
> of
> >> the registry as it was with 3.0 launch).
> >>
> >> We discussed this in-depth just a week ago (Read "About plugins in
> 3.1"),
> >> and I think several other times over the last month, if you would li
a week ago (Read "About plugins in 3.1"),
>> and I think several other times over the last month, if you would like to
>> read up on the details look there.
>>
>> No one likes the situation, we've been making headway into fixing it ever
>> since we discovered
r times over the last month, if you would like to
> read up on the details look there.
>
> No one likes the situation, we've been making headway into fixing it ever
> since we discovered the problem, and it can be resolved as soon as users
> upgrade from 3.0 (maybe that means w
resolved as soon as users
upgrade from 3.0 (maybe that means we can switch after 3.1 release, maybe
that means we wait for some 3-months deprecation time, not sure).
-Michal
On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson wrote:
> I agree with Joe that developing on anything other than maste
I agree with Joe that developing on anything other than master sucks. But
unfortunately, our hands are tied in the near term because the registry
doesn't know to fetch plugins from anywhere else. Also it makes life easier
for being who are installing plugins from git URLs.
I think we eventually wa
Yes, let's get this cleared up - confused myself.
On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI wrote:
> 3.1.0 is coincidental and it's temporary for this release because I
> wasn't sure where to get the code from and didn't want to compromise
> master or dev. I could have called it something els
3.1.0 is coincidental and it's temporary for this release because I
wasn't sure where to get the code from and didn't want to compromise
master or dev. I could have called it something else.
Jesse, I'd advise you to commit to dev. Everything will be merged to
master eventually.
So to re-iterate t
On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve wrote:
> Plugins are not tagged nor branched along with platforms. They are releases
> completely independently.
>
> Commit to the "dev" branch always.
AND FOREVER!11!!eleventyone!!!
Seriously, can't we have a stable branch instead? Having the d
Plugins are not tagged nor branched along with platforms. They are releases
completely independently.
Commit to the "dev" branch always.
For how to do a plugin release (aka merge dev into master, see
https://wiki.apache.org/cordova/StepsForPluginRelease). Anis just added a
branch for pushing them
I have a small change for Windows 8 that I need to apply to all the core
plugins.
Which branch should I work from, and which should I push to?
@purplecabbage
risingj.com
On Mon, Sep 23, 2013 at 9:39 AM, Joe Bowser wrote:
> So, what are the plugins being versioned at? 3.x? 1.x?
>
> I'm asking
So, what are the plugins being versioned at? 3.x? 1.x?
I'm asking because the plugins are tagged with the 3.0.0 release, so
it makes sense for them to start there.
On Mon, Sep 23, 2013 at 6:40 AM, Braden Shepherdson wrote:
> I don't think we want the Cordova version (3.1.0) getting tagged in
>
I don't think we want the Cordova version (3.1.0) getting tagged in
plugins. I should think we should merge dev to master and then tag it with
the plugin's own version number, not Cordova versions. Put another way,
it's only a coincidence that this plugin release happens to be near the
Cordova 3.1.
Jira issue is: https://issues.apache.org/jira/browse/CB-4889
On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI wrote:
> This is what I've done. Hopefully I didn't mess up because I haven't
> really followed the master/dev debate.
>
> For each plugin:
> - I created a branch and named it 3.1.0
> - I pul
This is what I've done. Hopefully I didn't mess up because I haven't
really followed the master/dev debate.
For each plugin:
- I created a branch and named it 3.1.0
- I pulled from origin dev
- I renamed the id from org.apache.cordova.core.* to org.apache.cordova.*
- I renamed the version from x.x
Sorry for being silent today. I ended up not having much time to work today
:(. Mostly what I got done is more thinking about how to go about things :P.
That said, Braden did manage to take care of RC1 of CLI! Thanks Braden! (
https://issues.apache.org/jira/browse/CB-4837). To get it:
npm install
I think since it has taken longer than expected to get the RC tagged, the
final release has been push till thursday to allow more time to test. Is
this correct?
On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard wrote:
> I'm confused about the date for 3.1.0 final release. These two posts don't
>
I'm confused about the date for 3.1.0 final release. These two posts don't
match.
On Sep 19, 2013, at 11:27 PM, Andrew Grieve wrote:
> Next Thursday:
> - If everything seems fine with RC1, release 3.1.0 final.
>
On Sep 10, 2013, at 3:20 PM, Andrew Grieve wrote:
> Monday 16th - Create releas
Ahh, thanks for the info. Any ETA on the updated plugins?
=Ryan
On 9/20/13 1:46 PM, "Michal Mocny" wrote:
>I think Braden is supposed to get an RC of the cli out today. I'm told
>this this may not included updated plugins yet until later, though.
>
>
>On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stew
I think Braden is supposed to get an RC of the cli out today. I'm told
this this may not included updated plugins yet until later, though.
On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart wrote:
> Is the RC still on track to get tagged today?
>
> I'm working on the PhoneGap-CLI and want to also r
Is the RC still on track to get tagged today?
I'm working on the PhoneGap-CLI and want to also release an RC version of
that when you guys have tagged.
=Ryan
On 9/20/13 1:01 PM, "Steven Gill" wrote:
>I think since it has taken longer than expected to get the RC tagged, the
>final release has b
for the delay.
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron
> > wrote:
> > >> > > >
> > >> > > > > Sorry for the iOS release guys I'm getting it out today
ase guys I'm getting it out today
> >> > > > >
> >> > > > >
> >> > > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <
> >> mmo...@chromium.org>
> >> > > > wrote:
> >> > > > >
gt; > > > > >
>> > > > > >
>> > > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <
>> mmo...@chromium.org
>> > >
>> > > > > wrote:
>> > > > > >
>> > &g
> > > > >
> > > > > > > I think its this one:
> > > http://wiki.apache.org/cordova/CuttingReleases
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Sep 19, 2013 at 7:52 AM,
; > > > > >
> > > > > >> I can take the responsibility of tagging BlackBerry. Could you
> > send
> > > me
> > > > > >> the wiki with instructions ?
> > > > > >>
> > > > > >> From:
wrote:
> > > > >
> > > > >> I can take the responsibility of tagging BlackBerry. Could you
> send
> > me
> > > > >> the wiki with instructions ?
> > > > >>
> > > > >> From: Andrew Grieve > agri...@chromium.org
>
> >> I can take the responsibility of tagging BlackBerry. Could you send
> me
> > > >> the wiki with instructions ?
> > > >>
> > > >> From: Andrew Grieve agri...@chromium.org
> > >>
> > > >>
gt;> the wiki with instructions ?
> >>
> >> From: Andrew Grieve mailto:agri...@chromium.org>>
> >> Date: Thursday, 19 September, 2013 10:40 AM
> >> To: dev mailto:dev@cordova.apache.org>>,
> Jeffrey
> >> Heifetz mailto:jheif...@blackbe
; >>
> > >> From: Andrew Grieve mailto:agri...@chromium.org
> >>
> > >> Date: Thursday, 19 September, 2013 10:40 AM
> > >> To: dev mailto:dev@cordova.apache.org>>,
> > Jeffrey
> > >> Heifetz mailto:jheif...@blackberry.com&g
t;>
Subject: Re: 3.1 Release
+Jeffrey - maybe you could take on the BlackBerry component for this release?
On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks
mailto:mich...@michaelbrooks.ca>> wrote:
Once the platforms are tagged, I can handle the docs. I'll need to review
our release
t; wrote:
>
>> I can take the responsibility of tagging BlackBerry. Could you send me
>> the wiki with instructions ?
>>
>> From: Andrew Grieve mailto:agri...@chromium.org>>
>> Date: Thursday, 19 September, 2013 10:40 AM
>> To: dev mailto:dev@cordova.apache.org&
org>>
> Date: Thursday, 19 September, 2013 10:40 AM
> To: dev mailto:dev@cordova.apache.org>>, Jeffrey
> Heifetz mailto:jheif...@blackberry.com>>
> Subject: Re: 3.1 Release
>
> +Jeffrey - maybe you could take on the BlackBerry component for this
> release?
>
+Jeffrey - maybe you could take on the BlackBerry component for this
release?
On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks
wrote:
> Once the platforms are tagged, I can handle the docs. I'll need to review
> our release process and see how the docs can best abide by them.
>
>
> On Wed, Sep 1
Once the platforms are tagged, I can handle the docs. I'll need to review
our release process and see how the docs can best abide by them.
On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve wrote:
> Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
> go without, but maybe k
Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
go without, but maybe keep at it until we get BB tagged? (just my opinion)
Heading home now - anyone know if Lorin is away or not?
On Wed, Sep 18, 2013 at 3:35 PM, Shazron wrote:
> When i mean ios-deploy still works, it
Ping Lorin & Shaz.
On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill wrote:
> FFOS will be tagged tomorrow. I have a few changes I am going to get in
> tomorrow before tagging but it will be good to go very soon!
>
> With FFOS, Only two plugins have been ported so far (vibration and device).
> We ar
I'm 99% done with iOS specific fixes. One last one I'm trying to do is
ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
This means if I don't get this fix in, we _can_ deploy from the command
line using ios-deploy _but_ we can't attach to the debugger. Will that be
acceptable yo
When i mean ios-deploy still works, it _installs_ it on the device, but
does _not_ run it.
On Wed, Sep 18, 2013 at 12:31 PM, Shazron wrote:
> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
>
> This mea
FFOS will be tagged tomorrow. I have a few changes I am going to get in
tomorrow before tagging but it will be good to go very soon!
With FFOS, Only two plugins have been ported so far (vibration and device).
We are going to continue to add firefoxos support to plugins post release.
I don't think
Thanks Jesse! Great work on being on top of things. If changes were done in
plugin repos, then those aren't a part of this release anyways and will be
picked up by the RELEASENOTES.md within the plugin repos on the next
plugins release.
I think it's up to you if you want to start writing RELEASENO
WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
re: Changelog
It is a little more difficult in these cases, and I n'er volunteered to do
it, so whatevs
- WP7+8 live in one repo, so their changes would need to be demuxed
- all the changes for Windows8 have happened in the plugin repos, and
cordova-
For the last plugin release, I tagged them with the plugin's version.
(e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes were
included in the release, so some may still not have any release tags.
On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson wrote:
> My understanding is t
My understanding is that the plugins are totally independent of Cordova
versions, and release on their own weekly-at-the-most-frequent cycle.
They only depend on Cordova versions when they need a sufficiently new
platform to support some feature (binary bridge, for example), and then
they set tag
Will the plugin repos get tagged? If so, do they get tagged on every weekly
cycle, or only when a cadence lines up with a weekly cycle, or both?
I see that StepsForPluginRelease wiki say it will happen, and the most recent
coho looks like it will do it, but I currently see only tags for 3.0.0 an
I'm totally fine with doing the branch cutting. Doing the actual testing is
the time intensive part though.
On Tue, Sep 17, 2013 at 12:00 PM, Joe Bowser wrote:
> Andrew, why don't you tag all the RC1 yourself, since you're the only
> one who can.
>
>
> On Tue, Sep 17, 2013 at 7:11 AM, Andrew Gr
Andrew, why don't you tag all the RC1 yourself, since you're the only
one who can.
On Tue, Sep 17, 2013 at 7:11 AM, Andrew Grieve wrote:
> Jesse - The "-" in there is needed for the version to be semver-compatible.
> There was some work done to support the missing -, but I think it's still
> the
In other news, I had to re-tag the JS because the build label was wrong.
You can actually see it in the previous email's output. It was
"3.1.0-rc1-0-g0d70465"
it should be "3.1.0-rc1". I've fixed it and re-tagged the JS.
On Tue, Sep 17, 2013 at 10:11 AM, Andrew Grieve wrote:
> Jesse - The "-" in
Jesse - The "-" in there is needed for the version to be semver-compatible.
There was some work done to support the missing -, but I think it's still
the case that without it plugins that have tags that require
"cordova-win8 >= 3.1.0" might fail to parse your version without the -.
Probably not so
I am working for Win8 inclusion.
Can we skip the dash in the version number? 3.2.0-dev is problematic for
now, I can create issues to support it, but I expect at least some things
will break. 3.2.0dev works great for me.
@purplecabbage
risingj.com
On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve
You set the version on the 3.1.x branch to 3.2.x-dev.
I tried following the steps on the wiki, and coho still fails horribly
on this end. I'm going to keep tagging the old fashioned way with
git. We should try and keep use of coho only for what we have
problems with (managing multiple plugin rep
I'm still on a couple loose ends on windows8 and wp7/8. I'll tag shortly.
Sent from my iPhone
> On Sep 16, 2013, at 12:06 PM, Andrew Grieve wrote:
>
> Looks like no one volunteered for release master, so I'll do so for this
> one.
>
> First up is creating the release bug and branching JS / Sp
Also - FYI - I updated the coho command today to update the VERSION file on
repo master branches to be "3.2.0-dev".
On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve wrote:
> Release Bug:
> https://issues.apache.org/jira/browse/CB-4830
>
> I've done the first task (tagging JS).
>
> The release bug
Release Bug:
https://issues.apache.org/jira/browse/CB-4830
I've done the first task (tagging JS).
The release bug may not have all of the platforms that it should. Wasn't
sure if win 8 or ffos should be in the list. If so, please add them :)
On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage wrote:
Looks like no one volunteered for release master, so I'll do so for this
one.
First up is creating the release bug and branching JS / Spec. I'll get on
it and report back! :)
On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser wrote:
> So, what's happening with this release?
>
> On Tue, Sep 10, 2013 a
So, what's happening with this release?
On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve wrote:
> Sure! New plan:
>
> Monday 16th - Create release branches & tag RC of all repos
> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> Monday 20th - Tag 3.1.0 for all repos
> Tuesday 21st -
Can we move this so it happens on Mondays instead of Fridays.
Releasing on a Friday is never a good idea, especially since we're
going to be MIA for those two Fridays with internal stuff at the
Vancouver Adobe office).
On Mon, Sep 9, 2013 at 8:10 AM, James Jong wrote:
> Andrew, thanks for kicki
Sure! New plan:
Monday 16th - Create release branches & tag RC of all repos
Tuesday 17th - Draft Release Blog Post (digest of changelogs)
Monday 20th - Tag 3.1.0 for all repos
Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
While we're at it, anyone want to volunteer to be Release
1 - 100 of 103 matches
Mail list logo
