Hi, Back when the release process was passed, I repeatedly mentioned that it would be a good idea to have 2 additional things: 1) a list of topics to focus on for the next release 2) a release manager that ensures that the list from 1) is not overlooked as well as ensuring that the release process is followed
I still think that this would be a good addition to the release process as it can also help as a guidance for developers who want to contribute but are unsure where to best allocate their ressources. However I think that for our up coming 2.3 release its imperative that we at least have such a list I mentioned in 1). So what are the things we really want to see happening in 2.3: - remove all deprecated code - mark (all?) APIs as stable - update all documentation accordingly - .. ? From the top of my head I see a few areas, that we could add to the above list: - content negotiation support in the Routing component (https://github.com/symfony/symfony/pull/5711) - ResourceWatcher component (https://github.com/symfony/symfony/pull/4605) - core events for CLI (https://github.com/symfony/symfony/pull/6124) - HttpCache unbundling from HttpKernel and potential refactoring (see discussion in https://github.com/symfony/symfony/pull/6213 and some other HttpCache related PRs) - issues around ICU and ext/intl - Form layer open PRs (there are several open PRs with 50+ comments) As such I propose that we either revive the IRC meetings, try to organize a physical meetup of key core developers or some other way we can quickly identify our focus areas and a game plan how to get there. regards, Lukas Kahwe Smith sm...@pooteeweet.org
signature.asc
Description: Message signed with OpenPGP using GPGMail
