> > > And Jenkins 2.0 is a big change for users --- you suddenly get a whole lot of > new things you haven't used before, and it encourages & promotes different > ways of using it. I think it's well qualified to call it 2.0, and I don't > think it's trying to untrain the general expectation. > I was on jenkins 2.0 meeting that took half of it presenting workflow. What > is the problem to use workflow in 1.xx? I don't see that workflow requires > breaking something in core. > UI change yes. DB change - yes. >
I also had this feedback when I discussed about a 2.0 with few Jenkins users. Will it increase the stability and performances of Jenkins. For them these are clearly the most important improvements which may motivate them to take the time to upgrade to a 2.0 They’ll love to have a better UI but it seems that it’s not enough interesting compared to the cost to upgrade to a major version (they probably have more in ming the upgrade maven 1.0 -> 2.0 than 2.0 -> 3.0) We clearly need to identify the cost/risk of the upgrade and discuss with users if the value provided is enough to justify it Arnaud -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15AA2ADC-53B5-42A7-83FD-540C5B79C9C7%40gmail.com. For more options, visit https://groups.google.com/d/optout.
