Engagement/Websites/Firefox/Webteam: Difference between revisions

Line 37: Line 37:
We use milestones through the quarter. The first release of Q3 is 3.0, then next is 3.1, onwards on a weekly basis. To see which bugs are in each release follow the link within the WebDev Calender or conduct a query in Bugzilla. <br>  
We use milestones through the quarter. The first release of Q3 is 3.0, then next is 3.1, onwards on a weekly basis. To see which bugs are in each release follow the link within the WebDev Calender or conduct a query in Bugzilla. <br>  


==== Working With Us  ====
<h4> Working With Us  </h4>
 
<p>We want to help your web launch! Depending on the scope of your project follow the following steps to insure a smooth web launch.
Launching new site content? Submit your change via Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites here] under the www.mozilla.org/firefox Component. To make sure it gets triaged assign to Laura Forrest or Chrissie Brodigan. They will then field it to the necessary milestone based on current work happening on the site.&nbsp;  
</p><p>
 
<p>Want to launch a entire new page or website? schedule a meeting with Laura and Chrissie to get started.
If you're thinking of kicking off a larger project on the site then schedule a meeting with Laura and Chrissie to get started. Here's a [https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content in-depth overview] of how to launch an entire marketing campaign on Mozilla.org.&nbsp;
</p><p>Have an idea for a marketing campaign you'd like to see on the website? Here's a &lt;a href="https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content"&gt;in-depth overview&lt;/a&gt; of how to launch an entire marketing campaign on Mozilla.org.
 
</p><p>Want to tweak existing site content? Submit your change via Bugzilla &lt;a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites"&gt;here&lt;/a&gt; under the www.mozilla.org/firefox Component. To make sure it gets triaged assign to Laura Forrest or Chrissie Brodigan. They will then field it to the necessary milestone based on current work happening on the site.&#160;  
Note: if you file a bug and it's assigned to no-one, and it has no milestone, nothing will get done. Oh noes! Avoid that!  
</p>
 
</p><p>Note: if you file a bug and it's assigned to no-one, and it has no milestone, nothing will get done. Oh noes! Avoid that!  
===== I'm Launching X. Where Can it Go On Our Site?  =====
<p><br />
 
</p>
For all matters relating to content strategy and management talk to Laura Forrest
<h5> How Long Will It Take to Get My X Live?  </h5>
 
<p>&lt;p&gt;It depends! For the most part start with the assumption that any change will take at least 5 work developer work days before they are built, and then go live within a scheduled milestone. QA takes about 1 day. If your page contains any sort of functionality, add more time to that estimate.&#160; <br />
===== How Long Will It Take to Get My X Live?  =====
</p>
 
</p><p><br />
It depends! For the most part start with the assumption that any change will take at least 5 work developer work days before they are built, and then go live within a scheduled milestone. QA takes about 1 day. If your page contains any sort of functionality, add more time to that estimate.&nbsp; <br>
</p>
 
<br>  


== Related Links  ==
== Related Links  ==


[https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content Launching an Engagement campaign on Mozilla.org/firefox] (A How-to for PMMs and other Engagement folks)
[https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content Launching an Engagement campaign on Mozilla.org/firefox] (A How-to for PMMs and other Engagement folks)
Confirmed users
685

edits