Please do A, but only after reviewing the changes on trunk since you
branched and applying anything that still makes sense (or adapting
it). We don't want to lose anything (and there have been relevant
changes - even last time I checked)
You're going to have trouble tabulating these 'votes', but that's ok.
It looks enough like consensus.
- Brett
On 30/04/2007, at 1:33 AM, Jesse McConnell wrote:
+1 for option A, to move the branch to the trunk, I have worked on the
code on the branch a bit and I find it very sanely organized and very
extensible in parts dealing with repository scanning and whatnot. I
think within a few days of usage we'll be able to iron out the
majority of webapp oddities and there is a drive here to get some
alpha releases going of both continuum and archiva so I think there is
some momentum here...
nice job with it joakim
jesse
On 4/27/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
>
>
> An 0.9 release is not intended to attract users, it's intended
to deal
> with the fact that it already *has* users, and should have been
> officially released a long time ago.
>
> I'm not planning to make a big deal of it, a quiet mention on
the user
> list and a link at the bottom of the download page is plenty.
> Personally, I have this code in production and would like to see
this
> line of development nicely wrapped up rather than just abandoned.
I also use this codebase for my corporate job and will contribute to
maintain supported features in future releases. I just don't
understand why
a "0.9" release would change about the trunk code to be maintained
or not.
Do you just mean that having a (pre)release would make the supported
features included in the roadmap ? We still have to re-code them
in the
branch-code.
--
> Wendy
>
--
jesse mcconnell
[EMAIL PROTECTED]
