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

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

Hi Reuben,

On 25 Mar 2013, at 03:34, Reuben Thomas <rr...@sc...> wrote:
> On 24 March 2013 11:37, Gary V. Vaughan <ga...@gn...> wrote:
> Done, although it took me a minute to find the listserv.  Might be worth advertising the list in README?
> 
> A thought before I do that: maybe it would be better just to encourage the use of the github issue tracker? Otherwise we're basically saying "you need a github account AND a sourceforge account if you want to play with us" which seems mean.

Well, you don't need a sourceforge account to sign up to the mailing list.

However, I for one don't think much of sourceforge... it's littered with advertising, and slow as hell.  I'd be very happy indeed to pretend they do not exist.  If the github issue tracker is sufficient to your needs, then I see no reason to keep a sourceforce mailing list around too...

>  > Some of the package tests are currently failing. Please can we have those fixed so we can release v34, which I need for another project?
> 
> How about I tag the revision just before I introduced those failures, and release that as v34?
> 
> 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.

Cheers,
-- 
Gary V. Vaughan (gary AT gnu DOT org)