Fabio, I think it depends on what is your job. I know a lot of corporate where the developper can't use a framework not compliant with several criterias.
If you are working on a project using nhibernate as I do (and i'm very happy with it); with a large number of entities, it is still very usefull to forecast a migration process, take time to learn the new functionnalities to really leverage the new version. But I still agree that the "official release" considering nh is more about "marketing" than stability. There is a good test base and the trunk is stable. Well that's continuous integration... I guess it is like using SQL : you are always fighting dinosaure. So when you can select and choose, it doesn't matter. But if your job is to recommand a technology; it is difficult to get credit if you don't have perspective on the roadmap. I don't want to flame the post, but a similar situation occurs for me a couple of month ago : we choose a framework for a particular task, and there was a roadmap identifying key relase dates; with the supposed new functionnalities. The first release is now over 6 months lates, and now a lot of people are asking if it is safe to go on with this framework. I do think that the answer is : don't give any roadmap if you have no intention of being in time. I mean, you've made quite an amazing job with NHibernate, you don't really need this kind of question to put discredit on the release process. That's the way things are in it : If you say you release, everyone is expecting you to release on time; and everyone THINKS that what is between two releases is under dev or completely buggy. Regards, Fred. Selon Fabio Maulo <[email protected]>: > No ? are you sure ? > we are using trunk of NH, trunk of NHV, trunk of NHCH, trunk of NHSpatial, > trunk of NHSerach, trunk of uNHAddIns, trunk of ConfORM in production. > > On Wed, Jun 16, 2010 at 8:04 PM, Craig van Nieuwkerk > <[email protected]>wrote: > > > I think it is important when planning a project manager types are > > often not happy to use beta versions. > > > > On Wed, Jun 16, 2010 at 11:40 PM, Paco Wensveen <[email protected]> wrote: > > > I always wonder why people care about release dates. What does it > > > matter if it is released or not (except political reasons)? I do > > > understand someone is interested in the release of a specific feature, > > > but for NHibernate, it will be the same code as the trunk. The > > > revision will be labeled and be called a release on that day I guess. > > > > > > > -- > > 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]<nhusers%[email protected]> > > . > > For more options, visit this group at > > http://groups.google.com/group/nhusers?hl=en. > > > > > > > -- > 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. > > -- 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.
