Development/Priorities

From MusicBrainz Wiki
< Development
Revision as of 14:22, 20 July 2015 by RobertKaye (talk | contribs) (Created page with "This page attempts to outline the development team's priorities in broad strokes -- this priority list should serve as a general guideline for our team to decide what to work ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page attempts to outline the development team's priorities in broad strokes -- this priority list should serve as a general guideline for our team to decide what to work on.

Summer 2015

For summer 2015, following RobertKaye taking over the development leadership of the MusicBrainz team, the following priorities exist for the dev team, in order of most important to least important:

  1. Site stability and performance issues: If the site is misbehaving or not performing as it should, the dev team should focus on resolving those issues as the first priority.
  2. ModBot/Nagios: If ModBot or Nagios sends periodic emails about an issue, the dev team should address these issues quickly. ModBot fixes may not require hot-fixes, but they should be addressed as soon as possible.
  3. Community improvement features: The only new features that we're going to focus on in the short term are features that address problems within our community. (e.g. MBS-1801)
  4. Bug fixing/finishing existing features: Fixing bugs or finishing tasks left over from the recent schema change.
  5. Apply new branding to musicbrainz.org: In lieu of moving to a full bootstrapped site, we should do minor cosmetic changes to the existing header bar and update the site to use the new MusicBrainz colors.
  6. New features: Creating new features or starting new sub-projects should not be considered this summer, since we have a lot of things that are higher priorities.
  7. New schema change features: Aside from finishing the May 2015 schema change features, we're not going to have another schema change in 2015. We're skipping the fall schema change.


Autumn 2015

The priorities for autumn have not been set yet -- please check back at the beginning of autumn.

Important note: We are not going to have a schema change release near October 15th. We're now well into summer and we still have not finished the schema change release UI from the last release. We really need a break from schema changes to focus on community related features.