cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: [Vote] 3.6.0 Cadence Release
Date Thu, 04 Sep 2014 19:59:05 GMT
I agree with all of Marcel's suggestions.

@purplecabbage
risingj.com


On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cmarcelk@gmail.com> wrote:

> Here is more specifics on what I'd suggest:
>
> - on the 3.6.x branch of all the platforms and tools in git, modify
> VERSION and/or package.json to bump the version to 3.6.1. Create a new
> 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> tags.
> - build new archives of these 3.6.1 images and post them to dist-dev. Do
> not publish them to npm.
> - do a vote based on the contents of dist-dev. For testing, use --usegit
> after verifying dist-dev matches the git content (a script could do the
> verify).
> - after the vote passes, publish 3.6.1 to npm at the same time as
> promoting from dist-dev to dist.
>
> Going forward, publishing rc's to npm before the vote isn't possible,
> because the version in package.json would need to be modified between rc
> and final.
>
> On Sep 4, 2014, at 3:30 PM, Jesse <purplecabbage@gmail.com> wrote:
>
> > Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> > it until AFTER a vore.
> >
> > We should be voting on what we see in the git-repos ( after verifying
> that
> > it is identical to the packaged binaries)
> > We should be testing via --usegit all the npm stuff should just be gravy.
> >
> > Carlos:
> > - The problem is that we won't be voting on what is already published
> >
> > @purplecabbage
> > risingj.com
>
>

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