This is the mail archive of the
mailing list for the binutils project.
Re: Add 2.29.1 as bugzilla "Target Milestone"?
- From: Nick Clifton <nickc at redhat dot com>
- To: Carlos O'Donell <carlos at redhat dot com>, Patsy Franklin <pfrankli at redhat dot com>
- Cc: Hans-Peter Nilsson <hp at bitrange dot com>, binutils at sourceware dot org
- Date: Thu, 14 Sep 2017 12:46:01 +0100
- Subject: Re: Add 2.29.1 as bugzilla "Target Milestone"?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=nickc at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 58D73356D4
- References: <alpine.BSF.firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
>> Does binutils have any process here for who is supposed to add
>> the milestone before the release goes out?
> Not as far as I know.
Actually I just found this note in Tristan's how-to-perform-a-binutils-release
Rename the current HEAD version entry in Bugzilla, and create a new
one. E.g. rename "2.16 (HEAD)" to 2.16, and create "2.17 (HEAD)". Go
to "Edit products" from the bottom toolbar, click on "binutils", then
on "Edit versions". If you don't have permissions to do this,
either ask Daniel Berlin to fix your account or ask Daniel Jacobowitz
to do it.
So presumably wither Tristan or Daniel or Daniel is the person to thank.