Generic Marketing release cycle schedule (draft)

[Paul W. Frields]

On Fri, Jul 31, 2009 at 04:11:15AM -0400, Mel Chua wrote:
> Attached.
>
> This is a draft of a skeleton schedule with all the milestones we'll have 
> to hit every release, to be customized at the start of each cycle to 
> create that cycle's particular schedule. (Because stuff like "alpha  
> readiness meeting" will be repeated every cycle, stuff like "get Fedora  
> Insight up and running" won't.)
>
> Emphasis on the word *draft.* Are there any other tasks that *must* be  
> completed every cycle? Tasks listed here that don't need to be done every 
> cycle?
>
> John, the formatting is pretty awful here - it might be easier to go  
> through and change the dates from things like "beta readiness mtg+1wk" to 
> things like "week 1 - week 3"... we can do that on gobby if you'd like.
>
> F12 schedule coming on Monday.

Mel, I'd probably put the Red Hat Brand coordination meeting earlier,
something like Alpha availability +1 week.  They need significant
headroom in their schedule for things like video production.

Paul



> Cleanup the wiki from the obsolete marketing cycles		start of cycle	start of cycle+1wk
> 
> Cycle the wiki pages to the new release                      start of cycle	start of cycle+1wk
> 
> Alpha Readiness Meeting				mtgdate			mtgdate         
> 
> List potential talking points and feature profiles			Feature freeze		Feature freeze+1wk
> 
> Decide format (podcast, video, text, etc) and provider (Docs or News) for each talking point and feature profile		Feature freeze+2wk	Feature freeze+3wk
> 
> In-depth feature profiles from 0% to 75% completion			Beta availability-6wks	Beta availability-2wks
> 
> Contact News beats people about topics/features we cover          as soon as feature profiles are 75% complete	that date +1wk
> 
> Drafts of talking points completed		beta availabiity-3wks	Beta availability-2wks
> 
> Beta Readiness Meeting                                     mtgdate	mtgdate
> 
> Open the call for release slogan suggestions                  beta readiness mtg-1wk	same
> 
> Release slogan selection                                 beta readiness mtg+1wk		same
> 
> Finish the in-depth feature profiles                     beta-2wks	beta
> 
> Meet with RH Brand to discuss additional/supplemental RH-provided marketing materials that may be coming out (video, press blog, etc)	beta	beta+1wk
> 
> Brief FAMSCo on talking points and propagate link to Ambassadors	beta-2wks	beta-1wk
> 
> Update the press kits                                    beta-1wk	  general avail-6wks
> 
> Final release slogan is ready for websites/design            beta readiness mtg - 2wks	same
> 
> Update and freeze the screenshots page                                    beta availability	+1wk
> Update and freeze the Fedora tour page                                    beta availability	+1wk
> 
> Brief News Distribution Network on tour page and other marketing materials created to date		beta-1wk	beta+1wk
> 
> Monitor community news sites and provide corrections and additional information as needed		beta-4wk	gen availability + 4wk
> 
> Final Readiness meeting                              mtgdate	mtgdate
> 
> GA Day social media explosion sprint                                               date	date

> -- 
> Fedora-marketing-list mailing list
> Fedora-marketing-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-marketing-list

-- 
Paul W. Frields                                http://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
  irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug