oh and here is a link to luke Jr wanting to throw in a difficulty twisting hard for with only a 3 month grace period (#GracePeriodHypocracy)
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-March/012489.html
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-March/012489.html
That doesn't support anything you said.
Quote
I think it may be reasonable to push for at least code-readiness before July, and possibly roll it into any other hardfork proposed before or around that time.
Are you not aware of the Hardfork Wishlist? It's been around since at least January 2012. The premise is that if bitcoin ever needs to hard fork, these are desired improvements that can only be implemented with a hard fork and therefore should be included. Luke's proposal has been on the Wishlist since at least January 2012. It's always been considered a bug to be fixed when possible. And he speaks of including it in a future proposed hard fork -- not a hard fork for the sake of implementing that bug fix alone -- as would be expected. The concept isn't controversial in the slightest (assuming sufficient testing). But feel free to explain how it is.
Also, you misunderstood regarding 3 months. He said it could be rolled into anything proposed around that time, because the code should be ready by then. He says nothing about the time period between consensus on rule activation and fork in regards to this proposal, though he is known to be conservative in that regard.
Your assumptions about Luke's proposal were also shown to be false: https://bitcointalk.org/index.php?topic=1387549.0;all