PS:
Kevin Kofler via devel wrote:
The way this was done is so wrong:
* There was a vote. You were not happy with the outcome.
* So you first tried to complain in the original ticket about this. It was
clear that the consensus in that ticket was to not reconsider at this
time.
* So instead, you filed up a *new* ticket, with *no* public discussion
(e.g., on this mailing list), and also with *no* link in the original
ticket, thereby excluding participants of the existing discussion that you
lost (who did not get any notification that the decision was being
reconsidered before it was too late and hence no chance to chime in).
* And then you expedited the issue to the next meeting, only 4 days after
it was opened, again precluding any kind of discussion or feedback.
* You apparently also did not even invite the toolchain team, the experts on
this issue, since judging from Florian Weimer's reply here and from Siddhesh
Poyarekar's reply in the ticket, they were caught by surprise by this sudden
complete reversal just as completely as I was.
* I also do not see anything that has changed since this was last
discussed.
* And as in the last discussion, I still believe that 2 releases, i.e., a
whole year, is way too long an evaluation period. If anything, this needs
to be evaluated in Rawhide only with the option to revert it with a mass
rebuild before feature freeze. It does not make sense to ship pessimized
Kevin Kofler