> What changed was that there was a period after 6.3 was pushed out the > door (2-15 April) in which there were effectively three active > releases and the project felt obliged to support 6.1 until 6.3's > projected release date. My previous post attempted to review a > possible workaround, though I suspect this sort of anomaly might not > be practically avoidable.
You are making stuff up.
