we don't want manage each feature in a separate branch! If you want understand how NH is working have a look to the SVN history after NH1.0.4.
Is not a matter of "defensive" is a matter of your insistence asking basing your questions in your opinion without think that some others developers may have different opinion. In SVN there are different ways to manage trunk-branches-tags, that's all. 2009/11/7 alberto rodriguez <[email protected]> > > I think you are getting overly defensive, so I'll leave it here. A > short "because managing multiple branches is too complicated for us" > would have been enough. > > On 7 nov, 15:46, Fabio Maulo <[email protected]> wrote: > > cuanto tiempo queres que pierda contestandote eso ? > > > > The TRUNK is the main development line; the new LINQ provider is one of > the > > most important feature of NH3.0 and this is the reason because we have it > in > > the main development line. > > > > Where you heard that everything in the trunk is ready for production ? > > > > If you don't like it there is a very simple solution: > > Open a new branch in gitHub or where you want and maintain it as you want > or > > pay somebody to do that work for you; we can't maintain more than 2 > versions > > at the same time (this is a fact not an opinion). > > > > If you are afraid using the trunk in production you can use one final > > release (the last, NH2.1.1GA, was released few days ago). > > > > The NHibernate's team has strictly rules for commits in trunk: the trunk > is > > always compilable and must pass all our existing tests (more than 2100) > > because the quality is not achieved by chance. > > > > If you have another standard in your mind you can apply it in your team. > > > > Is it clear now? or you need some other explications ? > > > > 2009/11/7 alberto rodriguez <[email protected]> > > > > > > > > > > > > > What? I'm afraid I am lost. I asked why the new Linq implementation is > > > in the trunk since "it is not yet ready from production" yet, you > > > asked me for a reason to do so (not including it in the trunk) and I > > > gave you one. How is that related to the fact that many people compile > > > NH from sources? > > > > > On 7 nov, 14:54, Fabio Maulo <[email protected]> wrote: > > > > there are a lot using NH trunk compiling sources, or through Horn, or > > > > downloading from TeamCity... > > > > "nobody can use it" is only your opinion. > > > > > > 2009/11/7 alberto rodriguez <[email protected]> > > > > > > > I answered your question. Will you answer my question now? > > > > > > > On 4 nov, 17:01, Fabio Maulo <[email protected]> wrote: > > > > > > Just out of curiosity... why it should be in a branch instead > trunk ? > > > > > > > > 2009/11/4 alberto rodriguez <[email protected]> > > > > > > > > > Just out of curiosity, then why is it in trunk instead of in a > > > > > > > separate branch? :) > > > > > > > > > On 4 nov, 16:15, Fabio Maulo <[email protected]> wrote: > > > > > > > > The trunk LINQ prov. is a completely new provider based on > HQL > > > AST > > > > > > > instead > > > > > > > > Criteria. > > > > > > > > The trunk version is not ready for production. > > > > > > > > > > 2009/11/4 Bill Barry <[email protected]> > > > > > > > > > > > Someone should correct me if I am wrong, but as I > understand > > > it, > > > > > the > > > > > > > trunk > > > > > > > > > provider is the contrib version which has been merged into > > > trunk. I > > > > > > > think > > > > > > > > > that chances are most people asking on this list are using > the > > > > > contrib > > > > > > > > > version because they haven't updated trunk to the proper > > > version > > > > > yet (I > > > > > > > know > > > > > > > > > I haven't). I wouldn't plan to use either of them for a > > > production > > > > > app > > > > > > > but > > > > > > > > > rather figure out how to help Steve Strong get the new > provider > > > > > > > written. In > > > > > > > > > the meantime I suppose it doesn't matter which one you > choose > > > to > > > > > use. I > > > > > > > > > would wrap it in a proxy class so that you can easily > replace > > > it > > > > > when > > > > > > > the > > > > > > > > > time comes: > > > > > > > > > > > public class LinqProvider { > > > > > > > > > ISession _session; > > > > > > > > > public LinqProvider(ISession session) { > _session=session;} > > > > > > > > > public IQueryable<T> Query<T>() {return > _session.Linq<T>(); > > > } > > > > > // or > > > > > > > > > .Query > > > > > > > > > } > > > > > > > > > > > This could be a transient IoC provided object you may use, > or > > > you > > > > > could > > > > > > > do > > > > > > > > > new LinqProvider(ISession).Query<Blog>()... every time you > want > > > to > > > > > use > > > > > > > it > > > > > > > > > (though I would go a bit farther and implement an > IQueryable > > > > > repository > > > > > > > > > class like this: > > > > > > http://www.codeinsanity.com/2008/08/implementing-repository-and.htmlb...tome). > > > > > > > > > > > Mohamed Meligy wrote: > > > > > > > > > > > I have been using the NHibernate Contrib LINQ provider for > a > > > short > > > > > > > while, > > > > > > > > > then a friend told me that NHibernate trunk itself has > another > > > LINQ > > > > > > > provider > > > > > > > > > that he heard is better. > > > > > > > > > > > However, I see all the LINQ related questions here use the > one > > > from > > > > > the > > > > > > > > > NHibernate Contrib - ISession.Linq<>() not > ISession.Query<>() - > > > so, > > > > > it > > > > > > > > > gets me confused. > > > > > > > > > > > The question is: > > > > > > > > > *Which NHIbernate LINQ provider is reocmmended to use *- > > > > > > > ISession.Linq<>()or > > > > > > > > > ISession.Query<>() -*, both short term (now) and long > term?* > > > > > > > > > > > Thank you very much, > > > > > > > > > Regards, > > > > > > > > > > > -- > > > > > > > > > Mohamed Meligy > > > > > > > > > Information Analyst (.Net Technologies) – Applications > Delivery > > > - > > > > > TDG > > > > > > > > > Injazat Data Systems > > > > > > > > > P.O. Box: 8230 Abu Dhabi, UAE. > > > > > > > > > > > Phone: +971 2 6992700 > > > > > > > > > Direct: +971 2 4045385 > > > > > > > > > Mobile: +971 50 2623624, +971 55 2017 621 > > > > > > > > > > > E-mail: [email protected] > > > > > > > > > Weblog:http://weblogs.asp.net/meligy > > > > > > > > > > -- > > > > > > > > Fabio Maulo > > > > > > > > -- > > > > > > Fabio Maulo > > > > > > -- > > > > Fabio Maulo > > > > -- > > Fabio Maulo > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
