User:Norv/dev/team: Difference between revisions From Online Manual

Jump to: navigation, search
(Created page with " ==The development team responsibilities (rough outline)== * Maintain a roadmap to plan for the short-term and long-term development of SMF software ** Review current and comin...")
 
Line 1: Line 1:
Please note that this page is obsolete. (even though essentially correct). It's copied from an old document, and should be rewritten fully to document the roles and entrance process.





Revision as of 14:44, 9 December 2011


Please note that this page is obsolete. (even though essentially correct). It's copied from an old document, and should be rewritten fully to document the roles and entrance process.


The development team responsibilities (rough outline)

  • Maintain a roadmap to plan for the short-term and long-term development of SMF software
    • Review current and coming technology, to make sure SMF stays current.
    • Provide direction and leadership to discussions of the future of SMF.
    • Review and select features for future versions.
    • Monitor the bug trackers and get feedback from the beta testers.
    • Monitor and address security reports, and keep the SC informed of all security issues.
  • Develop new versions of SMF.
    • Work with beta testers to make sure new features are tested adequately.
    • Fix bugs.
    • Provide useful "changelog" comments with every code check-in.
  • Release SMF versions to the community
    • Determine when the latest version of SMF is ready for release
    • Provide a changelog, derived from commit comments, to accompany each release of SMF.
    • Prepare the upgrade, update, and full install sets for each SMF release
    • Make the install sets available on the SMF website
    • Work with the SMF team to make an announcement of each SMF release
  • Work with and communicate with other SMF teams and the community.
    • Assist with support, when advice from a developer is needed.
    • Keep the other teams up-to-date on changes (Support needs to support it, Doc needs to write about it, and Customization needs to know about new best practices).
    • Manage the code repositories, including user accounts.
    • Communicate plans and progress to the SMF team and community.


Advertisement: