commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: [general] RC releases
Date Thu, 10 Jun 2004 12:41:21 GMT

Hi,
I also think home directories are fine.  We wouldn't anticipate a huge
amount of downloads (Maven's eternal RC process being the exception) for
a Release Candidate.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Martin Cooper [mailto:martinc@apache.org]
>Sent: Thursday, June 10, 2004 2:11 AM
>To: Jakarta Commons Developers List
>Subject: RE: [general] RC releases
>
>
>
>> -----Original Message-----
>> From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
>> 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" <ggregory@seagullsw.com>
>> 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:scolebourne@btopenworld.com]
>> > 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: commons-dev-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
commons-dev-help@jakarta.apache.org
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message