cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <shaz...@gmail.com>
Subject Re: 3.1 Release
Date Fri, 20 Sep 2013 00:56:41 GMT
ios-deploy stuff a no go so I left it out (check out the issue for the
sordid details) :(

sorry for the delay, I had other pressing work related stuff.
Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only one
failure on iOS 6 - contacts.spec.24.


On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <lorin.beer.dev@gmail.com>wrote:

> I was away a good chunk of yesterday due to a sick wife, getting BB tagged
> today. Sorry for the delay.
>
>
> On Thu, Sep 19, 2013 at 9:59 AM, Shazron <shazron@gmail.com> wrote:
>
> > Sorry for the iOS release guys I'm getting it out today
> >
> >
> > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mmocny@chromium.org>
> wrote:
> >
> > > Specifically, I think the section "Branch & Tag RC1 for Platform
> > > Repositories"
> > >
> > >
> > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mmocny@chromium.org>
> > wrote:
> > >
> > > > I think its this one: http://wiki.apache.org/cordova/CuttingReleases
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > > jheifetz@blackberry.com>wrote:
> > > >
> > > >> I can take the responsibility of tagging BlackBerry. Could you send
> me
> > > >> the wiki with instructions ?
> > > >>
> > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> agrieve@chromium.org
> > >>
> > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > > >> To: dev <dev@cordova.apache.org<mailto:dev@cordova.apache.org>>,
> > > Jeffrey
> > > >> Heifetz <jheifetz@blackberry.com<mailto:jheifetz@blackberry.com>>
> > > >> 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 <
> > > >> michael@michaelbrooks.ca<mailto:michael@michaelbrooks.ca>>
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 18, 2013 at 1:34 PM, Andrew Grieve <
> agrieve@chromium.org
> > > >> <mailto:agrieve@chromium.org>> wrote:
> > > >>
> > > >> > 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 <shazron@gmail.com
> <mailto:
> > > >> shazron@gmail.com>> wrote:
> > > >> >
> > > >> > > 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 <shazron@gmail.com
> > > <mailto:
> > > >> shazron@gmail.com>> 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 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 you think?
> > > >> > >>
> > > >> > >>
> > > >> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
> > > >> agrieve@chromium.org<mailto:agrieve@chromium.org>
> > > >> > >wrote:
> > > >> > >>
> > > >> > >>> Ping Lorin & Shaz.
> > > >> > >>>
> > > >> > >>>
> > > >> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
> > > >> stevengill97@gmail.com<mailto:stevengill97@gmail.com>
> > > >> > >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 are going to continue to add firefoxos support
to plugins
> > post
> > > >> > >>>> release.
> > > >> > >>>> I don't think we should start officially promoting
support
> for
> > > FFOS
> > > >> > >>>> until
> > > >> > >>>> we have more plugins. For 3.1, it will be available
for users
> > to
> > > >> try
> > > >> > >>>> out,
> > > >> > >>>> test, give feedback, etc.
> > > >> > >>>>
> > > >> > >>>> Cheers,
> > > >> > >>>> -Steve
> > > >> > >>>>
> > > >> > >>>>
> > > >> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve
<
> > > >> agrieve@chromium.org<mailto:agrieve@chromium.org>>
> > > >> > >>>> wrote:
> > > >> > >>>>
> > > >> > >>>> > 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
> > > >> RELEASENOTES.md
> > > >> > >>>> for
> > > >> > >>>> > WP7+8. My thinking was just that doing
so would make
> release
> > > >> > >>>> announcements
> > > >> > >>>> > easier.
> > > >> > >>>> >
> > > >> > >>>> > Since WP7 and WP8 are in the same repo,
does it make sense
> to
> > > >> have
> > > >> > >>>> > different subtasks for their taggings?
If so, I'll add it
> to
> > > the
> > > >> > >>>> template,
> > > >> > >>>> > if not, maybe I'll just change WP8 to say
WP7+WP8? WDYT?
> > > >> > >>>> >
> > > >> > >>>> > Shaz - I see you're still checking in iOS7
fixes. Do you
> > think
> > > >> > you'll
> > > >> > >>>> be
> > > >> > >>>> > able to tag iOS / OSX soon?
> > > >> > >>>> > Lorin - Same question for BB. Will you
be able to write an
> > > update
> > > >> > >>>> script
> > > >> > >>>> > for it (CB-4776)
> > > >> > >>>> > Steve - Likewise for FF
> > > >> > >>>> >
> > > >> > >>>> > I'd really like this tagging to be done
tomorrow so that we
> > can
> > > >> test
> > > >> > >>>> out
> > > >> > >>>> > RC1 using RC1 of CLI.
> > > >> > >>>> >
> > > >> > >>>> >
> > > >> > >>>> >
> > > >> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse
<
> > > purplecabbage@gmail.com
> > > >> <mailto:purplecabbage@gmail.com>>
> > > >> > >>>> wrote:
> > > >> > >>>> >
> > > >> > >>>> > > 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-js, so changelog  would be
empty
> > > >> > >>>> > >
> > > >> > >>>> > > Maybe I'll get this together for the
3.1.0, we'll see.
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > > @purplecabbage
> > > >> > >>>> > > risingj.com<http://risingj.com>
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM,
Andrew Grieve <
> > > >> > >>>> agrieve@chromium.org<mailto:agrieve@chromium.org>
> > > >> > >>>> > > >wrote:
> > > >> > >>>> > >
> > > >> > >>>> > > > 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 <
> > > >> > >>>> > braden@chromium.org<mailto:braden@chromium.org>
> > > >> > >>>> > > > >wrote:
> > > >> > >>>> > > >
> > > >> > >>>> > > > > 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 <engine>
tags appropriately.
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > Braden
> > > >> > >>>> > > > >
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > On Tue, Sep 17, 2013 at
3:18 PM, Marcel Kinard <
> > > >> > >>>> cmarcelk@gmail.com<mailto:cmarcelk@gmail.com>>
> > > >> > >>>> > > > wrote:
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > > 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 and 3.0.0rc1
in the plugins repos, not a
> > "weekly"
> > > >> tag.
> > > >> > >>>> > Thanks!
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > > On Sep 9, 2013, at
10:42 AM, Andrew Grieve <
> > > >> > >>>> agrieve@chromium.org<mailto:agrieve@chromium.org>>
> > > >> > >>>> > > > wrote:
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > > > I think it's time
to get the ball rolling on
> this.
> > > >> It'll
> > > >> > be
> > > >> > >>>> the
> > > >> > >>>> > > first
> > > >> > >>>> > > > > > > release post-3.0,
so will likely have a few bumps
> > to
> > > >> work
> > > >> > >>>> > through.
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > How about:
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > Friday 13th -
Create release branches & tag RC of
> > all
> > > >> > repos
> > > >> > >>>> > > > > > > Monday 16th -
Draft Release Blog Post (digest of
> > > >> > changelogs)
> > > >> > >>>> > > > > > > Thurs 19th - Tag
3.1.0 for all repos
> > > >> > >>>> > > > > > > Fri 20th - Push
3.1.0-1.0.0 of CLI to npm & Post
> > blog
> > > >> post
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > The main feature
of this release will be
> > > >> plugman-registry
> > > >> > I
> > > >> > >>>> > think.
> > > >> > >>>> > > > That
> > > >> > >>>> > > > > > > said, since CLI
/ Plugman aren't tied to cadence
> > > >> > releases, I
> > > >> > >>>> > think
> > > >> > >>>> > > > it's
> > > >> > >>>> > > > > > > just cordova-docs
that is relevant.
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > >
> > > >> > >>>> > > >
> > > >> > >>>> > >
> > > >> > >>>> >
> > > >> > >>>>
> > > >> > >>>
> > > >> > >>>
> > > >> > >>
> > > >> > >
> > > >> >
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> This transmission (including any attachments) may contain
> confidential
> > > >> information, privileged material (including material protected by
> the
> > > >> solicitor-client or other applicable privileges), or constitute
> > > non-public
> > > >> information. Any use of this information by anyone other than the
> > > intended
> > > >> recipient is prohibited. If you have received this transmission in
> > > error,
> > > >> please immediately reply to the sender and delete this information
> > from
> > > >> your system. Use, dissemination, distribution, or reproduction of
> this
> > > >> transmission by unintended recipients is not authorized and may be
> > > unlawful.
> > > >>
> > > >>
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message