I've been following the split from a distance. It now seems that an exodus just started of plugin maintainers [1] so the Hudson community will probably need to attract some new maintainers to keep those plugins available in the long run. It's a shame people obviously can't get along (and company politics have probably added to that as well) so we now end up with two forks that may or may not stay compatible. Oh well, they should have built all of this on OSGi anyway. ;)
So far my +1 goes to Jenkins for being more community driven, but only time will tell and I guess the OPS4J community can relatively easily change its mind anyway. Greetings, Marcel [1] http://java.net/projects/hudson/lists/dev/archive/2011-02/message/117 On 16 Feb 2011, at 16:53 , Pete Carapetyan wrote: > ditto on Niclas's comments > > On Wed, Feb 16, 2011 at 9:15 AM, Niclas Hedhman <[email protected]> wrote: > +1 on Jenkins. Have more trust in a community than 2 companies of > varying talent on open source community management. ;-) > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
