From: Mark P. <ma...@mo...> - 2005-07-13 00:30:22
|
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 2. I notice the 0.8 betas are not on sourceforge, so shall I upload the 0.9b1 somewhere else? 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. 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 thoughts? Happy days, - Mark |
From: Chuck E. <chu...@gm...> - 2005-07-13 15:41:49
|
On 7/12/05, Mark Phillips <ma...@mo...> wrote: > There is an svn tag for it named Release-0_9b1. I haven't committed > anything to trunk. >=20 > I tested the tarball today and no unexpected failures were encountered > during the AllTests routines. >=20 > 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. >=20 > 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 first. > 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 > thoughts? 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. -Chuck |
From: Ian B. <ia...@co...> - 2005-07-13 17:36:01
|
Chuck Esterbrook wrote: > On 7/12/05, Mark Phillips <ma...@mo...> 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. SF is even slower to update than we are, so it should work fine. You can use anything to ftp up the file, you don't have to use ncftpput. >>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 >>thoughts? > > > 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. Files can go in /var/www/downloads, which show up in http://webwareforpython.org/downloads -- Mark, do you have an account on w4py.org? If not you can email me a username and I'll set you up. -- Ian Bicking / ia...@co... / http://blog.ianbicking.org |