[Yt-dev] Releases, pull requests, "governance" ...

[Sam Skillman]

What if we were to, whenever the testing suite passes, automatically update
a "yt-stable" tag (or other name) on the yt branch, which would signify
that it is the latest change to pass all the tests?  My guess is that this
is basically the yt tip most the time, but perhaps we could then with some
confidence tell people to just update to that by default?  I'm just trying
to think of a way we don't have manually manage 2.2.X.

Sam

On Wed, Nov 2, 2011 at 10:47 AM, Stephen Skory <s at skory.us> wrote:

> Yo,
>
> > So I guess what it comes down to -- do we want to start being
> > aggressive about putting out patch (i.e., 2.2.X) releases?  Do we need
> > a set of release managers or curators, like there are in Enzo?  When
> > do we develop in a fork, when do we feel comfortable pushing to the
> > main repo?  The problem, as I see it, is that in some respects yt
> > suffers from the same *problems* a project like Enzo does, in that
> > some pieces of functionality are critical to a few applications, but
> > it does not have the level of support or engagement as Enzo, so we
> > don't have as much ability to spread workload around.  Any thoughts on
> > this?
>
> I feel that if we are to go to a second decimal point, it would be up
> to the person who did the fix to either do the point release if they
> have permissions (core devs), or the core dev who accepted the pull
> release. I think that would work fairly well.
>
> --
> Stephen Skory
> s at skory.us
> http://stephenskory.com/
> 510.621.3687 (google voice)
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20111102/dbf7b8be/attachment.html>