Websites/Mozilla.org/Roadmap 2011: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
=A Note On Naming=
=Roadmap=
 
Webdev has suggested we consider having rolling regular releases instead of adding things to the site in an ad hoc fashion to make scheduling resources easier.  We'll follow SUMO's [https://wiki.mozilla.org/Support/Kitsune#Roadmap Kitsune roadmap] as a template.
 
Proposal: Establish bi-weekly releases with the details of each release determined at a regular site planning meeting.
 
==1.0==
 
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=www.mozilla.com&target_milestone=1.0&product=Websites&classification=Other Bug list]
* Major tasks:
** Prepare for Firefox 4 launch
* Timeline:
** Code Freeze: January 6, 2011
** Push: January 11, 2011


Right now it is easy to talk about the Mozilla, Firefox and Thunderbird sites since they are different sites.  This will get more difficult when this content is consolidated together on www.mozilla.org.  To avoid confusion, we can just refer to them as sections instead of sites.
==1.1==


* The Firefox section is mozilla.org/firefox
* Bug list [TBD]
* The Thunderbird section is mozilla.org/thunderbird
* Major tasks:
* The Drumbeat section is mozilla.org/drumbeat
**
* The Mozilla section is mozilla.org/ (excluding Firefox, Thunderbird and Drumbeat sections)
* Timeline:
** Start: TBD
** Push: TBD


=Milestones=
=Milestones=


A list of high-level milestones for mozilla.org in 2011 in no particular order (timing will be discussed in the Roadmap section).
A list of high-level milestones for mozilla.org in 2011 in no particular order.


* Switch www.mozilla.com/firefox content to www.mozilla.org/firefox
* Switch www.mozilla.com/firefox content to www.mozilla.org/firefox
Line 37: Line 52:
* [[Mozilla.org/Roadmap_2011/Q2|Q2]]
* [[Mozilla.org/Roadmap_2011/Q2|Q2]]


=Roadmap=
=Open Questions=


Webdev has suggested we consider having rolling regular releases instead of adding things to the site in an ad hoc fashion to make scheduling resources easier.  We'll follow SUMO's [https://wiki.mozilla.org/Support/Kitsune#Roadmap Kitsune roadmap] as a template.
Is there an overview of what process we should follow when fixing bugs? How to nominate a bug for a milestone, when asking for QA, when to mark a bug as fixed in bugzilla, what are the new roles for trunk/stage/prod branches, stuff like that.


Proposal: Establish bi-weekly releases with the details of each release determined at a regular site planning meeting.
=A Note On Naming=


==1.0==
Right now it is easy to talk about the Mozilla, Firefox and Thunderbird sites since they are different sites.  This will get more difficult when this content is consolidated together on www.mozilla.org.  To avoid confusion, we can just refer to them as sections instead of sites.


* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=www.mozilla.com&target_milestone=1.0&product=Websites&classification=Other Bug list]
* The Firefox section is mozilla.org/firefox
* Major tasks:
* The Thunderbird section is mozilla.org/thunderbird
** Prepare for Firefox 4 launch
* The Drumbeat section is mozilla.org/drumbeat
* Timeline:
* The Mozilla section is mozilla.org/ (excluding Firefox, Thunderbird and Drumbeat sections)
** Code Freeze: January 6, 2011
** Push: January 11, 2011
 
==1.1==
 
* Bug list [TBD]
* Major tasks:
**
* Timeline:
** Start: TBD
** Push: TBD
 
=Open Questions=
 
Is there an overview of what process we should follow when fixing bugs? How to nominate a bug for a milestone, when asking for QA, when to mark a bug as fixed in bugzilla, what are the new roles for trunk/stage/prod branches, stuff like that.
canmove, Confirmed users
7,088

edits

Navigation menu