#327: create plaintext template for pretty logs
--------------------+-------------------------------------------------------
Reporter: kparal | Owner: vhumpa
Type: task | Status: assigned
Priority: major | Milestone: 0.5.0
Component: core | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by jlaska):
Replying to [comment:6 kparal]:
Replying to [comment:5 vhumpa]:
> Summary will go first then, and I don't think we should remove it for
upgradepath - perhaps only packages from the one particular update should
be shown there.
No perhaps, definitely.
Yeah, that's a better idea. Keep the summary, but make it specific to the
update (and the packages included).
> How about adding the update ID as extra row, that would just
show only
when we have it?
+1
+1 also.
How will these additional pretty logs be saved on disk and referenced in
the bodhi comment? Will they be referenced by the UPDATE-ID, some random
integer, a long string of packages in the update? Perhaps this is getting
too far ahead.
> Here's an example how I think the log could look like now:
>
http://vhumpa.fedorapeople.org/prettylog_upgradepath_example2.txt
Looks good.
Concise and informative, that seems like a winner to me
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/327#comment:7>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project