Trac

root/branches/README

Revision 4279, 1.4 kB (checked in by jwage, 4 months ago)

Updating branches information.

Line 
1 = Branch Overview =
2
3 == branches/0.10 ==
4
5 The 0.10 branch is the latest stable version of Doctrine. This
6 branch is recommended for use with production projects.
7
8 == branches/0.11 =
9
10 The 0.11 branch is where we are preparing the next latest stable
11 version of Doctrine. This branch will replace the 0.10 branch as
12 soon as it is ready.
13
14 == branches/experimental ==
15
16 An experimental branch should be created for undertaking a change
17 which is especially time-consuming and/or risky, especially if
18 during that change it may render the codebase unusable by other
19 developers.
20
21 An experimental branch should have a name which begins with the
22 name of the developer and also includes a descriptive title,
23 like dbrewer-rewrite-doctrine-in-LOLCODE. An example experimental
24 branch url might be:
25
26 http://svn.phpdoctrine.org/branches/experimental/dbrewer-rewrite-doctrine-in-LOLCODE.
27
28 == branches/ticket ==
29
30 A ticket branch may be created to deal with the changes required
31 by a specific Trac ticket.  You might want to do this if you are
32 working on a complicated ticket which will require extensive
33 changes, but want to be able to apply all the required changes to
34 the trunk or a branch as one clean merge.
35
36 These branches are always named using the number of the ticket,
37 and are located in branches/ticket. An example ticket
38 branch url might be:
39
40 http://svn.phpdoctrine.org/branches/ticket/560.
Note: See TracBrowser for help on using the browser.