Bug 569384 – Please provide mapping for herd gcc-porting@g.o (GLEP67)

• Product: Gentoo Infrastructure
• Status: RESOLVED WORKSFORME

[Description Michał Górny 2015-12-23 15:04:19 UTC]

The herds have been deprecated by the Council and are being replaced
by projects. For this reason, please decide on the fate of the herd
stated in the summary and update [1] or state the request here.

The common choices are:

1. Map the herd to an existing project (in this case all packages
in the herd will be maintained by the project) -- let us know which
project to use.

2. Create a new project for the herd -- create the wiki page, let us
know the new mail alias name to be created, create the wiki page
and let us know about it.

3. Decide to disband the herd -- just let us know (but keep it for now
in herds.xml!), we'll replace it with individual maintainers when herds
are removed.

[1]:https://wiki.gentoo.org/wiki/Project:Metastructure/Herd_to_project_mapping

[Comment 1 Ryan Hill (RETIRED) 2015-12-28 02:46:06 UTC]

gcc-porting is not a herd AFAIK.  No packages are maintained by gcc-porting.

[Comment 2 Michał Górny 2016-01-05 13:33:22 UTC]

Well, it is listed as a herd. But since no packages are maintained, we're just going to kill it with fire.

[Comment 3 Anthony Basile 2016-01-05 13:41:30 UTC]

(In reply to Michał Górny from comment #2)
> Well, it is listed as a herd. But since no packages are maintained, we're
> just going to kill it with fire.

We use it as the mail alias to track stable packages that build under our current stable gcc but break under an unstable gcc.  This seems like a good thing.  How will the workflow go in the future?  Still open bugs like #536984 but assign them to toolchain@g.o?

[Comment 4 Michał Górny 2016-01-05 13:44:23 UTC]

I'll keep the alias working, it will just not be listed in herds.xml/projects.xml.