I'm trying to follow this thread, I hope i'm not duplicating things.
Mark Thomas wrote:
Guenter Knauf wrote:
this makes me ask a couple of questions:
Remember we only *have* to make the source available. Anything we do
on the binary front is just being helpful and the release manager is
unlikely to have access to build binaries for all platforms.
1) why do some folders list older versions while others do not?
Probably because they are the latest stable version for that platform.
Yes, I tried to delete all older versions of binaries (tried = as far as
permissions allowed), but for sme platforms we don't have 1.2.23
binares, so I kept the latest available ones.
There is an open point, if we can find a way of distributing contributed
builds. I know we could get some, but there were valid concerns, if we
shold sign those with our own keys. So we would need some notion of
"contributed" and could put the binaries there.
2) why do we have a history of the last 3 versions with Win32 but no history
for any other platform?
Because the old version weren't cleaned out. They should have been.
I had no permissions to delete them, I'll write to the owners directly
to remove them.
3) where do the older versions go?
They are automatically copied to archive.apache.org which is linked
off the Tomcat homepage.
4) why do we prefix the directories with 'jk-' although 'jk' is already in the
path?
No particular reason I am aware of. We just do.
Seems to be history, and you decided to drop it for Netware :)
For NetWare I would like to have at least the 1.2.15 release up again since
that was last version where I supported Apache 1.3.x and Netscape - I point to
this version in the README but obviously nobody can download anymore (except
from my personal homedir). Sure its no problem for me just copy this over, but
first I wanted to discuss that here, and ask if I probably missed that there's
somewhere an archive from where older versions can be downloaded...
This is not correct. It is available along with all other versions in
the archive.
Then I would like to have at least the last three versions always up, + the
last version we have for any platforms where we cant build self, or where the
maintainer is currently busy and some versions behind.
-1.
dist (and the mirrors) should only have the current stable version and
the latest non-stable release if there has been once since the last
stable release.
This makes also sense in case it turns out later that we broke something with a
release, and users may have to switch back.
Again, that is what the archives are for.
So if the archives are important, we could replace the link text
"archives..." with something a little more prominent. Suggestions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
