In a meeting today between Release Engineering, QA, and various team
leads, we decided to enact a 7 day slip of the Fedora 11 release date.
The primary reason behind this slip is the state of our blocker bug: https://bugzilla.redhat.com/showdepende ... resolved=1 We cannot begin Release Candidate phase until the blocker bugs are closed or at least in MODIFIED state. We are not there today, which would be our last day to enter RC phase and still have enough time to release on the 26th. We hope to enter RC phase in the next couple days, and hit our new target, June 2nd.
Freeze breaks for critical bugs will still be accepted, however trivial
bug fixes should be pushed as updates via bodhi. Thanks!
A neutron walks into a bar; he asks the bartender, 'How much for a beer?' The bartender looks at him, and says 'For you, no charge.'
4ndY je napisao/la:
Iako, definitivno je stabilnost bitnija od datuma izlaska (ali ne kao kod Debiana... koji kasni i po par mjeseci+).
EDITED: iako, do sad su možda 2-3 Fedore u povijesti izašle bez odgode
A čuj, koliko vidim na Bodhi-ju, na Fedori se sve voli malo dulje istestirati. Pogledaj npr KDE4.2.x
Na OpenSusetu se već odavno vrti, sok ovdje kasni po par tjedana jer je u statusu testiranja.
Fedora je po pitanju izlaska novih stvari ni pre spora ni pre brza. Ima neku mjeru, a da se ipak prođe kakav-takav testni period.
Meni je to sasvim prihvatljivo. (Ubuntua se npr. i tako ne instalira dok ne prođe prvi mjesec od izlaska releasea )
A late discovered and just potentially fixed anaconda storage bug[1] has
necessitated another week slip of our schedule. The change is important
but invasive enough to require re-validating our storage tests. We were
already late in producing the Release Candidate and there is not enough
time to produce another one and validate it in time for next Tuesday's
release date. Therefor we have decided to enact another week long slip
of the release. This gives us time to create a second release candidate
and fully validate it and hand it off to the mirrors in plenty of time
to sync up for the new release date of June 9th. As much as we regret
slipping, we also wish to avoid easily trigger-able bugs in our release,
particularly in software that cannot be fixed with a 0-day update.
At this time we would only accept tag requests for critical issues.