From Fedora Project Wiki
(Initial version)
 
Line 33: Line 33:
* Given how often people get the provides/obsoletes wrong is just one approval on the list enough?  
* Given how often people get the provides/obsoletes wrong is just one approval on the list enough?  
* Should approval come from provenpackagers or some other group? Or is maintainers enough?
* Should approval come from provenpackagers or some other group? Or is maintainers enough?
- I think Obsoletes/Provides check or so is needed and re-review is more proper than approval on mailing list. Anyway I don't think reapproval will take long if the original spec file was in good shape - Mamoru

Revision as of 17:52, 18 December 2008

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

Changelog

0.1: Initial draft

Existing Guideline

None

Proposed Guideline

Packages are sometimes renamed, either by upstream action or locally in the collection to more closely match NamingGuidelines. This policy explains the procedure for renaming packages.

  • Links to this proposed renamed package will be posted to the fedora-devel mailing list for inspection of the development community.
  • Once approved by another package maintainer, the package maintainer can request CVS for the newly named module citing the mailing list post approval.

Pages which will need changes

Discussion

  • Should a re-review be required instead of just a mailing list approval?
  • Given how often people get the provides/obsoletes wrong is just one approval on the list enough?
  • Should approval come from provenpackagers or some other group? Or is maintainers enough?

- I think Obsoletes/Provides check or so is needed and re-review is more proper than approval on mailing list. Anyway I don't think reapproval will take long if the original spec file was in good shape - Mamoru