Well, for some reason we deviated from that last release. I don't know why but Steve proposed the change and it made sense at the time. On Sep 4, 2014 1:05 PM, "Brian LeRoux" <b...@brian.io> wrote:
> 0.0.1rc1 > 0.0.1rc2 > > no? > > > On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cmarc...@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 <purplecabb...@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 > > > > >
