On Wednesday, April 4, 2012 12:53:19 AM UTC+2, Lukas Smith wrote: > > Aloha, > > since my last mail on this topic kinda went without a reply. > > can we start talking about a timeline for 2.1? > > 1) i believe that we still need to really review all BC breaks, especially > the form related ones, and determine if they really makes sense, of they > should get a forward compat tweak to 2.0 > 2) again from my POV composer is now in good enough shape that its not a > show stopper anymore and of course people can continue to use the old > vendors script. > 3) i discussed briefly with Fabien in Denver about switching > symfony/symfony to be a collection of submodules and making the > component/bridge repo's the target for PR's. not sure if he has dropped the > idea as it will make maintaining 2.0 a serious pain, but the benefit would > be that for projects just using some components the contribution workflow > would be a lot nicer > As a Components Only™ user, I can add my developer use case:
I was using the Routing component (among others) when I realized my project needed to match routes based on the domain of the user. As I'm not using the full framework, I never considered looking at existing bundles (still don't know if there are any). Instead I started by just extending a few classes to see if my idea would work, and how much change was needed. Actually extending classes and mapping classnames etc. was quite easy to do, but I found that I had to override a few rather large methods, thus making future updates a pain. Instead, I decided to fork the component and point my project to my forked version. This was also rather easy. I would still need to keep my code up to date with upstream, but a simple rebase would do the trick. Once my modified version was production ready (for my needs), I wanted to contribute back to Symfony2. At this point, I had a working version, in a repo forked from the upstream component, basically one click away from a PR. Instead, I had to clone the full Symfony2 repo, port my changes over and push. Which really turned out to not be a big problem at all. While I worked on the patch in the full repo, I reworked the code to have proper test coverage, and at the same time found some bugs and made som changes. Now I had two versions which were no longer in sync. And (barring me just lacking some Git voodoo skills for cross repo merging) this was more of a hassle. As my code was already in production, waiting for the pull request to be accepted and made available in the official routing component, I had to keep using my own forked version, extracting the changes I've made after moving to the full repo. Luckily, I have not needed to do many changes in my project, so I have not had to do much cross repo syncing. To sum up: 1. Cloning and working on the full repo is not a big deal 2. Keeping full repo and modified component in sync is more problematic The second point could possibly be mitigated by a simple How To from someone with more Git skills than me, but being able to open pull requests for components, and then having some magic (or people) doing the syncing would be even better (from a user/developer perspective). -gunnar P.S.: My pull request, still open, is here: https://github.com/symfony/symfony/pull/3057 > 4) i am unware of any major PR's that urgently need to get into 2.1 > otherwise (though of course bug fixes should always come sooner rather than > later) > > so imho we should start discussing 1) on the list and then schedule a > meeting for thursday next week (or whenever Bernhard and Fabien can both > join) were we can discuss anything we couldnt resolve on the list. the > following week we should then hopefully be able to publish a first RC (i > dont think we need an alpha/beta phase). we should probably aim for 2-3 RC > releases with a one week wait between, which should give us a stable > release in the first half of may. > > this is already much later than we all had hoped back in december so i > think its high time we get going with this release. > > regards, > Lukas Kahwe Smith > > On Wednesday, April 4, 2012 12:53:19 AM UTC+2, Lukas Smith wrote: > > Aloha, > > since my last mail on this topic kinda went without a reply. > > can we start talking about a timeline for 2.1? > > 1) i believe that we still need to really review all BC breaks, especially > the form related ones, and determine if they really makes sense, of they > should get a forward compat tweak to 2.0 > 2) again from my POV composer is now in good enough shape that its not a > show stopper anymore and of course people can continue to use the old > vendors script. > 3) i discussed briefly with Fabien in Denver about switching > symfony/symfony to be a collection of submodules and making the > component/bridge repo's the target for PR's. not sure if he has dropped the > idea as it will make maintaining 2.0 a serious pain, but the benefit would > be that for projects just using some components the contribution workflow > would be a lot nicer > 4) i am unware of any major PR's that urgently need to get into 2.1 > otherwise (though of course bug fixes should always come sooner rather than > later) > > so imho we should start discussing 1) on the list and then schedule a > meeting for thursday next week (or whenever Bernhard and Fabien can both > join) were we can discuss anything we couldnt resolve on the list. the > following week we should then hopefully be able to publish a first RC (i > dont think we need an alpha/beta phase). we should probably aim for 2-3 RC > releases with a one week wait between, which should give us a stable > release in the first half of may. > > this is already much later than we all had hoped back in december so i > think its high time we get going with this release. > > regards, > Lukas Kahwe Smith > > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
