On Mon, 8 Sep 2003, robert burrell donkin <[EMAIL PROTECTED]> wrote:
i don't think that jakarta.apache.org/builds is the right place to store release candidates any more. where should release candidates now be stored? under cvs.apache.org?
Well, we've taken a very long time to sort things out, and during that period the idea of what should be placed where has changed quite a few times. I wouldn't blame anybody for not following the discussion and not moving files with every new decision - and jakarta/builds has been used in Jakarta land for a very long time.
Having said that, my understanding of the current policy:
nightly build -> cvs.apache.org/builds
latest release candidates, betas, alphas, milestones -> cvs.apache.org/dist
current stable release -> mirrored via www.apache.org/dist
older stable releases -> archive.apache.org/dist
good. (that's what i though it was.) maybe i'll put create a page somewhere with this information on.
this being the case, i now plan to move the release candidate and put a .htaccess redirection on builds/jakarta-bsf (previous comments about proposed timescales, other volunteers etc apply).
<snip>
it's a bit of a shame that there isn't an ASF release available for BSF (just a release candidate which appears to be data 12-Nov-2002) but i suppose that's an issue for BSF.
Of course. I know that Ant would love a BSF release that plays nicely with Rhino 1.5R4 - BSF's CVS HEAD does, but the RC doesn't.
i don't follow BSF closely but if there are any issues that the BSF team needs help (like lacking a release manager or not understanding how to create releases the new way etc) with it'd probably be a good idea for someone from BSF to post something to general or pmc at jakarta. i'm sure there are plenty of apache folks who'd be happy to help out.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
