2015-10-01 18:57 GMT-07:00 Kaj Kandler <[email protected]>: > Go for it! Those 4 digit minor numbers are getting a bit long :-) > > I'd just go for the UX/UI theme as 2.0. Not that all other things are > desirable too, but just the visual part could be a big boon and some > disruption for the plugin community as well. That said, is UI going to be > important going forward with DSL and Workflow? >
Yes, because we still want you to come to Jenkins to find out what's happening. Just that you won't have to go there to configure. I also think documentation improvements could be really helpful. > * For example I could not find a definition of the general Queue mechanism > and discipline, only references in plugins that change it. But nothing > authoritative. > * Similar, the documentation of extension points and API's is gravely > lacking (what is getBuildVariables() supposed to do? Can it call > getEnvironment()? Not if it wants to interoperate with a later build of the > SVN plugin, which calls getBuildVariables() in the getEnvironment - poof > stack overflow - who's fault is it? Oh, why does getBuildVariables() not > have any access to a logger?) > OK. Build variables vs environment is a confusing one indeed. > I personally love Wikis (at least those that accept Wiki syntax, which > Atlassian messes up with its newer versions and standard Wysiwyg editors > that break everything). > So my take is that you like textual syntax, which is what we are proposing wrt static site. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yoi8ifLAdPpm1fJGZWH72Q3Jvsr42x-BHZgJfzAbL-PQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
