Actions

Developer Area/Developer Meetings/2011-06-29: Difference between revisions

From Mahara Wiki

< Developer Area‎ | Developer Meetings
(proposal to change the bug status policy)
No edit summary
Line 5: Line 5:
## every new feature on master should have a bug report associated with it
## every new feature on master should have a bug report associated with it
## fixes for bugs that have never been in a release should be marked as "fix released" with no milestone
## fixes for bugs that have never been in a release should be marked as "fix released" with no milestone
## when using 'fix committed', you must set the milestone to indicate which release will get that fix
# Something Else [Person]
# Something Else [Person]
# Next meeting
# Next meeting
# Any other business
# Any other business

Revision as of 22:31, 21 Haziran 2011

Agenda for the 8th Mahara Developer Meeting

  1. Items from previous meeting
  2. Bug status proposal: [Francois]
    1. every new feature on master should have a bug report associated with it
    2. fixes for bugs that have never been in a release should be marked as "fix released" with no milestone
    3. when using 'fix committed', you must set the milestone to indicate which release will get that fix
  3. Something Else [Person]
  4. Next meeting
  5. Any other business