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

Stephen Skory s at skory.us
Wed Nov 2 09:47:43 PDT 2011


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)



More information about the yt-dev mailing list