1,574
edits
Changes
Jump to navigation
Jump to search
Line 286:
Line 286: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→ISSUE RELEASE NOTES
This update can be installed with the Software Installer from the Server Manager.
This update can be installed with the Software Installer from the Server Manager.
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#Software_Installer_Panel
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#Software_Installer_Panel
==MANAGING UPDATE AND RELEASE NOTES USING RNOTES.==
Ian Wells has over the years developed a webpage intended to assist in the management of pending updates and the creation of release notes. It consists of a number of perl scripts that generate a site at http://wellsi.homeip.net/rnotes/. Whilst the information found there is not essential to any update, it is a valuable tool design to streamline the overall process. It does an analysis of the packages in smeupdates-testing (both SME 7 & SME 8) and tries to work out what can be released, and if there are problems.
The site is subdivided into one html file per SME Server release, it updates every 8 hours.
SME 8: http://wellsi.homeip.net/rnotes/sme8/8bugreport.html
SME 7: http://wellsi.homeip.net/rnotes/bugreport.html
Each of the section above have a number of tabs, they are:
===Summary===
Summary of bugs for relevant version of SME on the day of query
===Overview===
Release Notes Overview - Work in progress - on the day of query
===SRPMs===
SRPMs content (note that the SRPMs list may be shorter than the RPMs list because some SRPMs generates multiple RPMs depending on the .spec file).
===RPMs===
RPMs content.
===Bug Report===
Report of packages associated with each bug. there are also links to relevant Bugs (click on the Bug number) and to an automated release notes (click on "notes"). One can also access ALL draft release notes for sme7 and sme8 by just looking at http://wellsi.homeip.net/rnotes/notes/
===Status.===
Status of each bug. The bugzilla product is highlighted if not matching the SME Version
You may see entries like ‘7026 <No Product Found> Access Denied’ that means it is a security bug.
===Simple.===
A simple list of bugs
===Missing Bugs Numbers.===
Changes without bug numbers - should always be empty if our devs remember to include a bug number in the changelog.
===Verified Package Versions===
This gives some hints as to which packages can be released to smeupdates - if it’s all green then it should be good to go.. It does not yet check the depends/blocks from bugzilla. It also only goes green when a bug and all dependents are Verified. When it cannot retrieve the status (as is the case with security bugs) it marks them as NA and colours them black, manual checking is advised.
===Smetest Files===
This lists packages provided as part of a SME Server release which have a newer version in smetest.
It is likely that these should be moved to smeupdates-testing.
Note 1: when compiling status of updates it is good to cross-reference the actual packages (RPMs) in the release queue (smetest/smeupdates-testing) with the bugzilla matrix and investigate where they don't match.
Note 2: final release notes consist of a script generated templates with some manual additions. Ideally the only changes needed to the automatically generated release notes would be the description of the update, in the part ‘<Insert Update Text Here>’ in the template. What was wrong, what was fixed, and any additional end-user information. This is the only challenging part. It is good to put links to additional information in the References section, as an example, check the release note for clamav 0.97.6-1 above.
Note 3: the template is only an aid, it may not be correct. You should check that:
- The version/release match the changelog
- The bug in references match the changelog - for security bugs, this needs to be added manually
- The RPMs & SRPMs listed match the changelog