> On 12. Jun 2017, at 10:23, [email protected] wrote: > > What do you think of releasing the current release adapting properly the > version scheme (so that the two releases with the same content but different > versions coexist) and, from now on, use the new version scheme for future > releases?
What is the impact of this? I'd rather see the tools fixed (or at least an attempt at this) than trying to have everyone agree on a versioning scheme. For, Build Monitor View uses a "+build.201701152243" suffix, isn't that the same problem? -- 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/B9D29E29-C245-47E2-A0D6-B122403C36F6%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
