This instalment of Test Day will focus on testing DNF 3.0
tagging @jmracek and @dmach ...
Metadata Update from @sumantrom: - Issue priority set to: critical (was: normal)
Hey, There has been multiple reports about broken dnf and we will like to have a test day as soon as possible. @jmracek @dmach can you people please let me know the dates when it will be good to host the test day?
We already fixed a lot of issues, but a test day is a good idea.
Is this test day going to take place? When?
Thanks
@jmracek when will be a good time to hold this? end of Aug? or start of sept?
We will discuss it next week with other team members.
@jmracek any updates?
I would like to remark that according to what I have heard, the test day should work with dnf version greater than 3.2 (i.e. 3.3 or 3.4). In the newer versions, many flaws have been corrected.
@lruzicka We are always good with testing the latest build any day! Do you have any idea on the dates?
Yesterday, I was told by @dmach that there will be a new version of DNF available soon (dnf 3.4). I suggest we run the DNF TestDay after it has been published.
@lruzicka Thanks for the update :100:
any updates on the dates ??
@dmach does 3rd of october fine with you for running the test day for DNF 3.5.1?
@sumantrom I cannot confirm that, because I wanted to take PTO around that date, but I can possibly make sure DNF team is represented by someone else.
What is actually expected from the DNF team members? Just to be available or anything else?
represent and just answer things if it catches fire :) or what will be a good date for you?
Oct 3 is fine. We're typically available during working hours (until 5 or 6pm CEST).
Awesome. I will lay in the test day bits.. do you have something specific thing in mind that you want us to test?
We're interested mainly in: feedback on modularity serious regressions to YUM v3 user experience issues (inconsistencies, awkward behavior) any performance issues
but probably nothing particular to test
I got the idea. Thanks @dmach :)
This test day was fine. Closing this now.
Metadata Update from @sumantrom: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.