Hi Lukas, everyone else! I've not been close to the code development itself recently, but the docs have come alive recently with more planning and pushing (more info on a hackathon for the docs shortly). We didn't need this 6 or 12 months ago, but enough time and development has happend that it was time for us to refocus, revisit things that have been put away for awhile, and re-push.
The point is, if people feel that there are enough things lying around and we need to refocus, then it makes sense. Is there a feeling this is needed or would it be an extra layer? Is GitHub enough already? I'm not in a position to say - but it seems worth collecting some thoughts. And not that it's a good reason to meet, but I miss everyone :). Of course, someone would have to wrangle this all together... Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://knpuniversity.com Twitter: @weaverryan On Wed, Mar 13, 2013 at 12:07 PM, Lukas Kahwe Smith <sm...@pooteeweet.org>wrote: > 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 > > > > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
