Le 6 avril 2012 23:46, Sébastien Bahloul <[email protected]> a écrit : > Hi Clement, > > Le 6 avril 2012 17:55, Clément OUDOT <[email protected]> a écrit : >> >> Hi, >> >> >> I tested the 2.0 version this week and I wanted to give some feedback, >> more than all issues opened in Redmine. > > Thanks for it ! > >> >> Let me start by saying this new version is cool, the XML configuration >> is a good idea, and the persistent search on LDAP server a really big >> feature. >> >> That said, I have a lot of remarks, that I share in a constructive >> perspective : >> >> * Subversion repository is a mess, I see 3 location of the >> administration interface : lsc-webai, lsc-webui, >> lsc/branches/trunk-webai ! I think the current implement is lsc-webai >> (I hope, because I worked on it). > > Administrative interface has not been developed for quite a moment and is at > a very early stage.
Ok, I believed it was developped to be released with 2.0, but we can maybe delay it to the next major version. For my needs, I will maybe wok on it before, to ship it as a separate module, but I really think it should then be released in the main LSC package. > > The old AI repositories are still visible because of SVN but if you know a > way to delete them, go ahead :) Yes I think a svn rm can clean a little the repository. Are we agree to keep only the lsc-webai directory? Same question for lsc-sample/ and lsc-samples/ ... >> >> * I do not understand why we have a syncrepl connector in plugins, >> what is the difference with the built-in persistent seaech in lsc-core >> ? > > The plugin was interrupted as described on the pom.xml description : > https://lsc-project.org/svn/plugins/trunk/connectors/syncrepl/pom.xml ok, it should also be removed I think. And the reference also removed from the pom.xml of webai. >> * The Redmine roadmap is also a mess, I do not understand why we have >> 2.0 and 2.0.X versions, but no 2.0rc1 and 2.0rc2? How can we know >> which bug was resolved in rc1 and rc2? > > No way to track them at this time but it should be. If you agree, I will create 2.0rcX releases in redmine and reassign some issues. >> >> And these versions seems only >> for lsc-core, how do we assign issue to WebAI? And the SVN commits >> >> messages never reference issues, it is quite hard to find what problem >> is solved in a commit. > > As I wrote before, WebAI is at an early development stage and not released, > so I don't think that it is highly required to track fixes and updates at > thi stage. I propose to create a version webai-1.0 in redmine to assign issues. >> * Some bugs are corrected in the trunk but not in 2.0 branch. My >> opinion is that all should be done in 2.0 branch and the applied in >> the trunk > > Yes it should be, but now the job is done on the trunk to avoid breaking the > 2.0 releases because of the various tests that should be done to release the > next RC and that are not automated. What you call "job" is new features for 2.1 releases? Can we consider the trunk is the version 2.1? Anyway, all bug fixes done in the trunn must be ported to 2.0 (or the contrary). >> To sum up, I will try to contribute to the project to help to release >> 2.0, but I think we have to take decisions on how manage code >> organization and versions :) > > Thanks for your interest and I agree with you as soon as it remains quite > simple : > - release policy: vhttp://lsc-project.org/wiki/qa/ > - the 2.0 version has been released because it has waited for a long time. > I'd like to avoid adding new features, but all bugfixes should be also > applied on the 2.0 branch. Ok, so I think we have to decide which issues are locking the release of 2.0 and work on their resolution (I will of course work on it). Then release the 2.0 quickly, to be able to work on 2.1 and also provide bugfixes versions for 2.0. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
