From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81717 invoked by alias); 2 May 2016 17:23:53 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 81704 invoked by uid 89); 2 May 2016 17:23:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=joel, Joel, notifications, traffic X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 02 May 2016 17:23:50 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E7D37C062C91; Mon, 2 May 2016 17:23:48 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u42HNlRk008009; Mon, 2 May 2016 13:23:48 -0400 Subject: Re: gdb-7.11.1 re-spin update To: Joel Brobecker References: <20160425214951.GA4079@adacore.com> <571F5BF8.4090205@redhat.com> <20160502154642.GA4771@adacore.com> Cc: gdb-patches@sourceware.org From: Pedro Alves Message-ID: <7290d675-bb3c-fa59-2021-7ab59657cb3f@redhat.com> Date: Mon, 02 May 2016 17:23:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160502154642.GA4771@adacore.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-05/txt/msg00016.txt.bz2 On 05/02/2016 04:46 PM, Joel Brobecker wrote: > If there is a way for me to subscribe to all bugzilla PRs that get > assigned a specific release version, then the downside of using > bugzilla only is less. I might still have to open the bugzilla PR > to verify that the PR is assigned to someone, but given the number > of such PRs, I can live with that. But the question is - can we > subscribe to a category or all of bugzilla? Bugzilla supports sending notifications when the milestone changes, (it's in the preferences page), but I don't how to do that when you're not the assignee/reporterd/cced to the bug. What I do, is subscribe to the gdb-prs mailing list: https://sourceware.org/ml/gdb-prs/ so I get a message for _every_ change done on our bugzilla. I follow this list like I follow gdb-patches@. I have a mail filter that puts all gdb-prs traffic on its own mail/imap dir. (Note one can reply to these bugzilla email via email too, which is convenient at times.) For example, I just now changed the milestone of PR build/20029 to 7.11.1, and that generated this mail: https://sourceware.org/ml/gdb-prs/2016-q2/msg00171.html ( and just using the bugzilla interface for that was quite convenient. :-) ) Guess if one wanted, one could easily set up a mail filter based on "List-id: gdb-prs" and the "Target Milestone" string being present in the mail body. > Otherwise, if someone is already tracking bugzilla PRs and also > understands the release process, I am fine delegating this part > of the work. At least I track bugzilla PRs. I had assumed all maintainers did. I don't reply to all PRs, there's just not enough time unfortunately, but at least I read all and have been trying to make sure milestones are set. > One of the important aspects of that is making sure > that the information remains accurate, at least up to release; > so that the release announcement is as correct as can be. Given that the entries in the wiki page are just the PR title, I think that ends up being the same amount or even less work. If a bug has an incomplete or inaccurate title, we should just fix it on the bug directly, IMO. Thanks, Pedro Alves