On Thu, Jun 30, 2016 at 8:35 AM, Erik Bray <erik.m.b...@gmail.com> wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, leif <not.rea...@online.de> wrote:
>> Erik Bray wrote:
>>> While we're tinkering with the workflow, I think we need to change the
>>> workflow associated with testing changes.
>>>
>>> Currently the release manager *closes* a ticket and marks it as
>>
>> s/currently the release manager/the current release manager/ ;-)
>
> Yes, but I didn't want to imply "fault" here or anything like that.
> Volker does what's best for Volker and that's completely fine.
>
> The problem is that there aren't any documented procedures (that I
> know of!) for how testing of issues, merging, and releases should be
> handled.  So the correct procedure *is* whatever the current release
> manager does.  That, I do have a problem with, though it's nobody's
> fault.

Erik,

You are just begging to take a *turn* as release manager...

Incidentally, when I stopped being release manager, after several
years when I suddenly realized that I wasn't the only person in the
world who could do it, we had rotating release managers for a while...
which resulted in documenting workflows at the time.        I don't
want to speak for Volker [*], but I imagine he might enjoy taking a
little break?

 - William

[*] who is ridiculously good at release managing Sage, to put it
mildly.  Doing Sage release management is very, very difficult.


-- 
William (http://wstein.org)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to