> > But my understanding of it all is that we can't create ARM specific > > releases until we have a release manager that owns an ARM machine > > where they can keep their gpg private key. > > … the Hadoop 3.3.0 ARM > artifacts was published with Brahma Reddy Battula help, > who is Hadoop PMC member and is also working for Huawei, he has served as > the Hadoop 3.3.0 release manager, and has > talked with Hadoop community that he will also take charge of the ARM > artifacts of future releases. there is a discussion: > http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/202003.mbox/%3CCAPwQCrkgwcDDFtC4+i_pv0pO8Zx6UG_43K=szxtv6k7-h4v...@mail.gmail.com%3E
That thread is gold, it answers all the questions I raised. Thanks Sheng Liu! I suspect we will continue with noarch releases. This kinda makes sense now that we have dropped support for Windows and are also talking about removing our Sigar dependency and its libraries. Having ARM in the CI means we can confidently support ARM on those noarch releases, and it makes the release managers job simpler and the role more fluid. Though, we hit the problem again when we want to publish any ARM docker images to https://hub.docker.com/u/apache/ (For example, currently CI has to build ARM docker images on-the-fly, as we have only amd64 testing images in dockerhub.) > > - can we SSH gpg-agent sign releases on hardware the release manager > > does not own? > > Or add an announcement about ARM platform support in Cassandra doc ? Yeah, we do need some updates to our docs regarding the platform support our noarch releases are tested on. And our debian and redhat packaging needs improvements, particularly now post-bintray, so worth keeping it in mind there too how we can best package and document it. > > Absolutely! I hope this becomes one significant part of the 4.0 > > announcement. > > Thanks for doing that. I am not sure if we can find a way to solve the > above problems finally. > But if we cannot publish official ARM64 artifacts due to the Apache policy > limit, maybe we can publish an unofficial ARM64 artifacts ? Those nightly artefacts I pointed to are our "unofficial" releases. But we cannot advertise them outside of development use. Though there is nothing stopping third parties taking those artefacts and putting their label of quality on them, announcing and distributing them. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
