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

Proposed Test Day - Sugar on a Stick #108

New issue
Closed
opened 2010-07-17 11:33:38 +00:00 by sdz · 3 comments
sdz commented 2010-07-17 11:33:38 +00:00
Copy link

Ownership - It'd probably be good if we had both somebody from the SoaS team (at the very least I can sign up, maybe also Mel and Peter) and Fedora QA hosting this.
Time frame - August 19 would be our favorite pick.
Feature - http://fedoraproject.org/wiki/Features/Sugar_0.90
Spin - http://fedoraproject.org/wiki/Sugar_on_a_Stick
Notes - http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process

Ownership - It'd probably be good if we had both somebody from the SoaS team (at the very least I can sign up, maybe also Mel and Peter) and Fedora QA hosting this. Time frame - August 19 would be our favorite pick. Feature - http://fedoraproject.org/wiki/Features/Sugar_0.90 Spin - http://fedoraproject.org/wiki/Sugar_on_a_Stick Notes - http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process
jlaska commented 2010-08-16 14:23:07 +00:00
Copy link

This snuck up on us quick given the delay in releasing F-14-Alpha. I have added the test day to the [https://fedoraproject.org/wiki/QA/Fedora_14_test_days calendar]. Has someone given thought to drafting a test day wiki? I mentioned this to sdz on IRC, but for folks on the cc list, take a look at the [https://fedoraproject.org/wiki/QA/SOP_Test_Day_management test day SOP] for suggested next steps. The next 3 big steps are ...

  1. Creating a test day wiki page
  2. Creating a live image for testing -- can we use http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/
  3. Promote the test day -- blogs, test-announce@lists.fedoraproject.org, sugar mailing lists etc...
This snuck up on us quick given the delay in releasing F-14-Alpha. I have added the test day to the [https://fedoraproject.org/wiki/QA/Fedora_14_test_days calendar]. Has someone given thought to drafting a test day wiki? I mentioned this to sdz on IRC, but for folks on the cc list, take a look at the [https://fedoraproject.org/wiki/QA/SOP_Test_Day_management test day SOP] for suggested next steps. The next 3 big steps are ... 1. Creating a test day wiki page 2. Creating a live image for testing -- can we use http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ 3. Promote the test day -- blogs, test-announce@lists.fedoraproject.org, sugar mailing lists etc...
rhe commented 2010-08-19 01:16:39 +00:00
Copy link

The test day time is due, but there's still no preparation for it. So probably it will be postponed. And I found [https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS the previous sugar test day] and it seems both soas.iso and the test cases are needed on the day.

The test day time is due, but there's still no preparation for it. So probably it will be postponed. And I found [https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS the previous sugar test day] and it seems both soas.iso and the test cases are needed on the day.
jlaska commented 2010-11-24 13:17:44 +00:00
Copy link

Closing this as 'wontfix'. If a SOAS event is desired for F-15, let's get a new ticket in. Thanks!

Closing this as 'wontfix'. If a SOAS event is desired for F-15, let's get a new ticket in. Thanks!
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 14
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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#108
No description provided.