I would agree with Alex. I would prefer "fix quickly, release often" pattern instead of waiting months for trivial (or may be not) fix. IMO, "core" should have it's own release cycle with major features planned, cautious development etc, while additional package may be released faster with help of NuGet.
понедельник, 4 марта 2013 г., 10:07:49 UTC+4 пользователь Alexander I. Zaytsev написал: > > Hi Patrick > > 1. I think that ability to make own small package instead of building own > NHibernate is an advantage. As for now many dialects/providers are outdate > or have minor or even trivial errors, and people often wait years to have > these issues to be fixed. Also there are number of independent providers > already in the Web. Also as we have CI in place we can build automatic all > the providers we already have. > 2. In world where nuget rules it is no more need to have all-in-one > assembly, so for me it is not argument anymore. In other words - you can do > "install NHibernate.YourFavoriteDatabase" and NHibernate will be installed > as dependency. > > Best Regards, > Alex > > > 2013/3/4 Patrick Earl <[email protected] <javascript:>> > >> It has the significant disadvantage of losing synchronization with the >> core so there would be more disparity between the different packages in the >> NHibernate universe. For example, has the PostgreSQL dialect been updated >> to work with NH 4.2 yet? If they're all secondary citizens, you'll >> probably get one or two that get pulled along and the others will stagnate, >> making it a far greater task to use a different database since you'll have >> to contribute patches and wait for a release or make your own packages. >> >> It also loses the simplicity of needing just one package to perform the >> basic operations. >> >> Myself, I think the loss of simplicity outweighs the benefits derived >> from separate release cycles. >> >> Patrick Earl >> >> >> On Sun, Mar 3, 2013 at 8:19 PM, Alexander I. Zaytsev >> <[email protected]<javascript:> >> > wrote: >> >>> Hi everyone, >>> >>> I think it will be extremely useful to have separate distribution for >>> dialects/drivers. I see some advantages of this: >>> >>> - shorter development cycle for dialects/drivers, it means we can >>> deliver fixes end enhancements much quickly >>> - better integration with ADO.NET providers, as we will not need to use >>> reflection >>> >>> What do you think? >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]<javascript:> >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nhibernate-development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]<javascript:> >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
