User Tools

Site Tools


mantisbt:role_packager

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
mantisbt:role_packager [2007/01/23 00:24]
vboctor created
mantisbt:role_packager [2011/11/16 07:35] (current)
atrol The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file.
Line 5: Line 5:
 ===== General ===== ===== General =====
  
-  * Typically they have experience in packaging products or are the packagers for Mantis for one or more distributions.+  * Typically they have experience in packaging products or are the packagers for Mantis for one or more distributions. [giallu: I think it is very unlikely to be the packager on more of one distro, not a big deal though...]
   * The packaging team will have CVS commit access (same access level as Mantis developers and globalization team).   * The packaging team will have CVS commit access (same access level as Mantis developers and globalization team).
  
Line 16: Line 16:
  
   * Maintain a list of Linux distributions that include Mantis.   * Maintain a list of Linux distributions that include Mantis.
-  * Maintain a list of Linux distributions that we should approach to include Mantis.+  * Maintain a list of Linux distributions that we should approach to include Mantis. [giallu: do we really want to actively do this? ]
   * Keep close communication with Mantis packagers and Linux distributions.   * Keep close communication with Mantis packagers and Linux distributions.
   * Responsible for integrating patches supplied to them by Mantis packagers.   * Responsible for integrating patches supplied to them by Mantis packagers.
   * Work with Linux Distributions that provide a list of issues that need to be done for them to include Mantis.   * Work with Linux Distributions that provide a list of issues that need to be done for them to include Mantis.
-  * Communicate to packagers and Linux distributions that only Mantis stable releases should be included in their distributions (whether stable or unstable).+  * Communicate to packagers and Linux distributions that only Mantis stable releases should be included in their distributions (whether stable or unstable). [giallu: this is not easy for all distros. For example, anyone feel free to correct me if I am wrong, debian stable is "stable" in the sense it will not change much overtime, and that only critical fixes are applied to packages, usually by backporting the patch]
   * Packagers can also use the “Contact Us” page to send emails to myself (vboctor) directly, then I can address or re-direct them to the appropriate news group or individuals.   * Packagers can also use the “Contact Us” page to send emails to myself (vboctor) directly, then I can address or re-direct them to the appropriate news group or individuals.
  
 ===== Security Bugs and Advisories ===== ===== Security Bugs and Advisories =====
 +[giallu: this whole section seems quite orthogonal to the packaging issue; of course distro packagers are interested in security issues/patches, but this list seems more suited for a security team, not a packaging one]
  
   * Manage the process of porting security bugs to the latest stable branch and make sure there are bugs to track such porting work (with summary starting with "Port:" prefix and adding a relationship of type "related").   * Manage the process of porting security bugs to the latest stable branch and make sure there are bugs to track such porting work (with summary starting with "Port:" prefix and adding a relationship of type "related").
Line 37: Line 38:
   * Security fixes should include a description of the fix.  It can be explanation of how to apply the fix, a patch, etc.  This should allow packagers to apply the fix, users who are not ready to upgrade to also do the same.   * Security fixes should include a description of the fix.  It can be explanation of how to apply the fix, a patch, etc.  This should allow packagers to apply the fix, users who are not ready to upgrade to also do the same.
   * Advisories that are hosted on the Mantis website will be hosted on the wiki and will be all linked from an index page.  The index page should include a table with information like: date, CVE, bug #s, versions affected, and summary.   * Advisories that are hosted on the Mantis website will be hosted on the wiki and will be all linked from an index page.  The index page should include a table with information like: date, CVE, bug #s, versions affected, and summary.
 +
mantisbt/role_packager.1169529896.txt.gz · Last modified: 2008/10/29 04:31 (external edit)