[Vm-dev] Re: Marking VMs as "stable"
Marcel.Taeumel at hpi.de
Mon Aug 1 12:46:45 UTC 2016
> AFAIR we wanted to merge the Cog branch into master and then tag the
> 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
> 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 <
> > wrote:
>> On Sun, Jul 31, 2016 at 2:42 PM, marcel.taeumel <
>> > 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
We should just use *some* version so we can program our release automation
scripts for it. We can always find a more stable version in the future.
View this message in context: http://forum.world.st/Marking-VMs-as-stable-tp4908814p4909001.html
Sent from the Squeak VM mailing list archive at Nabble.com.
More information about the Vm-dev