Confirmed users
1,193
edits
MDN/Development/Process: Difference between revisions
Jump to navigation
Jump to search
→Handling minor problems
| Line 57: | Line 57: | ||
Between the start of the Sprint and the end of the Sprint, the development team works on the features that they added to the Sprint Backlog. When a developer knows that he will be working on a particular feature, he assigns that feature to himself. When he knows that he will no longer work on it, he updates the feature to be unassigned so that someone else can begin working on it. | Between the start of the Sprint and the end of the Sprint, the development team works on the features that they added to the Sprint Backlog. When a developer knows that he will be working on a particular feature, he assigns that feature to himself. When he knows that he will no longer work on it, he updates the feature to be unassigned so that someone else can begin working on it. | ||
=== Handling | === Handling development annoyances === | ||
Occasionally, the team runs into minor | Occasionally, the team runs into minor annoyances that affect their development work, such as an error that causes an overwhelming amount of email. These problems are usually not much of a problem on their own, but they can pile up over time. To handle this, anyone affected by these issues should open a bug with the keyword [dev-papercut] in the status whiteboard. The team will watch a list of [http://mzl.la/UeVyMo ignored papercuts] to make sure they don't pile up. | ||
== Updating the MDN == | == Updating the MDN == | ||
During the sprint, we occasionally add our new features to the MDN by pushing code to our production server. We push about once per week (usually on Tuesdays or Thursdays) and avoid pushing on Mondays and Fridays. | During the sprint, we occasionally add our new features to the MDN by pushing code to our production server. We push about once per week (usually on Tuesdays or Thursdays) and avoid pushing on Mondays and Fridays. | ||