We have a distr per minor version. You can see them here (we only currently use the last 3 major releases 21x, 20x and 12x) you can see them here https://dist.apache.org/repos/dist/release/cassandra/debian/dists/
The release managers have a local repo with our reprepro settings. We deploy the artifact and export locally then copy the whole thing over to the apache dist server. Here is the relevant section of the release script https://github.com/tjake/cassandra-release/blob/master/finish_release.sh#L161 As our wiki shows, users add the maintainer keys and the specific dist they want https://wiki.apache.org/cassandra/DebianPackaging Ideally, we can redirect the existing location to the new one but I'm not sure if that's possible. How can we replicate this setup with bintray? -Jake On Wed, Jan 7, 2015 at 12:41 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Great! So to start, can you give us a sense of what your needs for the > repo are? What are you putting in it? Are you splitting it up by distro at > all or just putting new versions of Cassandra in each time? > > A. > > On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani <j...@apache.org> wrote: > >> Hi Andrew, >> >> I'm happy to help. >> >> -Jake >> >> On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer <aba...@apache.org> wrote: >> >>> Hi Cassandra team - >>> >>> So as you're probably aware, the Cassandra Debian packages currently on >>> dist need to be moved off there. The Infra team has been working on a >>> solution for that - we've got an organization for ASF on bintray.com, >>> which >>> can store and serve Debian repositories. We'd like to work with you all >>> on >>> moving the existing packages over to bintray, and figuring out what needs >>> to be done to get a working process for you to post new Debian packages >>> going forward. Could someone from Cassandra (or some set of someones) be >>> available to work with us on this? Thanks! >>> >>> A. >>> >> >> >
