Stephen Smoogen wrote:
> You can only refactor it when you have a steady set of requirements. The
> code has been 'refactored' at least 4 times but what happens is that you
> will get into about 1/3rd of the way into it and find you have now to add
> a bunch of new requirements.
Sounds like pretty much what I had guessed. ;-)
So I think it would really help if Bodhi were to become more of an enabling
tool and less of an enforcing tool again. Package maintainers have this
wonderful organ between their ears that allows them to know better what is
best for their packages than some piece of software, no matter how much
complexity we force that software's maintainers to add to the latter. :-)
Pretty much every one of those bodhi requirements is because either
* a developer did not use that wonderful organ for some reason, and people said 'that should never happen again.'
* what the developer decided was not liked by other developers enough that it was decided 'that should never happen again.'
Look back on the 15-20 years of fedora devel emails and see how many times someone has said that something should never happen. Guess what? Enough other developers agreed at times, and decided it needed to be automated because the other big old complaint was about how long it took for people to review things and how prone to failure was also true.