1,574
edits
Changes
Jump to navigation
Jump to search
Line 417:
Line 417: − + + Line 426:
Line 427: − + + − + + Line 468:
Line 471: − +
→PACKAGES UPDATE CYCLE
The life of packages under the responsibility of the updatesteam starts in smetest. Leaving aside contribs (they are the responsibility of individual maintainers), there are three distinct scenarios:
The life of packages under the responsibility of the updatesteam starts in smetest. Leaving aside contribs (they are the responsibility of individual maintainers), there are three distinct scenarios:
First scenario: SME modified packages
===First scenario: SME modified packages===
- Step one. Packages created in smetest should be summarely tested by the developer to ensure that it installs correctly. Particular attention should be given to accurate changelog including a reference to the bug report. The bug is then resolved FIXED, and a copy of the changelog including package name provided at time of resolution.
- Step one. Packages created in smetest should be summarely tested by the developer to ensure that it installs correctly. Particular attention should be given to accurate changelog including a reference to the bug report. The bug is then resolved FIXED, and a copy of the changelog including package name provided at time of resolution.
- Step four. The package is then moved to smeupdates for release, release notes issued and possibly announce in the Forums if applicable. This could be scheduled in batch weekly unless urgent fix.
- Step four. The package is then moved to smeupdates for release, release notes issued and possibly announce in the Forums if applicable. This could be scheduled in batch weekly unless urgent fix.
Second scenario: clamav packages
===Second scenario: clamav packages===
- Step one. Updatesteam raises a bug as soon as packages appear in smetest.
- Step one. Updatesteam raises a bug as soon as packages appear in smetest.
- Step two. Moved to updates-testing.
- Step two. Moved to updates-testing.
- Step three. Fast track verification and release + release notes.
- Step three. Fast track verification and release + release notes.
Third scenario: Upstream packages and kernel mods excluding clamav
===Third scenario: Upstream packages and kernel mods excluding clamav===
- Step one. Identify relevant packages by looking at all the RPMs, Changelogs, and Bugzilla. To find the upstream RPMs compare smetest to smeos. Rnotes simplify this process.
- Step one. Identify relevant packages by looking at all the RPMs, Changelogs, and Bugzilla. To find the upstream RPMs compare smetest to smeos. Rnotes simplify this process.
how do you deal with this class of packages?
how do you deal with this class of packages?
How do you generally deal with upstream packages not found in smeos?
How do you generally deal with upstream packages not found in smeos?
==ABOUT THE MIRRORS==
==ABOUT THE MIRRORS==