Difference between revisions of "Talk:Features/Policy"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too. | * As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too. | ||
| − | * The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process. | + | * The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process. (Another solution is to handle each Feature by the activity maintainer itself). |
Latest revision as of 07:07, 4 December 2009
Activity Process for Activities
Propose a Feature
The Feature can be proposed the same way than any other Feature.
Propose a Feature into an activity
The Process for inclusion of an Activity Feature into an activity release is similar to that of a Feature for Sucrose. The Feature must have an owner, there must be community consensus etc. There are two main differences:
- As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.
- The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process. (Another solution is to handle each Feature by the activity maintainer itself).