[Vm-dev] Marking VMs as "stable"
lists at fniephaus.com
Mon Aug 1 12:37:35 UTC 2016
Actually, I forgot that the interpretervm currently lives on the master
branch. So we'd either need to merge Cog into master and produce a spur
interpretervm now, or we could move the interpretervm from master to a new
branch and defer this task...
On Mon, Aug 1, 2016 at 2:22 PM Fabio Niephaus <lists at fniephaus.com> wrote:
> AFAIR we wanted to merge the Cog branch into master and then tag the
> master for a new release. The main question I guess is: when is the right
> moment to do this? IIRC Eliot has used his gut feeling in the past for
> declaring a specific version as stable. So I'd say it's up to him to decide
> when the first stable release on GitHub is ready.
> On Sun, Jul 31, 2016 at 1:17 PM Ben Coman <btc at openinworld.com> wrote:
>> On Sun, Jul 31, 2016 at 2:42 PM, marcel.taeumel <Marcel.Taeumel at hpi.de>
>> > Hi, there.
>> > Could some please tag some VM version as "stable" so that we have the
>> > candidate to be used in the Squeak release artifact packaging process?
>> :-) I
>> > don't want to package any latest "bleeding edge" VM build into those
>> > artifacts.
>> > Thanks,
>> > Marcel
>> Would there be a benefit in a release workflow like suggested under
>> the heading "Release branches"  ? (where their 'develop' branch
>> is effectively our 'Cog' branch)
>>  http://nvie.com/posts/a-successful-git-branching-model/
>> cheers -ben
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev