![]() Maybe some of the process that currently goes through Bugzilla could move here. This is update-centric, but does also have a lot of issue-tracker-like characteristcs in the “karma” system, and it is inherently close to our release process. I think this makes sense for initial package review too, although that would need some workflow changes.īodhi and the CI results system and all of that. Let’s enable issue tracking on (with whatever gitforge we end up with that on). Package-specific issues should be next to the PRs. Then, software defects may or may not be tracked relating to those conversations. This is our first-line of support, and it’s where we can do triage. We do have some pieces already in place that should be part of the foundation (or at least other metaphorical bricks in the construction):Īsk Fedora is the place for users to report and discuss problems. But, it also shouldn’t be a completely blue-sky initiative - we should avoid trying to develop a new gigantic piece of software that we own. In fact, I think it should be a Fedora Objective. I think we should create a project to figure this out. And fortunately, we DO have a few years, so for once we could do this before it’s a crisis. ![]() We need define exactly what we do need, and figure out how to get that, in a sustainable way going forward. I therefore think that Jira / wouldn’t either - although it’s got a ton of features on top, it’s fundamentally the same kind of thing. It’s just actually not filling our needs. But I’m not really here to complain about Bugzilla. The SCM workflow is … not good.Īnd I’m sure there’s more. A component-centric approach makes it hard to track larger issues. It’s not great for the review workflow, or for some of the other things we’ve twisted it to. Plus plenty of minor things: Our workflow still is shoehorned around a bunch of RH-centric stuff (lots of fields, flags, and statuses that we don’t really use or want). We could make stronger statements about policies, but as long as these two things exist in separate places, that tension will keep coming back. I have seen cases where a packager complained that someone filed a PR that they never noticed, saying “this should be a bug so I’ll see it”, while others close bugs with “please send a PR”. We’re inconsistent with PRs vs issues, which is confusing and makes more duplication. For whatever reason, a lot of perfectly good reports end up closed EOL, which is never a good outcome. Maybe it’s in a dependency package that’s really only loosely maintained. Maybe that report should actually be upstream. Many of our users are advanced and recognize real defects and file good reports, but this leads to even more frustration, because our response is inconsistent. This is a whole topic of its own, but in short, it’s really better for most users to report problems at Ask Fedora, and then possibly after triage a bug should be filed and tracked somewhere. When a user has a problem, that may or may not be caused by a software defect. I’m not arguing that we need ALL things in one place, but it’s important that Bugzilla isn’t that now anyway.īugzilla a terrible experience for end users. Not to mention upstreams (and inconsistent approaches to tracking upstream issues). We’ve got stuff scattered around Bugzilla issue trackers in Pagure GitLab, and GitHub pull requests in all of those places and more. It doesn’t serve as a single place to track everything. Buzilla is it’s deeply integrated in a lot of our processes, and we’ve got a lot of automations and so on. And I have personal fondness for it that, which I do not for, say, the wiki. I’m not saying Bugzilla has been terrible - it’s served us well, in fact. So to the second part: Bugzilla isn’t what we really need anyway. (And non-CPE volunteers? There’s so much that’s more interesting!) We could ask CPE to keep it going, but… there’s so much more I’d like to ask CPE. I don’t think it’s too much pulling-back-the-corporate-curtain to guess that if one or both get tired of that and decide to go start a yak farm, Red Hat won’t prioritize hiring backfill dedicated in the same way. Right now, there are basically only two people keeping it all going, which is heroic. On the first part: yes, there’s a long, slow sunset, but I think realistically we’re going to see business-side attention drop significantly, and we’ll have correspondingly worse and worse service. The second is that Bugzilla isn’t a great tool for what we need anyway. There are two reasons for this, and only one of them is that Red Hat is moving away. Here’s what I’m thinking: we should plan to migrate to something else in the next three years. I posted this on the Fedora Development mailing list, in the thread RHEL moving to only long term, and am re-posting here for broader discussion.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |