Branch and tags organization
Closed this issue · 6 comments
Actually I can see master and 2.0 branches.
We are in Symfony 2.2 now, and soon, 2.3 will be out.
How do you will organize branches and tags ?
It is really necessary to support old version (like 2.0 and 2.1) with the LTS version of Symfony ?
The 2.0 branch is unmaintained (as it's for symfony2.0, which is unmaintained).
Currently I'm trying to keep master compatible with symfony 2.1, 2.2 and 2.3 (there are still some failures for 2.3), so that there is not several branches to maintain.
If it's not possible, I'll extract maintenance branches, and during next months, support for 2.1 and 2.2 will be dropped, and we'll focus on 2.3, accordingly to http://symfony.com/doc/current/_images/release-process.jpg.
Ok, asking this question because I found lot of deprecated function actually.
I can help you if you want with PR for some FormType, but I thing you are working on it to.
So which part of your project I can contribute to ? :)
I've just extracted a 2.1 branch for symfony 2.1 and 2.2 support, tests are passing, because deprecations are ignored.
Current master is dedicated to symfony 2.3, we should focus our effort on this one, feel free to submit PR if you find anything wrong :), I'm not working on any type for the moment.
So, for deprecated function, I have to PR on master branch ? And for general bug (form validation not working for ex.) ?
Now I see 2.1 and 2.2(master) branches.
2.2 si only for 2.3, if I want to PR a bugfix or an ehanchement for 2.1 branch that works with sf2.2, can I do this ? Or what to do ? :)
yes you can, changes in 2.1 are then merged into 2.2.