Difference between revisions of "SME Server:Release Management"
m |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{WIP box}} | |
| + | |||
| + | == Koozali SME Release procedures == | ||
The Koozali SME Server release procedure by the release manager (Terry Fage): | The Koozali SME Server release procedure by the release manager (Terry Fage): | ||
| − | + | ||
| + | === ISOs === | ||
1. Receive a heads up from the devs on a new (Alpha/Beta/Final/Minor/Major) release. | 1. Receive a heads up from the devs on a new (Alpha/Beta/Final/Minor/Major) release. | ||
| − | 2. He then would | + | 2. He then would prep release notes and change logs based on information given from the devs |
3. He then would team up with documentation team and plan all required additions/changes to the wiki | 3. He then would team up with documentation team and plan all required additions/changes to the wiki | ||
| Line 24: | Line 27: | ||
10. He then would double check if all of the above has been finished before the mirrors are fully synced globally | 10. He then would double check if all of the above has been finished before the mirrors are fully synced globally | ||
| + | |||
| + | |||
| + | === RPMs=== | ||
| + | |||
| + | ====Repos==== | ||
| + | |||
| + | Where do packages go one they are added to buildsys? | ||
| + | |||
| + | Base packages | ||
| + | smedev > smetest > smeupdates-testing > smeupdates | ||
| + | |||
| + | Contribs | ||
| + | smedev > smetest > smecontribs | ||
| + | |||
| + | |||
| + | ===Version release Notes=== | ||
| + | |||
| + | https://wiki.contribs.org/Category:Release_Note | ||
Latest revision as of 11:56, 13 November 2018
Koozali SME Release procedures
The Koozali SME Server release procedure by the release manager (Terry Fage):
ISOs
1. Receive a heads up from the devs on a new (Alpha/Beta/Final/Minor/Major) release.
2. He then would prep release notes and change logs based on information given from the devs
3. He then would team up with documentation team and plan all required additions/changes to the wiki
4. He then would ask a bugzila admin to create new tags in bugzilla for the new release, so issues can be reported properly
5. He then would report back to devs that the release procedure is ready and release is a go, so the ISO can be released.
6. ONLY then the dev team would release the new ISO, and synced to the mirrors
7. He then would announce it in the forums in the announcement section with comments disabled
8. Together with the documentation team, all wiki changes would be submitted, including release pages/notes and download links
9. He then would make announcements to the media about the release (if required) via several channels
10. He then would double check if all of the above has been finished before the mirrors are fully synced globally
RPMs
Repos
Where do packages go one they are added to buildsys?
Base packages smedev > smetest > smeupdates-testing > smeupdates
Contribs smedev > smetest > smecontribs
