Hi, Svn dist area is the canonical distribution channel for Apache releases, which is only the source tarball. The rest of the files there are "convenience binaries" and are not part of the release themselves.
Same happens with the files uploaded to Nexus, which get synced to Central, the Dockerfile at hub.docker.com or the releases pages at GitHub, all convenience, we could not upload them.. but it so convenient for end-users :o) (GH releases is not a great example as they bundle a source tarball that is not the one voted upon) I have a small shell script that use when releasing to move the all the files you mention from git to svn, I can upload to git so next release is a bit less cumbersome? best regards, juan pablo El lun, 17 ago 2026, 23:06, Alex O'Ree <[email protected]> escribió: > While doing the past set of releases, i think there's some improvements > that can be made, at the very least, a discussion about why things are the > way they are. > > If you're not familiar with the process, it's basically, build, deploy to > nexus, then manually gather a number of artifacts and upload to a svn repo. > That svn repo, eventually gets merged to dist.apache.org which contains > the > final artifacts of a given project. > > What I've noticed is that we are effectively duplicating everything in this > svn repo that is also published to the nexus repo. This doesn't make a > whole lot of sense to me. Typically, there's just a readme, all of the > products or executables and hashes/signatures. In this case, I can see the > war file, the portable build, and that's about it. Everything else can be > sourced on maven central. In addition, everything from dist.apache.org > also > ends up in the archive at archive.apache.org. > > Does anyone a) know why we are putting every artifact into the svn repo or > b) have any reservations about changing the process to simplify things (and > reduce storage needs for the apache sites)? >
