quality/tickets
11
2
Fork 0
Code Issues 47 Projects Activity Actions

[F29] DNF 3.0 Test Day #562

New issue
Closed
opened 2018-07-05 17:53:16 +00:00 by sumantrom · 22 comments
sumantrom commented 2018-07-05 17:53:16 +00:00
Copy link

This instalment of Test Day will focus on testing DNF 3.0

This instalment of Test Day will focus on testing DNF 3.0
adamwill commented 2018-07-05 21:54:38 +00:00
Owner
Copy link

tagging @jmracek and @dmach ...

tagging @jmracek and @dmach ...
sumantrom commented 2018-07-10 02:27:41 +00:00
Author
Copy link

Metadata Update from @sumantrom:

  • Issue priority set to: critical (was: normal)
**Metadata Update from @sumantrom**: - Issue priority set to: critical (was: normal)
sumantrom commented 2018-07-10 02:29:11 +00:00
Author
Copy link

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?

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?
jmracek commented 2018-08-10 12:03:23 +00:00
Copy link

We already fixed a lot of issues, but a test day is a good idea.

We already fixed a lot of issues, but a test day is a good idea.
pkotvan commented 2018-08-20 07:11:59 +00:00
Copy link

Is this test day going to take place? When?

Thanks

Is this test day going to take place? When? Thanks
sumantrom commented 2018-08-20 09:01:03 +00:00
Author
Copy link

@jmracek when will be a good time to hold this? end of Aug? or start of sept?

@jmracek when will be a good time to hold this? end of Aug? or start of sept?
jmracek commented 2018-08-20 13:51:48 +00:00
Copy link

We will discuss it next week with other team members.

We will discuss it next week with other team members.
sumantrom commented 2018-08-28 14:51:53 +00:00
Author
Copy link

@jmracek any updates?

@jmracek any updates?
lruzicka commented 2018-08-29 13:00:29 +00:00
Owner
Copy link

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.

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.
sumantrom commented 2018-08-30 03:07:49 +00:00
Author
Copy link

@lruzicka We are always good with testing the latest build any day!
Do you have any idea on the dates?

@lruzicka We are always good with testing the latest build any day! Do you have any idea on the dates?
lruzicka commented 2018-08-30 08:25:12 +00:00
Owner
Copy link

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.

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.
sumantrom commented 2018-08-30 08:41:48 +00:00
Author
Copy link

@lruzicka Thanks for the update 💯

@lruzicka Thanks for the update :100:
sumantrom commented 2018-09-15 17:02:23 +00:00
Author
Copy link

any updates on the dates ??

any updates on the dates ??
sumantrom commented 2018-09-19 12:09:37 +00:00
Author
Copy link

@dmach does 3rd of october fine with you for running the test day for DNF 3.5.1?

@dmach does 3rd of october fine with you for running the test day for DNF 3.5.1?
dmach commented 2018-09-19 14:59:27 +00:00
Copy link

@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?

@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?
sumantrom commented 2018-09-19 17:17:46 +00:00
Author
Copy link

represent and just answer things if it catches fire :) or what will be a good date for you?

represent and just answer things if it catches fire :) or what will be a good date for you?
dmach commented 2018-09-20 07:33:00 +00:00
Copy link

Oct 3 is fine.
We're typically available during working hours (until 5 or 6pm CEST).

Oct 3 is fine. We're typically available during working hours (until 5 or 6pm CEST).
sumantrom commented 2018-09-20 11:02:38 +00:00
Author
Copy link

Awesome. I will lay in the test day bits.. do you have something specific thing in mind that you want us to test?

Awesome. I will lay in the test day bits.. do you have something specific thing in mind that you want us to test?
dmach commented 2018-09-20 12:13:34 +00:00
Copy link

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

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
sumantrom commented 2018-09-20 12:17:02 +00:00
Author
Copy link

I got the idea. Thanks @dmach :)

I got the idea. Thanks @dmach :)
sumantrom commented 2019-03-10 09:00:07 +00:00
Author
Copy link

This test day was fine. Closing this now.

This test day was fine. Closing this now.
sumantrom commented 2019-03-10 09:00:07 +00:00
Author
Copy link

Metadata Update from @sumantrom:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @sumantrom**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
agile

related to Scrum or other Agile methodology

  
anacondawebui

tickets relating to the anaconda 'web ui' interface refresh

  
arm

   
blockerfe

Issues relating to the blocker / freeze exception process

  
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Invalid
Closed with the reason of Invalid

  
Closed As
Wontfix
Closed with the reason of Wontfix

  
Closed As
Worksforme
Closed with the reason of Worksforme

  
coreos

issue related to coreos

  
criteria

release criteria-related issues

  
defect

   
easyfix

   
enhancement

   
iot

Issues related to IoT

  
meeting

a topic for the next QA meeting

  
meta

issues in the issue tracker itself (like, whooooaaa, man)

  
onboarding call

issues that are used to track new contributor onboarding

  
proventesters

   
retrospective

issues filed as a result of QA Retrospective feedback

  
silverblue

Issues related to silverblue

  
sponsor

requests to become a FAS group sponsor

  
test cases

   
test days

   
wiki
  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Fedora 29
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/tickets#562
No description provided.