Add changelog for 2.68

[daniel-beck]

Compared to the proposed changelog I trimmed the entries for the remoting update, as they all seemed related -- in fact, the link to the documentation for the first entry mentions the next two as well -- and therefore overly verbose. An (unfinished) intermediate state I tried:

This seemed excessive, especially given that AFAIUI nobody gets any of this without reading the linked docs on how to enable it.

---

While on its own not notable enough for the changelog, the documentation for time zone was not just improved, but now exists for the first time, so calling out the feature's presence in the changelog seemed appropriate.

---

@oleg-nenashev

[oleg-nenashev]

@daniel-beck Some changes are missing:

• [JENKINS-38527] - Prevent NullPointerException in Slave#createLauncher() and add cause diagnostics jenkinsci/jenkins#2923
• [JENKINS-43496] - Add handling of the null Node#createComputer() result. jenkinsci/jenkins#2922

[daniel-beck]

@oleg-nenashev Overlong commit messages coupled with squashing make it very difficult to find these, as the #1234 isn't visible on a /compare/jenkins-2.67...master URL. As I've asked before, please refrain from squashing unless it's necessary due to a particularly messy history.

Note that I did mention one of these at https://github.com/jenkins-infra/jenkins.io/pull/973/files#diff-5313295831c35cd7b37d630b93438d60R781

[daniel-beck]

I see the second one of these similarly not noteworthy, it's improving in robustness, but as this is a user changelog rather than a replacement for the git history, there's no reason to include these unless they fix a bug actually encountered by users.

[oleg-nenashev]

@daniel-beck Both issues have been seen in the wild (at CloudBees customer instances). The changes add some hardening, and they will be LTS candidates. Hence it worth mentioning them

…

On Jul 2, 2017 1:50 PM, "Daniel Beck" ***@***.***> wrote: I see the second one of these similarly not noteworthy, it's improving in robustness, but as this is a user changelog rather than a replacement for the git history, there's no reason to include these unless they fix a bug actually encountered by users — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#973 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC3IoN6ExwK8ESIyD4iYAYgjenwfY6gVks5sJ4QZgaJpZM4OLdAt> .

[daniel-beck]

@oleg-nenashev Done. I went with one entry for both. Does "related to agent connections" capture these correctly?

[oleg-nenashev]

@daniel-beck works for me though it makes people to look into the linked issues. Which is probably fine