What is the most notable difference between Jenkins and Hudson from an user perpective?

Question

It is around 10 months now that Jenkins split off from Hudson.

When looking at the project homepages I am wondering what the differences between Hudson and Jenkins in the meantime really are. From the changelog I do not realy learn much. There are a bunch of changes and the major difference seems to be that Jenkins releases more often with less changes and Hudson less frequently, but then with more changes in a release.

Are there any notable differences yet? So are there things that make me as a developer needing a CI system more productive rather with the one or the other? Is one of them more stable than the other? Is there any difference yet that has nothing to do with politics around Oracle?

What is the most notable difference from your point of view?

Answer 1

One notable difference is that a big number of plugins moved to Jenkins. While you would still be able to use the old versions with Hudson, the newer versions depend on Jenkins already. Also new plugins are mostly created with dependencies on quite recent Jenkins versions, so you probably won't be able to use them without hassle on Hudson.

This will probably differ from plugin to plugin, some might be more compatible with Hudson than others, while still others provide versions for both tools. But if something does not work well with a plugin you will receive help easier if you use Jenkins.

EDIT: Here is an interesting link I found, not only providing some solid numbers on the different paths Jenkins and Hudson have taken, but also addressing the (non-)issue of IP that was mentioned in the other post here...