----- Original Message -----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Tue, 12 Nov 2013 04:49:05 -0500 (EST) Jaroslav Reznik jreznik@redhat.com escribió:
----- Original Message -----
On Mon, Nov 11, 2013 at 06:56:57 -0500, Jaroslav Reznik jreznik@redhat.com wrote:
I'd say the Go/No-Go should be the break point to release/not to release as for primary offering. It could be a part of the Go/No-Go meeting to state release readiness of all deliverables we have (based on the sign offs or directly in the meeting?).
For consistancy and blame I think that is a good idea. Dennis shouldn't feel the heat for when screw ups result in a spin being dropped. Having it done at that point also keeps people from hoping for some float to get the sign off done.
Do we have anything as https://fedoraproject.org/wiki/Test_Results:Fedora_20_Beta_RC5_Desktop for marking tests passed or just http://fedoraproject.org/wiki/Releases/20/Spins?
I don't think so.
I'm not going to comment what's written bellow, I think Dennis covered it pretty well. I'm sorry if I missed the spis process, I know it was happening and now I know it's enforced - so let's try to find the way how to put it into schedule, communicate it better. It's definitely worth having it, and I'd be more than happy to help with it!
This policy is change is something that should have been communicated to you, so there is blame to go around. I could have thought of doing that since I see enough to have been able to draw the conclusion that this is something that should have been on the spins schedule.
Current spins schedule is at [1], is the rest of tasks still valid? I'm going to add sign off there too.
Jaroslav
[1] http://fedorapeople.org/groups/schedule/f-20/f-20-spins-tasks.html
as the Spins are non release blocking i feel the testing and sign off should happen before QA requests RC1. from RC1 on it may be impossible to get a fix in.
That's a good point, for other desktops than blocking, potentially blocking issues are considered as automatic FE but it does not mean fix will be pulled in.
In schedule, we don't have specific date to request RC as it's based on the current state of accepted blocker bugs (RC is blockers free). First TC milestone is probably too early. Usually we don't have RC week before first Go/No-Go so it could be an option. Or Change Deadline (with early TC, there should be something testable and usable).
Spins guys, any thoughts?
Jaroslav
Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJSgkMkAAoJEH7ltONmPFDRJx8P/2JlcH3lHHBpKzzBoqSXbMqU rzcrYZSbeRnvu6PFXpwz0x7wxwpb/s9kurzjAHByzYDpuhRb0Mqn1Ydtpkrcce5Z bR89wJw6+hXxNrgza9lrXx/0zDP+w/r1fCfAMdBqLqOjpFmhdW607O3CrvLYjkBS sNbm3fANsnUfTr+05UP7FpQ+kWPYIgUvMDQ082XOFUl6Ob/Pl7Yob1rqIpvcveYM w/wtF0qNHR1Ct+L5NVeeOLz/vbIxcU/UdXmSXIUpgDFdkEXRCm3N7+yITK2M9dfr 5jzfdK/kCwpTZmOvevfsYXBlo4HdDZkEl6XCSNkZG799+sb0lq4cGKiOJ/TP3rOf SiD/EEBTvGakE3VB5FIqLpBGLF4HWiNGAdjZaRVl24ZvMZAskzIkFyZE2mV2x7FF BcP4539fp8ppDeFdKNkdc8ZxU4c92N4c3QCpc2mU55cVouF0Mkpp10nO60Vwu2no NYl9XrXgRzXCXZkCduv2T91Pf+8qzOTpFv3saIRn6sruBYSP+mAhzRN5R+fnAZ4V BOG520hmPZhGQXNC5eyQxJrdjH/TYBU0EBFf/0WySJJfefFm+rA/IejjHRbRUnVz yvRP/j6Wx09TVa4VEN+2qXSdDrpYKftwnyVSoNR4/tkzRiLr2XF6uiHViZuFGmjX Yp4UsWl3Kj3t7fgUChtY =3+KK -----END PGP SIGNATURE----- _______________________________________________ spins mailing list spins@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/spins