3,267
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − +
→Propose a Feature into an activity
* 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).