Emmanuel Lecharny wrote:
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are applicable
to the
trunk.
I'm not quite sure I understand what you mean by renaming it to
1.0-trunk.
The svn URL is .../mina/asyncweb/branches/1.0/... Do you mean to
rename it
to .../mina/asyncweb/trunk/1.0/...?
Well, it's more a question about what we see as a branch.
Usually, when releasing, we start by freezing the trunk into a branch,
like what we did in 1.0
and if we want to start a new version, we do it in another branch.
In your case, the 1.0 branch is not a version, it's just a target. In
order to avoid confusion with a frozen version, it should be named
1.0-trunk.
Hope it's clearer ?!
I think I'm as confused as Sangjin. Should this be
".../mina/asyncweb/1.0-trunk/" as opposed to ".../mina/asyncweb/trunk/",
which is the 2.0 version? Also, should the existing branch be left
frozen, and this new working trunk be created as a copy of the frozen
branch?
I'm also +1 on this happening on the 1.0 branch. The 2.0 version does
not really look production-ready, and there were a lot of proposed
changes to that version that have never been implemented, so it isn't
really clear where things stand with that. Having some new features
implemented on a version that clearly has been used in a production
environment could only be a good thing.
Rick
