[Classpathx] Subversion Issues

[Conrad T. Pino]

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?

Conrad Pino