Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: Steve Cohen <scohen@javactivity.org>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: [net] commons-net.1.2.0-rc1
Date: Wed, 21 Apr 2004 23:55:39 -0500
User-Agent: KMail/1.5
References: <200404192042.06252.scohen@javactivity.org>
 <85y8oqc9y8.fsf@firefoot.brekke.org>
 <200404202215.54181.scohen@javactivity.org>
In-Reply-To: <200404202215.54181.scohen@javactivity.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404212355.39954.scohen@javactivity.org>

okay, I've pushed the site and built the candidate release.
I have followed the instructions here:

http://jakarta.apache.org/commons/releases/prepare.html

about uploading the candidate release:

Now tag (for example FOO_1_2_RC1) and build distributions from that tag (as 
per full release). 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.) 

I have done this.  It's unclear to me that anyone else can access the release 
there, so let me know.  This may once again be a case of stale instructions.

Once I have a clear sense of "uploading the candidate release" I will propose 
a vote on releasing 1.2.0.


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