page3
New Features flow
Once again, the nature of our project means that we develop new features in several different branches and doesn't always reflect the more classic schema of many other upstream projects.
Our goal is to make sure that features are designed properly and are propageted consistently across our product range.
While the bug fixes flow is pretty much standard and can easily be reflected into a schema, the feature one is not. It requires a lot of careful attention.
The best way to handle features is to communicate with the team about them. Do not start a one-man job on any feature. There will always be little corners of the project that your new feature could break or make it too complex to maintain in the long run. Basically make sure that your feature has been approved by the whole team with a clear plan on what products should receive the change and why.
When thinking about features, try to take into account (just a few notes here):
1) will the customers or users expect this feature forever?
2) is it worth to develop this feature at all?
3) does QE have resources to test this feature?
4) can we support it across our product range?
5) can GSS provide support for it?
6) can somebody else maintain it for you?
7) did PM ask for it? If so make sure that you fight it as much as you can... it's probably useless :)