Git-Url: http://git.frugalware.org/gitweb/gitweb.cgi?p=frugalware-current.git;a=commitdiff;h=268acce02aecd1eff7269f56a1f2829f0b810d4f
commit 268acce02aecd1eff7269f56a1f2829f0b810d4f Author: Miklos Vajna <[EMAIL PROTECTED]> Date: Sun Jul 27 20:16:12 2008 +0200 docs/security: improve the 'How to release an FSA' section diff --git a/docs/security.txt b/docs/security.txt index 08a7fe8..448b53b 100644 --- a/docs/security.txt +++ b/docs/security.txt @@ -23,12 +23,21 @@ issue in -stable and releases a new FSA. == How to release an FSA? -. Check if the backport is ready (the binary packages should be uploaded for -each arch). +. Open the -stable Changelog file of the package. There you can see the + vulnerable and unaffected versions of the package. -. Update the frugalware/xml/security.xml file in the homepage-ng repo and check -if the mail is sent to the frugalware-security list. If not, then ask on -devel -what can be the problem. +. Check if the backport built by syncpkgd is ready (the binary packages + should be uploaded for each arch). + +. Add a new entry to the frugalware/xml/security.xml file in the + homepage-ng repo. + +. Commit, push. The commit hook will check if the xml is valid, so most + common errors can be avoided. In rare cases, the announcement may not + appear on the frugalware-security list. If this is the case, then ask + on -devel about what the problem can be. + +. Close the task in the BTS, filing in FSAxxx in the closure message. == How to notice security issues _______________________________________________ Frugalware-git mailing list Frugalware-git@frugalware.org http://frugalware.org/mailman/listinfo/frugalware-git
