I agree, we can use the existing repository and just add an appropriate suffix.
Best, Stamatis On Tue, Mar 10, 2026 at 7:03 AM Ayush Saxena <[email protected]> wrote: > > I think we should use a single repository for now and rely on a proper suffix > such as 4.3.0-SNAPSHOT. That version can be updated as new snapshots are > produced. > > Maintaining a separate repository would add some operational overhead, and > given that we don’t have a large number of volunteers maintaining things, > keeping everything in one place seems more practical. From a user perspective > as well, this approach is simpler—users would only need to switch the > snapshot version in their export HIVE_VERSION command to start using the > newer build. > > If there are no strong objections to this approach, I suggest we proceed with > it for now. If later we feel there is a clear need for a separate repository, > we can always revisit and move in that direction. > > -Ayush > > On Wed, 18 Feb 2026 at 15:27, Shohei Okumiya <[email protected]> wrote: >> >> Hi, >> >> I'm glad to see many positive reactions and information new to me. Thank you! >> >> We should probably discuss which repository to use for this new >> purpose. I believe we can reuse apache/hive as long as we use a proper >> tag name. It is also an option to use apache/hive-nightly or something >> like Apache Solr. I am currently biased toward having a separate >> repository, i.e., apache/hive-nightly, for two reasons. From Docker >> users' perspective, pushing all in a single repo will likely obscure >> stable tags such as 4.2.0. From the committers' perspective, >> separating a repo would make management tasks, such as expiring old >> images, easier and safer. It's not a strong opinion. >> >> Once it's decided, I can try to create a pull request (and an INFRA >> ticket if we need a new repo), and we can discuss other details, such >> as naming conventions or frequency, there. >> >> Best, >> Okumin >> >> On Wed, Feb 18, 2026 at 4:39 PM Ayush Saxena <[email protected]> wrote: >> > >> > +1. >> > >> > I believe there is a policy covering this (likely in the incubator >> > documentation), though I can’t locate it at the moment. As far as I >> > remember, publishing such images is allowed provided they are suffixed >> > with -SNAPSHOT and do not use tags like latest. >> > >> > I’ll look for the exact reference and share it here once I find it. >> > >> > -Ayush >> > >> > On Tue, 17 Feb 2026 at 17:52, Attila Turoczy <[email protected]> wrote: >> >> >> >> +1 >> >> do not want to repeat why it is important and valuable. Very cool idea! >> >> What is the next step to make it happen? :) >> >> >> >> -Attila >> >> >> >> On Sun, Feb 15, 2026 at 3:22 PM Denys Kuzmenko <[email protected]> >> >> wrote: >> >>> >> >>> +1 for the initiative! >> >>> >> >>> I think having nightly/snapshot Docker images would be really useful for >> >>> Hive developers. It allows quick testing of the latest master, easier >> >>> development of container-related features, and keeps the Docker build >> >>> pipeline actively tested.
