Le 9 février 2012 15:45, Clément OUDOT <[email protected]> a écrit : > Le 9 février 2012 15:35, Sébastien Bahloul > <[email protected]> a écrit : >> Hi Clement, >> >> You can push the 1.2.2 version and tag it, but I would like to avoid >> publishing a new 1.2.X version because new users should now use the 2.0 >> branch as the 1.2 version is not anymore maintained. > > Ok, I will do that : tag 1.2.2 and push 1.2.2 files in the files section. > > But regarding the site and the roadmap, it is not clear that we do not > maintain 1.2 or 1.3 branch. For example, is this issue included in > 2.0: http://tools.lsc-project.org/issues/205 ? > > And 2.0 is just a release candidate, not a stable version... Maybe it > is now the time to publish the real stable version and move unclosed > bug to 2.1 or 2.0.1 ? To be honest, I did not test the new version so > I don't know if it's ok to release it. > > Whatever we choose, we must update the roadmap, so users will know we > do not work anymore on 1.X version.
So, 1.2.2 is released on the forge, we won't do any communication around it, it just for maintenance. In the roadmap, I closed all 1.2 versions. There are still issues for 1.3 versions, I let you decide what to do with them. The goal would be to have only 2.X versions in the roadmap. Clément. > > > Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
