SeaMonkey:First Release: Difference between revisions

m
The text needed wrapping
m (The text needed wrapping)
Line 22: Line 22:


Quoting Ben Goodger from IRC:
Quoting Ben Goodger from IRC:
  <ben_> so here's what you need to do to ship a release. 1. decide what you want out of it (a good start is to develop a product plan in wiki.mozilla.org with checkmarked features/etc) 2. find engineers to do each of the items in the aforementioned list 3. get those engineers to provide blurb+swag for each - this is a description of the item + estimated time to completion or an ETA. 4. have them implement the features. 5. deal with bugs that arise, manage the
  <ben_> so here's what you need to do to ship a release.  
  <ben_> 6. when your features are done, you can beta... when you get to a low level of remaining bugs, you can kick off the final release process.  
        1. decide what you want out of it (a good start is to develop a product plan in  
          wiki.mozilla.org with checkmarked features/etc)  
        2. find engineers to do each of the items in the aforementioned list 3.  
          get those engineers to provide blurb+swag for each - this is a description of  
          the item + estimated time to completion or an ETA.  
        4. have them implement the features.  
        5. deal with bugs that arise, manage the
  <ben_> 6. when your features are done, you can beta... when you get to a low level of  
        remaining bugs, you can kick off the final release process.  
  <Callek> ben_ 5. Deal with bugs that arise, manage the  ...??? (cut off)
  <Callek> ben_ 5. Deal with bugs that arise, manage the  ...??? (cut off)
  <ben_> the final release process involves things like documenting changes (release noets, product pages, etc).  
  <ben_> the final release process involves things like documenting changes (release noets,
  <ben_> er, "manage them using bugzilla flags, etc. prioritize them and have people work on those."
        product pages, etc).  
  <ben_> ... getting testing builds spun, having interested users test them and submit feedback, driving the list to zero and handling new bugs as they come in.
  <ben_> er, "manage them using bugzilla flags, etc. prioritize them and have people  
        work on those."
  <ben_> ... getting testing builds spun, having interested users test them and submit feedback,  
        driving the list to zero and handling new bugs as they come in.
  <ben_> Asa probably has more info on the latter half of this process.  
  <ben_> Asa probably has more info on the latter half of this process.  
  <ben_> but what I would suggest starting with is saying, "what do we want from Seamonkey 1.8?"  
  <ben_> but what I would suggest starting with is saying, "what do we want from Seamonkey 1.8?"  
24

edits