[9328] in athena10
Re: [Debathena] #673: Rebuild for Squeeze
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Jul 2 00:13:30 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: geofft@MIT.EDU, jdreed@MIT.EDU, kaduk@MIT.EDU
Date: Mon, 02 Jul 2012 04:13:26 -0000
Reply-To:
Message-ID: <057.6ddac73b108dad4745e412c78417cef4@mit.edu>
In-Reply-To: <042.78eb80de9ba558fe586de5b2dcb90b04@mit.edu>
Content-Transfer-Encoding: 8bit
#673: Rebuild for Squeeze
--------------------+-----------------------------------
Reporter: geofft | Owner: jdreed
Type: task | Status: development
Priority: low | Milestone: The Distant Future
Component: -- | Resolution:
Keywords: | Upstream bug:
--------------------+-----------------------------------
Comment (by kaduk):
Replying to [comment:4 jdreed]:
> Now that we have -staging, we should think about a workflow? Should it
just get moved to -development upon a successful build? Or should it
require testing in -staging, then -dev, then -proposed. Or -staging to
production?
I think it should just get moved to -development upon successful build,
"most of the time".
Reasons not to move include if there's other stuff in -development we
don't want to squash, or un-ack'd code or something like that.
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/673#comment:6>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
