Re: [Classpathx] Subversion Issues

[Chris Burdess]

On 18/01/14 21:18, Conrad T. Pino wrote:
> In general I see Subversion content is appropriately POSIX focused.
> 
> I see some svn:executable inconsistencies which matter on POSIX.
> 
> svn:eol-style property is absent and files are POSIX newline style.
> 
> In addition we're attempting a formal GNU JavaMail release cycle.
> 
> Therefore I propose:
> 
> 1. We apply property revisions as they are found to /trunk since
> these should not affect file content nor bug fix releases.
> 
> 2. We create a next release candidate branch that allows broken
> builds to facilitate cross platform development.
> 
> 3. The next release candidate branch shall closely track commits
> made to /trunk from time to time.
> 
> 4. Upon acceptance, the next release shall be merged into /trunk.
> 
> If above is accepted, what shall next release candidate path be?

I don't think it's necessary to do a complete branch and merge since
nothing is likely to change on trunk in the meantime. We can just work
off trunk as a release candidate and then branch when we release to make
a snapshot.