sometimes there is a 2.0.x branch that's like the trunk 2.0 fixes, while 2.1 or future releases are being worked on in the real trunk. that is if older releases are being maintained while new releases are being worked on.
ray, On 6/1/06, Doug Cutting <[EMAIL PROTECTED]> wrote:
Otis Gospodnetic wrote: > How should 2.0 fixes be handled? Should we fix things in branches/lucene_2_0 and then manually apply the same change to trunk immediately, or are people using svn merge a la http://svnbook.red-bean.com/en/1.0/re16.html ? Generally we should not change things in the branch, but rather continue to develop primarily in trunk, then sync applicable patches to the release branch with 'svn merge' when we're preparing to make a point release, including the revision range merged in the commit message. This makes it much easier to determine which patches have been sync'd to the release branch and which have not. Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
