[7007] in Release_7.7_team
debathena Workflow Policy comments
daemon@ATHENA.MIT.EDU (andrew m. boardman)
Wed Oct 13 17:15:57 2010
Date: Wed, 13 Oct 2010 17:15:50 -0400
Message-Id: <201010132115.o9DLFoh3006960@pothole.mit.edu>
From: "andrew m. boardman" <amb@MIT.EDU>
To: release-team@MIT.EDU
Since I gather we're doing to discuss this
(https://debathena.mit.edu:444/trac/wiki/WorkflowPolicy) on Friday, here
are some comments:
Under "Committing Code": one bit says that zephyr discussion should
always also be summarized in email, even though ACKs via zephyr are OK.
This seems odd, especially without having this requirement at later
stages. If we have a "go read the zlogs if you want the full story"
policy anyway, we may as well stick with it. For "Code should be ACK'd
by at least $num members of debathena-root", I suggest
s/\$num numbers/one member/. (I think that was ultimately hashed out as
what we wanted and this just never got updated, but perhaps we want to
argue about it. I am in favor of a reasonably low bar to make it into
dev.) The last sentence is also incomplete and I'm not sure where it was
going.
Under "Uploading to Alpha": I'd like to make it explicit whether one of
the two acks (for approval to move something to Beta) can be from the
original author.
Under "Uploading to Production", I'd like to add a "today = weekday"
requirement.
