Confirmed users
1,193
edits
MDN/Development/Process: Difference between revisions
Jump to navigation
Jump to search
→Handling minor problems
No edit summary |
|||
| Line 59: | Line 59: | ||
=== Handling minor problems === | === Handling minor problems === | ||
Occasionally, the team runs into minor errors, usually in the form of error emails. These problems are usually not much of a problem on their own, but they can pile up over time. To handle this, the person affected should open a bug with the keyword [dev-papercut] in the status whiteboard. The team will watch a list of [ | Occasionally, the team runs into minor errors, usually in the form of error emails. These problems are usually not much of a problem on their own, but they can pile up over time. To handle this, the person affected 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. | ||