[7016] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: debathena Workflow Policy comments

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Fri Oct 15 23:47:36 2010

Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <201010132115.o9DLFoh3006960@pothole.mit.edu>
Date: Fri, 15 Oct 2010 23:47:29 -0400
Cc: release-team@mit.edu
Message-Id: <CFE47BAD-9053-4D53-A2CE-B1745CE72313@mit.edu>
To: "andrew m. boardman" <amb@mit.edu>
Content-Transfer-Encoding: 8bit

As per discussion at release-team, I have made the changes.   

The policy documented at http://debathena.mit.edu/trac/wiki/WorkflowPolicy should be effective immediately.   In a few months, we should review the source-commits archive, and if we find too few ACKs (that is, more often than not, the TTL is expiring), we should discuss the implications of that and possibly revisit the policy.

-Jon


On Oct 13, 2010, at 5:15 PM, andrew m. boardman wrote:

> 
> 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.



home help back first fref pref prev next nref lref last post