Hi, When BlueOcean was originally being developed, James Dumay, who was a Director, Product Management at Cloudbees was very active in leading Blue Ocean, and communicating status and milestones with the Jenkins community.
Since James has left Cloudbees, what I have observed is: 1. No one at the manager/director level is visible on the https://gitter.im/jenkinsci/blueocean-plugin Gitter channel to communicate with users or get feedback 2. Many bugs filed against Blue Ocean in JIRA are unassigned 3. Cloudbees employees who log into https://gitter.im/jenkinsci/blueocean-plugin seem to be doing so as a best-effort/volunteer level. For example, on Nov. 16, Keith Zantow reported: *Keith Zantow @kzantow Nov 16 06:36 @rodrigc hard to say exactly what's in the road map at this moment, but certainly open to patches* Can someone in Cloudbees management comment on the company's commitment to Blue Ocean? I try to do what I can. I've submitted one bugfix: https://github.com/jenkinsci/blueocean-plugin/pull/1794 And submitted a few bug reports: https://bit.ly/2B8MmmQ Blue Ocean is very good, but needs some bugfixes and usability fixes to meet parity with the Jenkins Classic UI. Blue Ocean is some complicated "modern JavaScript", and I don't have enough time to dig into it to fix the problems myself. I am trying to push Blue Ocean and Pipeline very heavily at the companies I work for, and for the most part everyone I talk to really likes Blue Ocean, but the bugs/gaps are a problem for wider adoption/success in the projects I work on. Thanks for any feedback. -- Craig -- 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/CAG%3DrPVcjVMQjcw0Q8PueVwiPZV%2B3ZM938dW%3DFCHshioByqhMiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
