You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2004/10/25 04:10:46 UTC

3.0.1 /dist/ area screwups

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Theo Van Dinter writes:
> On Fri, Oct 22, 2004 at 08:09:10PM -0700, Justin Mason wrote:
> > SpamAssassin 3.0.1 is released!  3.0.1 contains some important
> > bugfixes, and is recommended.
> 
> Another couple of notes about the release.  Apparently the
> dist/spamassassin/source files for 3.0.0 were removed -- so the only version
> available for download now is 3.0.1.  Don't we want to keep the older
> version(s) available for at least some period of time?

This is going by what the ASF guidelines for usage of the mirrored
www.apache.org/dist/ say *must* be done.   see
http://www.apache.org/dev/mirrors.html ,
http://httpd.apache.org/dev/release.html ,
http://cvs.apache.org/~bodewig/mirror.html ,
http://jakarta.apache.org/site/convert-to-mirror.html .
However, I think I agree -- leaving the old versions there for
a short while makes more sense.   Take a read over those and see
what you think.

The fundamental problem this time around was that I miscomputed that
?update parameter.  we should create a simple build script that generates
the correct value for us to cut and paste and cut down on faulty
brain-work. ;)

There *is* another problem, though -- since the downloads.html/.cgi page
is on the single un-mirrored site, and the downloads are on the mirrors
which may be up to 24 hours out of sync, we would still have to use the
?update=200409211830 parameter on the downloads.cgi URL to ensure that
only up-to-date mirrors are used; otherwise the download link will either

    - (a) if it points to Mail-SpamAssassin-3.0.1.tar.gz, return a 404

    - (b) if it points to Mail-SpamAssassin-current.tar.gz, return the old
      file which will not match the checksums, and that's not good.

> Also, the dist/spamassassin/source files were removed, but not the symlinks to
> them in dist/spamassassin -- so there were 12 bad symlinks lying around.
> I've already received a complaint note about it, so I removed the bad symlinks.

oops.  my fault!  we need to update build/README to reflect that.

> I really don't understand why we put the source files in the source directory,
> and then have symlinks for them all in the parent directory.  Just put the
> source files in the parent directory!

Again, ASF guidelines.  It might be worth asking infrastructure@ if the
guidelines can be ignored in this case... although I'm not sure there's
a big win.

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBfGCmMJF5cimLx9ARAiUjAJ43Mzilp/NpIkAlD/nPSbhm3cGqPACdHzSR
tc6h+C3KAq2K9PCWvbW6M9M=
=9cda
-----END PGP SIGNATURE-----


Re: 3.0.1 /dist/ area screwups

Posted by Theo Van Dinter <fe...@kluge.net>.
On Sun, Oct 24, 2004 at 07:10:46PM -0700, Justin Mason wrote:
> http://www.apache.org/dev/mirrors.html ,

Current public releases: http://www.apache.org/dist/

Releases that are intended for current public download should be placed on
www.apache.org. This is the main public release site and the site that is
mirrored world-wide. [minotaur.apache.org:/www/www.apache.org/dist/]


So if we only want the latest release there, that's fine, but we'll need to
put up a link to the http://archive.apache.org/dist/spamassassin/ site for
older releases.

> However, I think I agree -- leaving the old versions there for
> a short while makes more sense.   Take a read over those and see
> what you think.

I think leaving the most recent 2 stable releases is fine.

> the correct value for us to cut and paste and cut down on faulty
> brain-work. ;)

;)

> There *is* another problem, though -- since the downloads.html/.cgi page
> is on the single un-mirrored site, and the downloads are on the mirrors
> which may be up to 24 hours out of sync, we would still have to use the
> ?update=200409211830 parameter on the downloads.cgi URL to ensure that
> only up-to-date mirrors are used; otherwise the download link will either
>     - (a) if it points to Mail-SpamAssassin-3.0.1.tar.gz, return a 404
>     - (b) if it points to Mail-SpamAssassin-current.tar.gz, return the old
>       file which will not match the checksums, and that's not good.

I'd rather use the update parameter then risk people getting really confused
with "-current".  We already need to push out a new download page with the
latest version on it, so it's not a big deal to update the parameter.

-- 
Randomly Generated Tagline:
We're a hospital of people helping each other, performing random acts
 of beauty for each other, even when no one is watching but God.
              -- Larry Wall, 8th State of the Onion