[9193] in athena10

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

Re: [Debathena] #967: Create -bleeding repository

daemon@ATHENA.MIT.EDU (Debathena Trac)
Tue Jun 5 10:33:47 2012

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: jdreed@MIT.EDU
Date: Tue, 05 Jun 2012 14:33:43 -0000
Reply-To: 
Message-ID: <057.7d3b01e0756fa0c8979de9345d28f37e@mit.edu>
In-Reply-To: <042.2a72aac15cce45ba6f03912ea4fa58b1@mit.edu>
Content-Transfer-Encoding: 8bit

#967: Create -bleeding repository
-------------------------+-----------------------------------
 Reporter:  jdreed       |         Owner:  jdreed
     Type:  enhancement  |        Status:  accepted
 Priority:  normal       |     Milestone:  The Distant Future
Component:  --           |    Resolution:
 Keywords:               |  Upstream bug:
-------------------------+-----------------------------------
Changes (by jdreed):

 * owner:   => jdreed
 * status:  new => accepted


Comment:

 Done.  Rules for the -bleeding repository:

 - Do not talk about the -bleeding repository.
 - Version consistency need not be enforced.
 - Use zephyr as a locking system for people testing the same file, or add
 version tags or something.
 - Nothing EVER gets `damove`d to another repo.  Go rebuild it and upload
 to -dev as usual.
 - This NEVER gets added to an end-user's machine, not even for testing.

-- 
Ticket URL: <http://athena10.mit.edu/trac/ticket/967#comment:1>
Debathena <http://debathena.mit.edu>
MIT Debathena Project


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