----- "Kamil Paral" <kparal(a)redhat.com> wrote:
Thanks, James, patches look completely fine. My quick smoke test
succeeded.
Let's deploy! :)
One more thing. Since autoqa 0.4.3 is now out, we should fix the
outdated documentation:
https://fedorahosted.org/autoqa/query?status=new&status=assigned&...
So if anyone is interested (all of you, right?:)) please grab a ticket
and fix the wiki, thanks.
For the next release I think I'll discard "Outdated documentation"
milestone and propose a different workflow:
1. If possible, fix documentation right after the patch is pushed
to master :o)
2. If you don't want to do 1), then instead of closing the corresponding
ticket, just change the component to "documentation" and leave it
open. And make sure the milestone is set to the next autoqa release
(currently 0.4.4). That way we will see what documentation we need to
fix before releasing a new version.
3. If there is no ticket for your patch (and it requires documentation
changes), just create a new ticket, provide a description with your
patch checksum, and assign to "documentation" component and nearest
release milestone.
This way we should be able to track outdated documentation nicely and
it doesn't require any more work than with current approach. The bonus
is that those tickets will block our next release, so that we don't
forget about them.