Re: [Fedora QA] #147: Ratify Fedora 15 Schedule

[Fedora QA]

#147: Ratify Fedora 15 Schedule
---+
  Reporter:  poelstra  |   Owner:  jlaska   
  Type:  task  |  Status:  new  
  Priority:  critical  |   Milestone:  Fedora 15
 Component:  Trac  | Version:   
Resolution:|Keywords:  meeting  
---+
Comment (by poelstra):

 == Test Composes ==

 BTW, had a conversation with James Laska about the timing with the Test
 Composes and it sounded like there were times during Fedora 14 when there
 wasn't enough breathing room between then the testing of the Test Compose
 and issues found there and the creation of the RC.

 For Fedora 15 I'm proposing a schedule that has the compose of the TC on
 Tuesday (previously Thursday) and testing running from Tuesday to
 Wednesday (previously Thursday to to Thursday) of the following week.
 This also has the benefit of starting testing of the TC a few days before
 the weekend vs. Thursday and Friday as happened with Fedora 14.

 == Final RC Compose ==
 For Fedora 14 the, final Change Deadline was on Monday, followed by Tues
 to Thurs for Release Engineering create the RC.  Because of the earlier Go
 /No-Go meeting date for the final release  (Tuesday) this gave QA one less
 day to test than in the Alpha and Beta.

 I'm proposing that QA and Releng split the difference in the following
 way:
  * Releng does RC compose from Tues to Wed
  * QA Tests from Wed to Tues

 Updated schedule is here:
 http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #147: Ratify Fedora 15 Schedule

[Fedora QA]

#147: Ratify Fedora 15 Schedule
---+
  Reporter:  poelstra  |   Owner:  jlaska   
  Type:  task  |  Status:  new  
  Priority:  critical  |   Milestone:  Fedora 15
 Component:  Trac  | Version:   
Resolution:|Keywords:  meeting  
---+
Comment (by poelstra):

 If I don't hear any feedback by 2010-11-03, I will assume the schedule is
 fine and move forward with having FESCo approve it.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Fedora QA] #147: Ratify Fedora 15 Schedule

[Fedora QA]

#147: Ratify Fedora 15 Schedule
--+-
 Reporter:  poelstra  |   Owner:  jlaska   
 Type:  task  |  Status:  new  
 Priority:  critical  |   Milestone:  Fedora 15
Component:  Trac  | Version:   
 Keywords:  meeting   |  
--+-
 Time to set a schedule for Fedora 15

 Based on what we experienced in Fedora 13 and Fedora 14, should we
 continue with the same schedule methodology as it pertains to test
 releases, etc?

 It would be helpful to get feedback within the next week so Release
 Engineering can discuss and pass the schedule on to FESCo for approval.

 https://fedoraproject.org/wiki/Releases/15/Schedule
 http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test