db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "MoveAChangeBetweenBranches" by BryanPendleton
Date Tue, 23 Oct 2007 04:02:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by BryanPendleton:
http://wiki.apache.org/db-derby/MoveAChangeBetweenBranches

------------------------------------------------------------------------------
   * 10.1.2.x - As shown by sysinfo on the 10.1 branch
   * 10.2.0.x - As shown by sysinfo on the trunk
  
+ == Branches are generally more stable than the trunk ==
+ 
+ The point of the branch is to provide a stable always-working set of code that anyone can
take and make either a public release from or expect that a private release will work.  So
only bug fixes should go in, and a committer will usually exercise more caution when backporting
a fix than for a trunk check-in.
+ 
+ A committer may first check in a change to the trunk and then let it sit for a few days
before putting it into the branch.  This means that the community gets a chance to see the
change, the change gets tested against a wide variety of platforms, and there is time to run
at least one full set of tests with the change against the branch.  After a few days in trunk,
if no new bugs have been found across all the various platforms, the committer will generally
go ahead with the back port if appropriate. Note that each committer will use their experience
and judgement to determine what makes sense. 
+ 

Mime
View raw message