One of the feedbacks on 2.0 has been that we need to bring more transparency to what's being targeted for the initial launch and what's the remaining work.
I took much too long, but I finally created https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=66 Comments, thoughts, etc are all welcome. The general rule of thumb for me here is that we shouldn't have tickets in here who don't have the assignee agreed to commit the task to 2.0 GA (see timeline <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0#Jenkins2.0-RoughTimeline>.) Not all the tickets currently satisfy this criteria and I need to still chase down some people to get those nailed, but I think it's in the good enough state now. I'd also point out that there are 3 tickets currently assigned to Chris that are very parallelizable, and I think it'd be a great place for everyone willing to help to pitch in. -- Kohsuke Kawaguchi -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4w-3%3DUMHiPoYfnqLEj8enjRSUBhnEKgRrBZym4d7fiBAA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
