On 7/12/05, Mark Phillips <mark@...> wrote:
> There is an svn tag for it named Release-0_9b1. I haven't committed
> anything to trunk.
> I tested the tarball today and no unexpected failures were encountered
> during the AllTests routines.
> I am at the point where the Release Procedures say to upload the tgz to
> sourceforge but, being new at this, I have a couple of questions.
> 1. Is ncftp still the required utility to upload to sf? That is, will
> this still work:
> > ncftpput -V upload.sourceforge.net /incoming Webware-VER.tar.gz
I don't know. Keep in mind it's been a long time since we cut a
release and occasionally SourceForge changes things. You'll want to
consult their current docs.
> 2. I notice the 0.8 betas are not on sourceforge, so shall I upload the
> 0.9b1 somewhere else?
We were putting the betas on the web site just to avoid polluting the
SF Webware file release list with them since they are rather
temporary. I'm not religious about this. You can do that or make the
beta a real release.
> 3. Under "Release on SourceForge", there is an admonition to wait until
> after the final test before sending user notification. I have a notion
> as to what is meant, but would someone clarify that, please.
Once you release on SF you'll want to tell the whole world. That note
is a reminder to download the release, unpack it and test the product
> BTW, on the 'to do' list is updating the Release Procedures doc and
> ReleaseHelper.py to use the svn. It seems to me that svn will simplify
> these two quite a bit. I suspect the commentary in Release Procedures
> about the mirror site at ebad.pair.com be removed or updated. Any
Yeah ebad.pair.com is no more. If you still want to put an extra copy
of the release somewhere for when SF is broken, the web site would be
the place to do it.