Michael Cronenworth wrote:
- Requiring an update from the get-go for this package is frivolous.
It's quite common practice actually. For example, the whole KDE was updated to 4.1.3 around the day of the F10 release and we're planning to do the same with 4.2.3 and F11. Other packages also work that way.
The advantages of pushing stuff as updates on release day: * it can't break the live images or the installer, * there are 1-2 extra weeks for testing/fixing (the time between the RC composes and the first update push), * it's possible to go through updates-testing (e.g. KDE 4.1.3 went to updates-testing in the first F10 update push and to the stable updates in the second).
The drawback is that they don't get included on the live images and the installer DVD, but need to get updated by the user post-install, but that's not a big issue for the mingw32-* packages because they aren't on the live images or the installer DVD anyway, at worst this can affect custom spins including those packages but not including updates.
Kevin Kofler