In this case, I will continue working on 3.0. By the way, I want to do a lot of work on it this Sunday & Monday; so if you have some changes to commit, it would be nice to do it before I get started :)
Pierre Henri. On Jan 21, 5:45 pm, "paulh" <[email protected]> wrote: > Pierre > > I'm not sure why Oren decided to go straight to Hibernate Search 3.1 rather > than working on the current port to 3.0 GA - this was picked as it was based > on a version of Hibernate that we have most of the features of whereas the > 3.1 has a dependency on Hibernate Core 3.3 which we are not compliant with. > > Completion level of the current port of Seach I would estimate at 80% with > the test completion at 60-70% with a current coverage of 60%, major lack at > the moment is support of thing like projections. > > Any patches you have are gratefully received - I can put tests in if needed. > > Regards > > Paul > > ---------------------------------------- > > From: Pierre Henri Kuate <[email protected]> > Sent: 21 January 2009 12:52 > To: NHibernate Contrib - Development Group <[email protected]> > Subject: Working on NHibernate.Search > > Hi all, > > I would like to summarize my understanding of the status of > NHibernate.Search and discuss its future dev. > > From the history in the SVN (http://nhcontrib.svn.sourceforge.net/ > viewvc/nhcontrib/trunk/src/NHibernate.Search/?view=log), I see that > the NH.Search in NHContrib is a port of H.Search 3.0, but I don't know > how complete it is. > > Ayende has also started a port of H.Search r15224 (pre-H.Search 3.1 > Beta2):http://nhcontrib.svn.sourceforge.net/viewvc/nhcontrib/branches/nh-sea... > By the way, H.Search 3.1 GA was released in December with some > interesting improvements (http://in.relation.to/Bloggers/ > HibernateSearch31IsOutPerformanceRobustnessAndNewFeaturesOnTheMenu) > > I am currently using NH.Search in my project and I have hacked it a > little to fix some small bugs here and there. But since these changes > are untested, I don't feel comfortable committing them. > > From my experience, the current NH.Search is still quite buggy; I > don't know if any of you has used it in production... > > So, where do we go from there? > > I agree with Ayende that stabilization should have a high priority. I > don't know if trying to fix the current NH.Search will get us there > faster than completing the port of H.Search 3.1... > > Pierre Henri. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" 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.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
