Difference between revisions of "DevelopmentModel"

From Claws Mail FAQ
Jump to navigationJump to search
(first version)
 
m (Reverted edit of Youngtyrant84, changed back to last version by Claws)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Claws Mail Development Model ==
 
== Claws Mail Development Model ==
  
   Stage 0: Propose ideas/goals
+
   Stage 0: Release of a new .0 version
 
    
 
    
   Stage 1: Some bug fixing
+
   Stage 1: Propose ideas/goals
 
    
 
    
   Stage 2: Implementation, single developer testing and committing to CVS
+
   Stage 2: Implementation, single developer testing and committing to CVS.
 +
          Fix bugs.
 
    
 
    
 
   Stage 3: Synchronization and multiple developer (and CVS users) testing,  
 
   Stage 3: Synchronization and multiple developer (and CVS users) testing,  
           unless the code is mature enough, go to 1 or 2 (or even 0).
+
           unless the code is mature enough, go to stage 2 (or 1).
           From time to time, migrate mature features to stable branch.
+
          Fix bugs.
 +
           From time to time, migrate bugfixes to stable branch.
 
    
 
    
 
   Stage 4: Depending on the goals reached, code maturity, moon phase and  
 
   Stage 4: Depending on the goals reached, code maturity, moon phase and  
 
           other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.
 
           other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.
 +
          Fix bugs.
 
    
 
    
   Stage 5: Magic happens here.
+
   Stage 5: Fix bugs.
 +
          Magic happens here.
 
    
 
    
   Stage 6: Feature freeze (usually 2 weeks before 8).
+
   Stage 6: Feature freeze 2 weeks before stage 8).
 +
          Fix bugs.
 +
 
 +
  Stage 7: String freeze 1 week before stage 8).
 +
          Fix bugs.
 +
 
 +
  Stage 8: Release a new shiny .0 version.
 +
          Collect donations, get rich.
 
    
 
    
   Stage 7: String freeze (usually 1 week before 8).
+
   Stage 9: Go to stage 0.
 
 
  Stage 8: Release a new shiny version.
 
  
 
Motto: All of this can change at developers will. Code must flow.
 
Motto: All of this can change at developers will. Code must flow.

Latest revision as of 09:29, 23 January 2013

Claws Mail Development Model

 Stage 0: Release of a new .0 version
 
 Stage 1: Propose ideas/goals
 
 Stage 2: Implementation, single developer testing and committing to CVS.
          Fix bugs.
 
 Stage 3: Synchronization and multiple developer (and CVS users) testing, 
          unless the code is mature enough, go to stage 2 (or 1).
          Fix bugs.
          From time to time, migrate bugfixes to stable branch.
 
 Stage 4: Depending on the goals reached, code maturity, moon phase and 
          other variables, release a stable bugfix, a beta, or a rc.
          Fix bugs.
 
 Stage 5: Fix bugs.
          Magic happens here.
 
 Stage 6: Feature freeze 2 weeks before stage 8).
          Fix bugs.
 
 Stage 7: String freeze 1 week before stage 8).
          Fix bugs.
 
 Stage 8: Release a new shiny .0 version.
          Collect donations, get rich.
  
 Stage 9: Go to stage 0.

Motto: All of this can change at developers will. Code must flow.