[cross posting] New Policy for Moving Packages to Dockyard

Per this afternoon/evening's team meeting, we have established the 
following policy for package moves.

PLEASE adhere to this policy. It is very much core to assuring product 
quality.


1) The builder of a package must NEVER move his own packages to dockyard. 
--Exception-- If you have repeatedly asked another developer to 
test/move your package, and have not
received a response, and the package has not moved for >=14 days, you 
may move it yourself.
2) Once a package is built, you should ask another developer to test the 
package.  When you do this, you should
inform that developer as to what aspects should be tested, and what 
equates to a working package.
3) If time is not an option, repeat step 2 with another developer, then 
ask that developer to move the package to dockyard.

--IF at any point during steps 2 or 3, the package fails, the process 
starts over--

--IF you see stale packages in the needsmoving queue, contact the 
builder and enquire about the status. DO NOT MOVE THEM
WITHOUT KNOWING THEIR STATUS!--

-- IF you are building a string of dependencies, please notify 
devel-list and inform us about what the various packages in the string
include--

(do not think this is optional simply because I said 'please'.  
Following these guidelines will help assure that dockyard
remains a stable environment. If this policy is not followed, and leads 
to a breakage in dockyard, you MAY lose access to the build server)