Re: Git Forge Requirements: Please see the Community Blog

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

 



On Thu, Jan 30, 2020 at 10:40:05AM +0100, Vít Ondruch wrote:
>    Dne 29. 01. 20 v 23:22 Pierre-Yves Chibon napsal(a):
> 
>  On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote:
> 
>  Julen Landa Alustiza [1]<jlanda@xxxxxxxxxxxxxxxxx> writes:
> 
> 
>  (snip)
> 
>  20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen:
> 
>  To me that's the all point of this
>  process, let's put down what we *really* *really* need and  then look at
>  the different options.
> 
> 
>  Do we *really* *really* need to compete with other full featured git
>  forges on features? The ODF says that this is one of the problem. Well,
>  imo we don't *really* *really* need to compete with them.
> 
>  Actually we already have the features that we *really* *really* need.
>  Otherwise we could not release fedora using pagure as we are using,
>  could we? :)
> 
>  We don't have per-branch default assignees, which is actually a pretty
>  big problem in Fedora (especially with EPEL packages).
> 
>  I'd counter-argue that we don't need one considering bugzilla doesn't support a
>  per-version assignee. So we need an assignee for Fedora and one for Fedora
>  EPEL, going the level lower (F31, F30, F29, epel8, epel7...) does not bring
>  anything since we wouldn't be able to sync this to bugzilla.
> 
>    I mostly agree. However, retired packages, such as [1], should then be
>    owned just by orphan after the years since their retirement. This used to
>    work during PkgDB days, it does not work anymore.

I'm traveling right now so I can't track it down, but the issue for this is that
basically the script that syncs status from src.fp.o to bugzilla has been broken
for a while.
We fixed this just last december and started running the new script early this
year, so this should be fixed now. If the issue persist, it's likely something
that is going on with someone's FAS email not mapping to a bugzilla account.
Having access to the logs of the cron job (runs twice a day), I can easily check
this when I get back to a more stable working station.

Could you open an infra ticket to track this, so we don't forget about it?

Thanks,
Pierre

Attachment: signature.asc
Description: PGP signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux