Re: Triage of fedmsg issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 8 Nov 2016 16:04:38 +0100
Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:

> On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> > This is likely also
> > https://pagure.io/fedora-infrastructure/issue/4022 Perhaps I should
> > close that one UPSTREAM? (I have no idea if it still needs fixing)  
> 
> Nah that's bug in our git hook that is in ansible.
> 
> There are two ways to go about it:
> - Announce git branch that are removed
> - Don't
> (on pagure I took the second approach).
> 
> If we want to take the first approach, we'll need to adjust
> fedmsg_meta_fedora_infra for a new topic.
> 
> I can take this one, any preferred solution?

well, I don't much care honestly. We could just not announce things
until someone asks us to add that message? But on the other hand, if we
had the message someone might think of some use of it. ;) 

kevin

Attachment: pgpuVbPG7VU9j.pgp
Description: OpenPGP digital signature

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux