Difference between revisions of "Development Team/Release"
Jump to navigation
Jump to search
(New page: == New features proposal == At the beginning of each release cycle, maintainers will send a proposal for each major new feature they plan to develop on the sugar mailing list for discussi...) |
|||
| Line 1: | Line 1: | ||
== New features proposal == | == New features proposal == | ||
| − | At the beginning of each release cycle, maintainers will | + | At the beginning of each release cycle, maintainers will write a proposal for each major new feature they plan to develop. They will be discussed on the Sugar mailing list, revises on the base of the feedback and made available on the wiki. New modules will require explicit approval by the release team. |
As part of this new activities will be proposed for inclusion. Criteria for approval will be: | As part of this new activities will be proposed for inclusion. Criteria for approval will be: | ||
Revision as of 03:56, 10 May 2008
New features proposal
At the beginning of each release cycle, maintainers will write a proposal for each major new feature they plan to develop. They will be discussed on the Sugar mailing list, revises on the base of the feedback and made available on the wiki. New modules will require explicit approval by the release team.
As part of this new activities will be proposed for inclusion. Criteria for approval will be:
- The maintainer is willing to follow the Sugar schedule.
- Supports internationalisation and localisation.
- Does not duplicate the functionalities of other activities.
- ...