> -----Original Message-----
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 09, 2004 3:36 PM
> To: Jakarta Commons Developers List
> Subject: Re: [general] RC releases
>
>
> I knew I'd seen something about it. I just wasn't sure if a publicly
> announced RC (via the announce list) might be different.

It's somewhat subjective. If you anticipate thousands of downloads shortly
after the announcement, then it would be good to arrange for the mirrors to
pick it up ahead of time. Otherwise, providing it from your home directory
is probably fine.

--
Martin Cooper


> Stephen
>
> ----- Original Message -----
> From: "Gary Gregory" <[EMAIL PROTECTED]>
> From http://jakarta.apache.org/commons/releases/prepare.html:
>
> "For commons components, it's usually unnecessary to post the release
> candidate on the main release site. (It's usually good enough to upload
> it into the public folder ~/public_html in your home directory on
> cvs.apache.org.)"
>
> Thank you,
> Gary
>
> > -----Original Message-----
> > From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, June 09, 2004 15:29
> > To: Jakarta Commons Developers List
> > Subject: [general] RC releases
> >
> > Is my public_html folder a good enough place for a publicly announced
> > RC1/Beta? Or do I need to put it on the mirrors?
> >
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to