[yt-dev] YTEP-0008: Release procedure

Britton Smith brittonsmith at gmail.com
Thu Feb 21 10:50:02 PST 2013


Hi all

I agree with Stephen that we should not close discussion just yet.  I would
like to chime in on this PR, but won't have time until tonight.  I think
this PR should perhaps remain open for a full day.

Britton


On Thu, Feb 21, 2013 at 1:46 PM, Stephen Skory <s at skory.us> wrote:

> Hi all,
>
> I just approved the YTEP PR, but I don't think that means the
> discussion is closed. For example, there are still future release
> manager slot unassigned.
>
> On Thu, Feb 21, 2013 at 9:14 AM, Matthew Turk <matthewturk at gmail.com>
> wrote:
> > Hi all,
> >
> > Because of the somewhat dysfunctional release process we've had
> > recently, there was some discussion of how to improve this in IRC.
> > I've tried to synthesize many of those comments (thanks, Sam, Nathan,
> > Cameron, Jeff, Britton, Kacper, etc...) and come up with a plan for
> > releases.
> >
> > I'd appreciate feedback on this in the PR.  I anticipate that this
> > YTEP will be one of the most updated, as it will need updates as we
> > fine tune things, and as we move forward with new versions.
> >
> > Please leave comments on the PR, or if you feel they warrant much
> > further discussion, in reply to this email.
> >
> >
> https://bitbucket.org/yt_analysis/ytep/pull-request/9/adding-draft-of-ytep-0008-release/diff
> >
> > -Matt
> > _______________________________________________
> > yt-dev mailing list
> > yt-dev at lists.spacepope.org
> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
> --
> 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/20130221/bbab8f28/attachment.html>


More information about the yt-dev mailing list