Thomas Martitz wrote:
It seems we're trapped. On the one hand, for people which do have
the problem, the realease would be a grand failure. On the other hand,
we (accidentally?) kept promising USB will be THERE in 3.2.
Where did we promise anything beyond *hopefully* having it?
The last week before a release isn't meant for testing, but for fixing
the very last issues (and language updates), but I still may propose
that that FS#8802 and FS#10015 should be fixed/committed immediately
(saratoga reported great success on the latter one) after the freeze,
and that we reconsider enabling USB 1 or 2 days before the 23rd.
We've been in freeze for a week. We're approaching the branch after
which nothing is supposed to be changed unless it can't be avoided. It
needs to basically be in a "final" state before the branch, we shouldn't
plan to change things after it.
The branch should basically be looked at as "the release date" with
things only changed if we completely missed something. Applying patches
and leaving a feature on during the branch, to disable it right before
the end, is a DEFINITE no-do. It completely flies in the face of why we
do things in this order. That's the sort of thing that could've happened
during the freeze, possibly, but not the branch.
