cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Gill <stevengil...@gmail.com>
Subject Re: 3.1 Release
Date Fri, 20 Sep 2013 18:00:27 GMT
Hey Andrew,

Need any help with this stuff? Let me know if you want me to take care some
of these.

-Steve


On Fri, Sep 20, 2013 at 10:52 AM, Andrew Grieve <agrieve@chromium.org>wrote:

> Sounds good. I don't think we need a release branch on docs if it's not
> adding benefit.
>
>
> On Fri, Sep 20, 2013 at 4:25 AM, Michael Brooks <michael@michaelbrooks.ca
> >wrote:
>
> > >
> > > Michael: I noticed that the launch bug I created is missing any
> subtasks
> > > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> > we
> > > don't actually say that the docs branch should be created until once
> > we're
> > > ready to launch final. I think this is wrong, but wanted to know what
> > your
> > > thoughts are for it. I'm thinking:
> > > - cordova-docs should have a release branch created as soon as the RCs
> of
> > > the platforms are tagged
> > > - I don't think there's much value in having an RC tag for the docs,
> > since
> > > they tend to change a bunch post RC1 of platforms
> > > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > > made the default. We can keep re-uploading it as changes are made.
> > > - Once we're ready for the final release, we delete the rc1 version,
> > > upload the non-rc version, and make that the default.
> > > Does this sound good?
> >
> >
> > If possible, it would be nice to avoid creating any branches for the
> > cordova-docs. When we have a branch, the maintainers need to apply their
> > commits to both the master and the release branch. It's error prone and
> > troublesome. Since we version cordova-docs by directory, can we skip the
> > release branch without messing up the release process? Of course, this is
> > temproary. When we switch the a new doc generator and restructure the
> docs,
> > we will version by tags and then we can adopt the release branch
> approach.
> >
> > The rest of your steps are exactly how I see it working out.
> >
> >
> > On Thu, Sep 19, 2013 at 8:27 PM, Andrew Grieve <agrieve@chromium.org>
> > wrote:
> >
> > > Sounds good.
> > >
> > > So - here's what I'm thinking for next steps:
> > >
> > > Friday:
> > > - Remove "core" from plugin IDs
> > > - Remove URLs from <dependency> tags
> > > - Do a plugins release
> > > - Do a plugman release
> > > - Do a CLI release, but don't tag it as "latest", tag it as "rc"
> instead.
> > > This will cause it to be installed only if you type "npm install
> > cordova@rc
> > > "
> > > - Add "cordova platform update" instructions to the upgrade guides
> within
> > > the docs
> > > - Upload RC1 of cordova-docs
> > > - Write blog post about the availability of the RC1. Tweet it.
> > >
> > > Next Thursday:
> > > - If everything seems fine with RC1, release 3.1.0 final.
> > >
> > > Sound good?
> > >
> > >
> > > Michael: I noticed that the launch bug I created is missing any
> subtasks
> > > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> > we
> > > don't actually say that the docs branch should be created until once
> > we're
> > > ready to launch final. I think this is wrong, but wanted to know what
> > your
> > > thoughts are for it. I'm thinking:
> > > - cordova-docs should have a release branch created as soon as the RCs
> of
> > > the platforms are tagged
> > > - I don't think there's much value in having an RC tag for the docs,
> > since
> > > they tend to change a bunch post RC1 of platforms
> > > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > > made the default. We can keep re-uploading it as changes are made.
> > > - Once we're ready for the final release, we delete the rc1 version,
> > > upload the non-rc version, and make that the default.
> > >
> > > Does this sound good?
> > >
> > >
> > >
> > > On Thu, Sep 19, 2013 at 11:04 PM, Shazron <shazron@gmail.com> wrote:
> > >
> > >> Lets skip it, it's unchanged
> > >>
> > >> On Thursday, September 19, 2013, Andrew Grieve wrote:
> > >>
> > >> > Thanks Shaz. Do you want to do OSX as well, or should we skip that
> for
> > >> this
> > >> > release?
> > >> >
> > >> >
> > >> > On Thu, Sep 19, 2013 at 8:56 PM, Shazron <shazron@gmail.com>
wrote:
> > >> >
> > >> > > 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
> > >> > > > > >
> > >>
> > >
> > >
> >
>

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