Le 9 mars 2015 18:22, "Les Mikesell" <lesmikes...@gmail.com> a écrit : > > On Mon, Mar 9, 2015 at 11:53 AM, Baptiste Mathus <bmat...@batmat.net> wrote: > > I tend to disagree. People using LTS are somehow conservative and would be > > at risk to get confused: "so, in the end, is that LTS safe, or is it going > > to screw up my data?". > > Yes, when you know that LTS is going to screw up data, it only seems > reasonable to post it in a visible place.
Ahem. That's the point here. The LTS is not concerned by that change... > > > We could indeed add information in the LTS changelog that is going to change > > *in the future*, but I personally think it's just better to leave it clean > > for non-advanced user. > > I thought the point of even having LTS was to be able to avoid known > issues to the extent possible. So when an issue affecting it becomes > known, the ideal thing would be to _fix_ the by-then-known problem, > but if that is too much to ask, warning about it would seem > appropriate. See above. > > > If you install bleeding edge version, better read the changelog in general. > > And if you don't and it crashes, then read the changelog. > > In this case, it was not a lot of versions of difference so not even much to > > read. > > But when you want to get away from the crashes of the bleeding edge > version and back off to LTS in hopes of doing better you probably > won't be happy when it eats your existing data... > > > What I agree on, though, is that we may want to add some kind of disclaimer > > in the main changelog, and on the download link (latest and greatest one) to > > warn users that it may be (very) unstable and depending on their situation > > they may prefer trying LTS. > > There is an issue in general with breaking changes in stored data > formats and one-way migration. And this is hardly a unique case. > Switching to LTS is a likely, but not the only thing that may make you > need to go backwards. It would be nicer if such breaking changes had > a way to convert back - or at least there There is. Read the link, did you? > was a 'big-picture' of what > versions (including plugins) could deal with the storage formats of > what other versions. For example, installing the latest svn plugin > broke all of my stored credentials and I had to back the plugin out > and restore the credential files from a backup. Where can I look to > know what to expect in situations like that? https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin in this case, in general. Then depends on your very issue. Cheers > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > You received this message because you are subscribed to the Google Groups "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpysu6H2aJHohXud4YqDKWqAiQbpSm%2B9TO4mGXXApTPoCQ%40mail.gmail.com . > For more options, visit <https://groups.google.com/d/optout>https <https://groups.google.com/d/optout>:// <https://groups.google.com/d/optout> groups.google.com <https://groups.google.com/d/optout>/d/ <https://groups.google.com/d/optout>optout <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4OJuSdzexeZo%2BZVOgsUvB%3DNr5M2-oM-utruyon9MY2wQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
