[yt-dev] YTEP-0008: Release procedure

Matthew Turk matthewturk at gmail.com
Mon Feb 25 19:46:33 PST 2013


Hi all,

Looks like it's all been approved.  Here's the build of the current
YTEP-0008 about the release schedule.

https://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0008.html

In keeping with this, on Friday I'll upload 2.5 to PyPI and the
release announcement will go out from John.  I'd also point out that
we've had pretty good success with new PRs and keeping to the
guidelines.

-Matt

On Thu, Feb 21, 2013 at 2:02 PM, Britton Smith <brittonsmith at gmail.com> wrote:
> Stephen, it's ok.  We can still leave comments and issue another PR if we
> want to make changes.
>
>
> On Thu, Feb 21, 2013 at 1:54 PM, Stephen Skory <s at skory.us> wrote:
>>
>> Hi Britton & Cameron,
>>
>> sorry to both of you, in my first message I wrote "approved" but I
>> actually merged it. But we can still comment on the PR, and the
>> content can be updated accordingly. I regret having such an itchy
>> "merge" finger!
>>
>> On Thu, Feb 21, 2013 at 11:50 AM, Britton Smith <brittonsmith at gmail.com>
>> wrote:
>> > 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
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>



More information about the yt-dev mailing list