On 10 July 2018 at 15:26, Dustin Wheeler <mdwhe...@ncsu.edu> wrote: *snip*
> Personally (for Class Friendship), I opted to target either 7.4 or 8.0 > (whichever was decided to be next-in-line) > Seems to me this is one of the issues - that this is something that isn't just set in stone. If there was an overall roadmap of major and minor versions, along with set dates and deadlines that could not be moved, this wouldn't be an issue. > > At the same time, I would hate to see a TON of additional process / > voting constraints come as a response to this issue. > > That said, if feature freeze for a release is announced well in > advance, published, and there was an agreed "best intentions" policy > to not submit RFCs that encroach on that date, then I think all would > be well. I don't think there's any intent to slide features in under > the finish line. It just seems like a lot of ideas finished baking at > a weird time. That, or subconsciously, the talk of a new version of > PHP sparked folks to get off their ass and put forth their ideas! :P > > > I think a hard deadline would be a better solution. Past that date, it simply doesn't matter what the RFC is about, it'll make the next version at the earliest, not the current one. Movable feature freeze and release dates do not benefit the language or its users, nor most of the core developers, I'd say. Just my take on it. -- CV: https://stackoverflow.com/cv/peterlind LinkedIn: plind Twitter: kafe15
