From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.11.1 re-spin update
Date: Mon, 02 May 2016 15:46:00 -0000 [thread overview]
Message-ID: <20160502154642.GA4771@adacore.com> (raw)
In-Reply-To: <571F5BF8.4090205@redhat.com>
Hi Pedro,
Sorry I wasn't able to anwer this any sooner...
> I was the one who first added these urls, sorry if it causes
> you trouble, and sorry that I didn't reach out to you before
> actually doing it. I thought in good faith that that would
> be an obvious improvement.
>
> Let me explain what went through my mind:
It makes sense.
On the other hand, the first advantage of having it in the wiki was
that I was able to subscribe to the release wiki page, and therefore
get an email each time a chnage in made. The side effect of that I can
then double-check the entries added, and in particular checking that
someone is assigned that entry.
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?
Otherwise, if someone is already tracking bugzilla PRs and also
understands the release process, I am fine delegating this part
of the work. 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.
WDYT?
--
Joel
next prev parent reply other threads:[~2016-05-02 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 21:50 Joel Brobecker
2016-04-26 12:16 ` Pedro Alves
2016-05-02 15:46 ` Joel Brobecker [this message]
2016-05-02 17:23 ` Pedro Alves
2016-05-02 19:38 ` Joel Brobecker
2016-05-02 19:41 ` Pedro Alves
2016-05-02 21:16 ` Joel Brobecker
2016-05-02 21:30 ` Pedro Alves
2016-05-05 13:49 ` Joel Brobecker
2016-04-27 19:36 ` Jan Kratochvil
2016-05-03 14:19 ` Simon Marchi
2016-05-03 14:31 ` Joseph Myers
2016-05-03 15:01 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160502154642.GA4771@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox