User:RobertKaye/Schema Change Release May 2012: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
== Tickets under consideration for May 15 2012 ==
== Tickets under consideration for May 15 2012 ==

=== Unclear tickets ===

The following tickets are not clearly specified:
* http://tickets.musicbrainz.org/browse/MBS-1385
* http://tickets.musicbrainz.org/browse/MBS-4337

Please provide more information on these tickets.


=== Conflict tickets ===
=== Conflict tickets ===
Line 18: Line 10:
=== Clearly stated tickets ===
=== Clearly stated tickets ===


These tickets seem relatively simple and can proceed without too much trouble:
These tickets appear to be cleanly stated and nearly actionable:


* http://tickets.musicbrainz.org/browse/MBS-2885
* http://tickets.musicbrainz.org/browse/MBS-2885
Line 28: Line 20:
* http://tickets.musicbrainz.org/browse/MBS-1799
* http://tickets.musicbrainz.org/browse/MBS-1799
* http://tickets.musicbrainz.org/browse/MBS-1798
* http://tickets.musicbrainz.org/browse/MBS-1798
* http://tickets.musicbrainz.org/browse/MBS-1385
* http://tickets.musicbrainz.org/browse/MBS-4337


== Next Steps ==
== Next Steps ==
Line 33: Line 27:
For each of these tickets, we will require the following two pieces of work:
For each of these tickets, we will require the following two pieces of work:


* Specify exactly what the user interface changes will be. Mock ups would be great. Due date: April 2
* Oliver and Warp will review these tickets and sanity check the proposed schema changes. Due date: 29 March
* Specify exactly what the user interface changes will be. Mock ups would be great. Due date: 2 April
* Specify exactly what the database changes will be. We will need to have an exact database table change proposal. Exactly which columns will be added/removed/modified and what new tables will be created. If you cannot specify the changes to be done, chase down a developer to specify them for you. Bonus points if the change is described in actual SQL statements. Due date: March 26



Tickets that do not provide the required information by the given due date will be removed from the 2012-05-15 schema change.
Tickets that do not provide the required information by the given due date will be removed from the 2012-05-15 schema change.

Revision as of 23:50, 26 March 2012

Tickets under consideration for May 15 2012

Conflict tickets

This ticket is a lot of work and may conflict with a Summer of Code proposal:

I'm unsure how to proceed with this ticket.

Clearly stated tickets

These tickets appear to be cleanly stated and nearly actionable:

Next Steps

For each of these tickets, we will require the following two pieces of work:

  • Oliver and Warp will review these tickets and sanity check the proposed schema changes. Due date: 29 March
  • Specify exactly what the user interface changes will be. Mock ups would be great. Due date: 2 April


Tickets that do not provide the required information by the given due date will be removed from the 2012-05-15 schema change.