The directory layout is setup in /www/www.apache.org/dist/jakarta/tomcat-connectors and /www/archive.apache.org/dist/jakarta/tomcat-connectors .
The old coyote beta and milestone releases have been removed. The webapp releases have been moved to the archive.
The latest jk2 release is setup on the mirror and previous releases are in the archive.
The mod_jk 1.2.5 source distribution has been released on the mirror, previous versions have been copied to the archive.
The jakarta site binindex.cgi and sourceindex.cgi have been updated. The jk docs in the Tomcat 4.1 directory have been updated with the download links fixed.
For now I am leaving the current jk/jk2 releases in place on the jakarta site. After a few days I will remove them and put the .htaccess file in place.
The mod_jk 1.2.5 release is now accepting binary releases. Please consider the following when packaging your binary release distributions:
Build binaries and upload distributions to www.apache.org --------------------------------------------------------------
Build mod_jk for a specific web server and OS. Package it as appropriate for the OS and sign the archive using PGP. Please include the ASF License, the generated docs, and the tools. Please name the distribuiton as follows:
jakarta-tomcat-connectors-jk-{version}-{os-version-cpu}-{web server-version}.(tar.gz|zip)
scp the binary distribution and pgp signature file to the appropriate binaries/{os} directory.
Make sure the group write bit is on for all files you upload.
I will send out the announcement in a few days once some binaries have accumulated and the mirrors have had a chance to rsync them.
Thanks,
Glenn
Glenn Nielsen wrote:
As part of the mod_jk 1.2.5 release I promised to move the JTC download to www.apache.org/dist so that the downloads can be mirrored. Here are the changes I propose to make as I set this up.
First, here is the directory layout for mirrored downloads at /www/www.apache.org/dist/jakarta/tomcat-connectors :
KEYS jk jk/README.html jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz -> jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz jk/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz.asc -> jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc jk/binaries jk/binaries/aix jk/binaries/freebsd jk/binaries/iseries jk/binaries/linux jk/binaries/macosx jk/binaries/netware jk/binaries/solaris jk/binaries/win32 jk/source jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz jk/source/jakarta-tomcat-connectors-jk-1.2.5-src.tar.gz.asc jk2 jk2/README.html jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz -> jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz jk2/jakarta-tomcat-connectors-jk-2.0-src-current.tar.gz.asc -> jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc jk2/binaries jk2/binaries/aix jk2/binaries/freebsd jk2/binaries/iseries jk2/binaries/linux jk2/binaries/macosx jk2/binaries/netware jk2/binaries/solaris jk2/binaries/win32 jk2/source jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz jk2/source/jakarta-tomcat-connectors-jk-2.0.2-src.tar.gz.asc
Each binary directory would contain a tar.gz, rpm, or zip for the binary release
rather than .dll or .so files. The archive would be named:
jakarta-tomcat-connector-jk-{version}-{OS-Version-CPU}-{Webserver}.tar.gz (.zip for windows, .rpm for linux rpm's)
linux rpms would go in the binaries/linux directory.
Here is an example for mod_jk 1.2.5 for FreeBsd on i386 for apache 2:
jakarta-tomcat-connector-jk-1.2.5-freebsd4.8-i386-apache-2.0.47.tar.gz
This will allow us to put multiple binaries in the same directory for different
jk release versions, OS versions, and web server versions and make managing
the mirrored download and archive.apache.org directories easier.
httpd includes the source with their binary distributions, I recommend that we do
the same. The binary release should contain the contents of the source release
plus the binary files.
Here is what I propose we do:
1. Coyote - /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/
This contains 9 coyote connector beta release and one release candidate.
Do we need to keep these? If not, since coyote comes with the Tomcat releases,
why not completely remove coyote from the tomcat-connectors download?
+1 to remove coyote from the download completely since it is part of the Tomcat release.
If we keep them, I will make the following changes.
Take each release directory and create both a tar.gz and .zip for the release, sign each. i.e. The jar files in v1.0-b1 are put into apache-tomcat-coyote-1.0-b1.tar.gz.
Place the tar.gz and zip files in the
/www/archive.apache.org/dist/jakarta/tomcat-connectors/coyote/binaries/ directory.
2. JK1.2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/
Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html.
Remove the nightly directory, no nightlies have been done.
Reorganize the releases as described above. Move old releases to archive.apache.org/dist,
move the current release to www.apache.org/dist .
3. JK2 /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/
Remove the docs directory, point users to jakarta.apache.org/tomcat in the README.html.
Remove the nightly directory, last nightly was done Oct. 5 2002.
Reorganize the releases as described above. Move old releases to archive.apache.org/dist,
move the current release to www.apache.org/dist .
4. Add a section to http://jakarta.apache.org/site/sourceindex.cgi for downloading the
tomcat connectors from the mirror.
5. Use a .htaccess file to add a permanent redirect for jakarta.apache.org/builds/jakarta-tomcat-connectors to
www.apache.org/dist/jakarta/tomcat-connectors/ .
Comments and suggestions welcome.
Regards,
Glenn
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
