I strongly suggest to set forth an end-of-life date for the 1.6 branch, to give our users sufficient time to prepare for the next upgrade. Of course, it makes no sense to drop support for 1.6 before 1.7 will be released, and as it is not clear when that will happen, it is hard to define a fixed date. On the other hand, there is PHP 7 which is scheduled for release in October (I guess it will be delayed, but probably not much). I'd rather won't support the 1.6 branch for PHP 7 (presumably it won't be that hard, but you'll never know). That would imply that we have XH 1.7 ready when PHP 7 is available -- I expect at least a few hosters to switch early after its first GA. That means we should get out XH 1.7 this year.
So I suggest to vote about "Set 1.6 branch EOL to 2015-12-31". The voting options would mean:
- "now": make it so
- "later": set the EOL to 2016-06-30
- "never": set a later EOL (would need a further voting)
Furthermore I suggest to vote about "Deny PHP 7 support for the 1.6 branch". That doesn't mean that the 1.6 branch won't necessarily run under PHP 7, but rather that we explicitely deny any warranty that it will (what might safe us painful work).
That are two votes, but presumably a single discussion thread might suffice.