Christopher Blizzard wrote:
Hi, Warren. I think that my only suggestion here is based on our
history with the Red Hat bugzilla, which is a mess of flags and states.
It turns out that flags and states, and the interactions thereof make
for a terrible workflow tool. And that's what you really want, a real
workflow tool. I don't know if we have the bandwith to find out and
build it out and hook it up to bugzilla properly, but that has to be
better than trying to teach people about the various interactions
between all the states.
Hi Chris,
We tried to create a process that was usable *now* because it would be
unacceptable to block the entire project on implementing the ideal tool.
I am fully aware that this only putting lipstick on a pig.
But while this pig isn't gorgeous, it is at least moderately less ugly
than before. The non-obviousness and complications of these flags are
moderately less broken than the previous blocker bug + wiki workflow.
While this interim process wont make everyone happy because it is
ambiguous and non-obvious in places, it sucks less, and we can use it
immediately.
Meanwhile we can think hard about what exactly we want in the ideal
workflow tool, and implement that fresh. It will help at that point
that requisite pieces like Fedora Account System, Build System, Source
Control, and Package Database will be evolving together. Armed with
knowledge of our these past pigs, we have a clearer understanding of
what exactly we need at that point.
Warren Togami
wtogami@xxxxxxxxxx
--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers
--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
