On 3/29/07, David Ashley <dashley@us.ibm.com> wrote:

I have been struggling with how to deliver the release candidates for ooRexx 3.1.2. I have come to the conclusion that we should create a new release on Sourceforge just for the release candidates. When the final release is ready I can drop the release candidate release so that it does not appear any more on the page. This also gives us a common place to collect all the files as anyone can FTP anything into the SF upload area, but only an admin can make them visible to the release.
 
 
This sounds good.  I'm still a little clue-less here, though.  I'm not sure where the SF upload area is, or how to FTP to it.  Can you give me a hint.  <grin>
 

So as you get rpms, debs, zips, etc ready just upload them to SF and then post a note to the this mailing list and I will make them visible as a release candidate.
 
Do I need to put rc1 or something similar in the file names, or is just have them in the release candidate area sufficient?
 
Thanks.
 
--
Mark Miesfeld