----- Original Message -----
Since we're looking to release this week, I figure it's time
to start
figuring out what is and is not going to make it into 0.5.0.
I'm sorry, we've been working so heavily on the code that we forget to be
transparent and communicate the progress continuously. I've just sent "[PATCH]
pretty logs" into mailing list, that should sum it up.
For the stuff that isn't going to make it into 0.5.0, do we want to
create a 0.5.1 milestone or just save it for 0.6.0
0.5.1 should be for bugfixes/hotfixes, 0.6.0 for new features.
Other than what has already been closed, my read of what is going to
be
done is:
- #314 Decrease the volume of 'PASSED' email sent to maintainers from
bodhi
* This 'just' needs to be merged and tested more
- #326 Create user-facing documentation for depcheck
* Going to start on this later today
Great. Please see the new output in depcheck logs (in origin/pretty branch).
- #315 Create per-item logs for multi-item tests
- #318 Provide access to test documentation
Not sure:
- #298 test.py - split postprocess_iteration reporting into standalone
methods
Part of 'pretty patch'.
- #316 depcheck: extract possible cause of failure
Same as above.
- #330 upgradepath: improve behavior when pushing update to multiple
releases
Not included, postponed.
Probably not:
- #319 Create HTML log output if possible
* based on what is currently in the comments
Part of 'pretty patch'.