Sorry, I actually meant build*s*@hive.apache.org. Sorry for the typo. On Mon, 9 Nov 2026 at 13:43, László Bodor <[email protected]> wrote:
> That makes sense to me, Stamatis. I'm proceeding with > [email protected]. > > > > On Wed, 7 Oct 2026 at 09:53, Stamatis Zampetakis <[email protected]> > wrote: > >> How about a new mailing list dedicated to build/job notifications, >> namely [email protected]? >> >> Various other ASF projects (Arrow, Solr, Lucene, Airflow, Impala, >> Flink, etc.) follow this approach and we can create it instantly via >> the selfserve service [1]. >> >> In a recent change [2], I opted to send notifications for failed >> GitHub workflows to [email protected] but I feel that even for >> this a new list would be more appropriate. >> >> Having said that, I don't mind having those in commits@ to begin with. >> >> Best, >> Stamatis >> >> [1] https://selfserve.apache.org/mailinglist-new.html >> [2] >> https://github.com/apache/hive/commit/81b0b13301f5402a439ac8beebbe8b68273bfcec >> >> On Tue, Oct 6, 2026 at 10:31 PM Sai Hemanth Gantasala >> <[email protected]> wrote: >> > >> > Hi Laszlo, >> > >> > Using [email protected] for the Hive SNAPSHOT deployment failure >> notifications sounds reasonable. >> > Starting with the commits list makes sense to keep automated alerts off >> dev@, and we can adjust later if needed. >> > >> > Thanks, >> > Sai >> > >> > >> > On Tue, Oct 6, 2026 at 5:54 AM László Bodor <[email protected]> >> wrote: >> >> >> >> Hi all, >> >> >> >> I’m working on HIVE-30137, which adds a Jenkins job to deploy Hive >> SNAPSHOT artifacts from master to the Apache snapshot repository on every >> commit. >> >> >> >> As part of the setup, the job can send email notifications when a >> deployment fails. I’d like to confirm which mailing list we should use for >> those failure notifications: >> >> >> >> [email protected] >> >> >> >> [email protected] >> >> >> >> My preference would be [email protected] for now, to avoid >> adding automated failure notifications to the dev@ list. We can always >> change the destination later if we find that dev@ would be more >> appropriate. >> >> >> >> Does [email protected] sound reasonable for this? >> >> >> >> Thanks, >> >> Laszlo Bodor >> >> >> >> >> >
