I suggest the creation of a TODO file at the root of the symfony-docs repository. This way, everytime someone finds something that's missing, the TODO can be populated.
On Thu, Apr 26, 2012 at 3:50 PM, ryan weaver <[email protected]> wrote: > Hi guys! > > There is a partial todo list of what's needed in the docs. via a "2.1" > label on the symfony/symfony-docs issues. This is by no-means exhaustive - > it's just been built as people have noticed things. A lot of 2.1 features > *have* been documented, but many have not. The best place to look is the > CHANGELOG for 2.1: > https://github.com/symfony/symfony/blob/master/CHANGELOG-2.1.md. > > So, a great thing to do would be to either check out the 2.1 tag at > symfony/symfony-docs, or scan through the 2.1 CHANGELOG and either document > something you think is missing, or even create a ticket to track it. If you > have some sample code but no time to find the right place for it in the > docs, just create a ticket and paste some dummy code in there - that kind > of stuff is AWESOME. :) > > Also, probably several of the things that will be delayed for 2.1 have > been documented on the master branch of the docs. That's ok, we'll just > need to create a 2.1 branch and do the sam reverting on it that is being > done in the code. Even if there are some issue(s) opened up on which > features are being reverted, I can help make sure that those things are > reverted in their correct places. > > Thanks everyone! > > Ryan Weaver > US Office Head & Trainer - KnpLabs - Nashville, TN > http://www.knplabs.com <http://www.knplabs.com/en> > http://knpuniversity.com > Twitter: @weaverryan > > > > On Thu, Apr 26, 2012 at 12:26 PM, Fabien Potencier < > [email protected]> wrote: > >> On 4/26/12 7:15 PM, Mario Alberto Alvarez Garcia wrote: >> >>> But that is just for the Form/Validator components or for all component >>> with BC changes? >>> >> >> Just for Form/Validator as this is where we have made the more BC breaks >> and many of them are still in flux and not stabilized yet. >> >> El jueves, 26 de abril de 2012 13:06:32 UTC-4, Lukas Smith escribió: >>> >>> >>> >>> On 26.04.2012, at 18:32, Fabien Potencier >>> >>> <fabien.potencier@symfony-**project.com<[email protected]> >>> >>> <mailto:fabien.potencier@**symfony-project.com<[email protected]>>> >>> wrote: >>> >>> > On 4/26/12 3:27 PM, Lukas Kahwe Smith wrote: >>> >> >>> >> On Apr 26, 2012, at 15:26 , Fabien Potencier wrote: >>> >> >>> >>> Forms and Validators. >>> >>> >>> >>> I've discussed with Bernhard and Victor and the plan is to >>> create a 2.1 branch, revert almost all PRs that break BC and release >>> 2.1 from here. They have already done the hard work at the beginning >>> of this week, so that we now have clear vision of what needs to be >>> done. Hopefully, this will land into the repository soon... which >>> means than an RC next week is totally possible. >>> >> >>> >> what will happen with those changes .. they will just be >>> discarded or reserved for a later version? >>> > >>> > They will stay on master and as such they will be available for >>> Symfony 2.2. The idea is to stop delaying Symfony 2.1, to have more >>> time to finialize all the changes Bernhard wants to make to the >>> Form/Validator components, and to only break BC (badly) once. >>> >>> ok sounds like a good plan. >>> >>> regards, >>> Lukas >>> >>> -- >>> 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 >>> symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%[email protected]> >>> For more options, visit this group at >>> http://groups.google.com/**group/symfony-devs?hl=en<http://groups.google.com/group/symfony-devs?hl=en> >>> >> >> -- >> 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 >> symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%[email protected]> >> For more options, visit this group at >> http://groups.google.com/**group/symfony-devs?hl=en<http://groups.google.com/group/symfony-devs?hl=en> >> > > -- > 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 > -- Klaus Silveira (011) 8564-2492 www.klaussilveira.com -- 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
