[Vm-dev] Marking VMs as "stable"

[Fabio Niephaus]

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.

Cheers,
Fabio

-- 

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>
> wrote:
> >
> > Hi, there.
> >
> > Could some please tag some VM version as "stable" so that we have the
> first
> > 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" [1] ?   (where their 'develop' branch
> is effectively our 'Cog' branch)
>
> [1] http://nvie.com/posts/a-successful-git-branching-model/
>
> cheers -ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160801/45eed713/attachment.htm