Re: [Lua-users-stdlib] Getting v34 released

[Gary V. V. <ga...@va...>]

Hi Reuben,

On 25 Mar 2013, at 08:48, Reuben Thomas <rr...@sc...> wrote:
> On 25 March 2013 01:44, Gary V. Vaughan <ga...@gn...> wrote:
> > That would be nice, provided my recent patch to getopt goes in. In fact, preferably everything up to 47d51c718ce. Is that possible without messing with history?
> 
> No it's not.  And github (rightly) don't allow rewinding on master, so I just committed a revert for the premature branch merge.  master builds and meets specs using both Lua 5.1 and 5.2 for me.  Feel free to release, or ping me if you like me to do it.
> 
> 
> I'm unclear why you couldn't just tag before the bit you reverted? But fine, making a release now is good.

So that the commits you made to master after the premature merge (particularly changes to the release rule) are available while making the release.

> Note that I changed the release source check-in scheme to work the same as that for luaposix, i.e. it expects to find a checkout of master next to a checkout of the release branch, the latter named stdlib-release. This avoids nuking files in the master checkout (in my case I found I was nuking all my release-notes-* files, which is not a disaster, but is a bit annoying).

Ack.  No worries... I'll make another clone of the git repo, and fire off the release later this afternoon.

Cheers,
-- 
Gary V. Vaughan (gary AT vaughan DOT pe)