Difference between revisions of "Updates cycles"
From SME Server
Jump to navigationJump to search| Line 6: | Line 6: | ||
They are: | They are: | ||
| − | -dev [corresponds to smedev in the mirrors] | + | -dev [corresponds to smedev in the mirrors] |
| − | -test [corresponds to smetest in the mirrors] | + | -test [corresponds to smetest in the mirrors] |
| − | -updates-testing [corresponds to smeupdates-testing in the mirrors] | + | -updates-testing [corresponds to smeupdates-testing in the mirrors] |
| − | -updates [corresponds to smeupdates in the mirrors] | + | -updates [corresponds to smeupdates in the mirrors] |
In addition, there is a staging area (stage) that is used to build the next ISO, you will see reference to it in some repository update emails. | In addition, there is a staging area (stage) that is used to build the next ISO, you will see reference to it in some repository update emails. | ||
Revision as of 15:33, 2 December 2012
OVERVIEW
The SME Server update and maintenance cycle consists in the management of a number of repositories and package categories.
Repositories
The master directories associated with the update and maintenance cycles are located on the build system. Their content is then propagated to the mirrors.
They are:
-dev [corresponds to smedev in the mirrors] -test [corresponds to smetest in the mirrors] -updates-testing [corresponds to smeupdates-testing in the mirrors] -updates [corresponds to smeupdates in the mirrors]
In addition, there is a staging area (stage) that is used to build the next ISO, you will see reference to it in some repository update emails.
