Learn more about these different git repos.
Other Git URLs
I'd asking for the following: - retirement of the seperate "upstream" for fedora-release, i.e. simply merge https://pagure.io/fedora-release/pull-request/119. This has to be done by one of the owners of that repo. - the ability to build fedora-release. I probably can write to dist-git directly as proven packager, but I'm not sure if I can successfully build the package in koji. Either way, I'd prefer to be added as co-maintainer to make this official, and for any other changes that need to be made to be made. - review of https://src.fedoraproject.org/fork/zbyszek/rpms/fedora-release/branch/drop-upstream-split. I can't submit that as PR now, because PRs are disabled.
Stuff that I can do myself, once the above is done: - enable PRs on src.fp.o/rpms/fedora-release - resubmit the drop-upstream-split as PR, merge it once it's reviewed, and build - resubmit other requests against fedora-release as PRs, e.g. https://pagure.io/fedora-release/pull-request/139 and others.
Hi, any progress on this?
Yes, I'm going to take the lead, plan to get to it later this week, early next week and work with @mboddu on it.
Metadata Update from @pbrobinson: - Issue assigned to pbrobinson
Note we need to add some CI/CD for testing PRs to assist with regression etc so if anyone can assist with that please let me know.
Yes, I'm going to take the lead
Cool, thanks.
some CI/CD
What kind of testing?
upgrade paths would be a good start, we've had issues in the past where things like that broke
There is a dependency test in taskotron that runs on all packages (e.g. for latest fedora-release update: https://taskotron.fedoraproject.org/artifacts/all/4e634638-6585-11e8-875f-525400fc9f92/tests.yml/itemlogs/fedora-release-28-2.armhfp.log, example of failure for another package: https://taskotron.fedoraproject.org/resultsdb/results/22314584). Those results are only advisory afaik, since gating was disabled, but I'd rather build on this rather than implement something specific to fedora-release. If you are worried about this, it might be possible to either enable gating for fedora-release, if possible, or just document that until gating is restored, anyone making an update should verify that the test is green before submitting for stable.
I mean on a PR in pagure so it's tested before it's even made into a rpm that's pushed to koji
Metadata Update from @mohanboddu: - Issue tagged with: meeting
Pull requests for this are filed:
https://src.fedoraproject.org/rpms/fedora-release/pull-request/2 https://src.fedoraproject.org/rpms/fedora-repos/pull-request/2
Please review, AFAICT the output is the same as the current one.
This is done now. Thanks @pbrobinson.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @zbyszek: - Issue status updated to: Open (was: Closed)
Metadata Update from @zbyszek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Hm, I have no idea what those state changes are about. I don't recall touching this issue at all.
This was a pagure bug. Closing again since this is done.
Login to comment on this ticket.