Changes

   

   

When the developer is satisfied that a package won't break the system and wants wider testing without actually releasing things, the package should be moved manually into smeupdates-testing.  This is a semi-stable testing area that shouldn't break a system but hasn't been verified yet.  This repo is also included in Shad's staging area (stage) for the purpose of building the next ISO.  All verifications should be done on packages in smeupdates-testing. Once the package is verified, and agreement reached on the Go/NoGo for releasing, the package should be copied manually to smeupdates and released.

When the developer is satisfied that a package won't break the system and wants wider testing without actually releasing things, the package should be moved manually into smeupdates-testing.  This is a semi-stable testing area that shouldn't break a system but hasn't been verified yet.  This repo is also included in Shad's staging area (stage) for the purpose of building the next ISO.  All verifications should be done on packages in smeupdates-testing. Once the package is verified, and agreement reached on the Go/NoGo for releasing, the package should be copied manually to smeupdates and released.