I was just looking on nhforge and saw the most recent release of nhibernate 3.0 is the alpha 1 release. Is that the most recent available binaries, or did I miss them?
Also, is nhiberante 3.0 solid enough to use in a production environment. Is anyone currently using 3.0 for development?
I am beginning to develop a new project and was wondering if I should stick to 2.12 or if it safe to move onto 3.0.
Thank for any thoughts.
EDIT -
I just found the following web post - http://www.infoq.com/news/2010/08/NHibernate-3.0 - which contains the following -
"NHibernate has reached version 3.0 Alpha 1, and is “rock solid”, according to Jason Dentler, author of the upcoming book "NHibernate 3 Cookbook" from Packt Publishing, and interviewed by Scott Hanselman. Dentler also said that even if it is an alpha release, NHibernate 3 is already used in production."
NHiberante does not have an instable branch. The code in the trunk is stable, but it is not feature complete until released. There can be issues in new features, but no issues in existing features. You can use the NHiberante trunk in production. Thousands of people do it already, you won't be the first one. The version in the trunk is more stable than the alpha binary release, because it contains bug-fixes. For NHiberante the rule is: The newer, the more stable.
"ready for production" is hard to answer. I suppose since it's alpha, you can simply say "no".
However, I am using it in a small project that is in production with no issues at all. I am quite impressed with the quality and "solid-ness" for an alpha release. Note that I have much of the code using nhibernate covered with integration tests, so my confidence is pretty high.
Related
Trying to test some code in Pharo 2.0 and it depends on BlockContext which was dropped, what can I do?
You can download Pharo 4 and run Magritte 3 and Seaside 3.1, as that are the stable versions. The major change in Magritte 3, introduced and explained early 2012, is the moving of the descriptions to the instance side, and renaming description to magritteDescription. You can find sample code of Seaside & Magritte in a QCMagritte image you can download from CI, in addition to the plain magritte builds
Otherwise, just check the pharo, seaside and pier mailing lists of 4 years ago and the monticello repositories to see what changed. There have been lots of little changes because of the improvements in Squeak and Pharo in the past 4 years.
If you need to use Magritte 2 to migrate legacy code you might want to take a look (with Pharo 5) at my experimental MonticelloProjects code on Smalltalkhub. That builds a data structure of all source code in the Monticello packages in a project repository, allowing you to more easily see what changed when.
I am an NHibernate newbie so I apologize if there is an obvious answer to this that I'm missing.
I see some questions on SO and some blog posts referring to NHibernate 3. But when I go to nhforge.org, it looks like the current downloads are for 2.1.2. Is 3 still a work in progress? Are there betas available somewhere? Documentation? Is there an established timeframe / roadmap for 3.X?
Update:
NH 3 has been released :)
http://sourceforge.net/projects/nhibernate/files/
You can download the latest NHibernate 3.0 Alpha from Sourceforge and view the roadmap / change log for the project on the NHibernate Issue Tracker.
If you click on the "Download Now NH 2.1.2" link on the NHForge home page, that will bring you to the download location for NH 3.0 Alpha 2 source and binaries.
http://nhibernate.info/
For release notes, see this thread from the NH user's group (basically, release notes are available in the download):
http://groups.google.com/group/nhusers/browse_thread/thread/e0cc47b01207b5ae/ef89fb5218e46fd7?lnk=raot&fwc=1&pli=1
Here is an NHibernate features page. Some, but not all, of the 3.0 features are called out here:
http://nhibernate.info/doc/nhibernate-features.html
The NHibernate documentation is here:
http://nhibernate.info/doc/nh/en/index.html
But the documentation doesn't appear to have been updated for NHibernate 3.0 yet. Most of the 3.0 features have documentation available on various blog posts that you can find through Google searches. I'm sure the project would love to have a volunteer pull all the documentation together in one place.
The timeframe / roadmap for NHibernate 3.0 to be officially released is whenever the important bugs have all been fixed. You can watch the progress on bug fixes on the NHibernate JIRA:
https://nhibernate.jira.com/browse/NH
Like most software, NHibernate 3.0 will be released when "it's ready". Here's a quote from Fabio, the project lead for NHibernate:
Roadmap: we hope to fix all of the
actual existing open issues but
because we know that it will be
impossible we can only say you that we
will release NH3 before the end of
this year.
(Source: http://groups.google.com/group/nhusers/msg/40769ab8b95750fc)
From the NHUsers mailing list, it sounds like quite a few people are running NH 3.0 in production.
You can find some information about NH3 from this podcast
http://www.hanselman.com/blog/HanselminutesPodcast225LearningAboutNHibernate3WithJasonDentler.aspx
You can also find the source for the project on source Forge
http://sourceforge.net/projects/nhibernate/files/
It hasn't been released yet. I believe it's still in the alpha stage, as per the wiki
And actually, after listening to Hanselminutes Podcast 225 - Learning about NHibernate 3 with Jason Dentler, http://nhibernate.info/ is a great place to get all the information you're looking for.
Check their website.
You can download binaries there: http://sourceforge.net/projects/nhibernate/files/NHibernate/
I'm getting ready to deploy the first release of our software, version 1.0. Once it's out to our customer, inevitably, some bugs will be found. When I fix those bugs though, I'm not sure what "best practice" is for versioning it. When I release the fixes, would that be an entirely new version (in maven), such as 1.01 (or whatever the increment is, 1.1 for example)? Or would it still be 1.0 with some sort of classifier (maybe a date tag)?
Thanks,
Jeff
Wikipedia has a surprisingly thorough discussion of software versioning. It covers all the major points and discusses most of the approaches I've seen.
(In your specific case I'd go with 1.0.1 which would generally be regarded as "an update to 1.0 with no significant feature additions")
You have to change the number in order for maven clients to recognize a newer version in the repository. The change is up to you. I'm sure there's a best practice document somewhere but my company dictates the numbers we use so I've never looked for one.
We are in mid of a project where we have used an extended Dojo 1.1.1 to meet the customer requirement and add richness.
But there are quite some bugs and performance problems with this version of Dojo and
we are looking ahead to migrate the Dojo version to overcome both the issues, but the migration cycle seems to be quite painful and may not be yield expected result.
The concern we have is with the various extension which we have created with the version of Dojo for components that were provided in 1.1.1 and the impact on them after migration.But, the advantage we see are equally important.
As per Dojo , they have kept some level of compatibility with version 1.1.1 but i have not seen any discussion around this anywhere.
Has any body else previously done
migrated between Dojo version?
Will the components like Grid will
work as expected or will i need to
carry out a refactoring exercise?
Do we have any commercial support
available as the forum seems to
deprecated?
Any help or suggestions are welcome
Dojo has had a policy of freezing and supporting public APIs since 1.0. Migrations prior to 1.0 were extremely painful. Now, it should be much better, provided you use only public APIs. Code written for stable JS APIs in Dojo or Dijit in 1.1 should largely still work. Exceptions are noted in the release notes, which you should explore (good luck finding them... unfortunately the site is a bit of a mess)
If you wrote any custom widgets, you're probably in for some extra work. dojox.grid was not particularly stable at that point, and it has also seen a major rewrite since then (there is an old 'compat' layer you may wish to use)
Regarding for forum, like the note says, you can either use the active dojo-interest mailing list or post questions here at SO. There are some firms which offer commercial support, but that's outside of the scope of Dojo as an open source project. (try googling 'Dojo commercial support' or asking on dojo-interest)
I have done 5 dojo migrations now (from 0.2 -> 1.4) over the last few years. Although the API does not change, you will often have coded in workarounds that no longer work after upgrading. Things I have noticed:
quality in 1.4 is VERY good and worth
upgrading to (even from 1.3)
although
the API does not change, little
things that are not public often
change slightly (diji.Tree
itemNodeMap -> itemNodesMap in 1.4)
build options are usually added each
release but not always publicised -
strage really as they are always
useful improvement
since you are 1.1.1, you should change all your set attribute calls to 'attr' - this could take a while to do.
As for commercial support, you could try Sitepen
I'm writing a small free tool. It's currently in Beta testing using .NET 3.5 but there's at least one aspect from .NET 4 I'd like to incorporate.
So, is it jumping the gun a bit to release .NET 4 based software?
Thx!
Wait till atleast the public release of .NET 4.0 before releasing anything other than early beta software with it.
I'm excited about alot of the new stuff too, but beta software built on a framework that is itself in beta is a recipe for disaster if you ask me.
Writing code for 4.0 might make sense. Releasing for general consumption prior to its official release seems foolish to me. Minor changes in 4.0 between now and the official release could cause your code to break. It would likely be easy to fix, but until you do your users are mad at you for putting out (what appears to them to be) a buggy program.
I read somewhere that VS2010 comes with a go-live license, meaning you can. Not sure I would, though. (See other answers...)
Well, you'd be forcing people to download and install Beta software. People may be reluctant or even unable to do this so, if nothing else, you're limiting your audience.
Also anything built with the Beta software isn't guaranteed to be compatible with the final released version.
I wouldn't go for the full framework, but including libraries like the CTP for the Task Parallel Library if your application is heavily multithreaded would be OK since you can just ship the .dll with you application and your users won't have to download anything. However, even with the TPL I would watch out, it's quirky and can slow your algorithms by an order of magnitude on things that should seemingly run just fine. The CTP is already over a year old though.