[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] LuaJIT 2.0 git repository
- From: Alexander Gladysh <agladysh@...>
- Date: Wed, 9 Dec 2009 17:13:43 +0300
On Wed, Dec 9, 2009 at 16:58, Jerome Vuarand <email@example.com> wrote:
> 2009/12/9 Alexander Gladysh <firstname.lastname@example.org>:
>> On Wed, Dec 9, 2009 at 14:20, Mike Pall <email@example.com> wrote:
>>> Beta2 + hotfix#2 has all the 'fixes'. The development version has
>>> new minor 'features'. Now that the git repo is in place, my plan
>>> is to release new betas only for major fixes or major features.
>> Well, I just don't like to run my code on the Git snapshots. It is
>> simpler to run on some officially named version (even if it is named
>> "beta2.2" or whatever). At least from management point of view -- it
>> is easier to say to people "go install beta2.2" than "go install
>> a6e08e". :-)
>> I can live with the current situation though.
> An intermediate solution is to use some tags, maybe a "mostly-stable"
> or "usable" tag that is updated from time to time.
AFAIR, it is generally a very bad idea to update Git tags. In Git tags
are intended to be constant objects.
"mostly-stable" more fits as a branch.
Given a single active committer though, I'm not sure if this formalism