I would not say I am 100% happy since the current state requires long PR builds, etc. I would also prefer keeping changelogs in the main repo. But now it is definitely a step forward compared to what we had before. If we experience significant issues with the current state, likely we will consider moving to the separate repo.
BR, Oleg понедельник, 20 февраля 2017 г., 13:37:10 UTC+1 пользователь Arnaud Héritier написал: > > Ok. If main contributors are happy with it, I have nothing to say. > > Le lun. 20 févr. 2017 à 12:42, Daniel Beck <m...@beckweb.net <javascript:>> > a écrit : > >> >> > On 20.02.2017, at 11:37, Arnaud Héritier <aher...@gmail.com >> <javascript:>> wrote: >> > >> > I don't like to have the changelog leaving outside of the project >> repository. >> >> It already was in the case of LTS (which AFAIK is the line more >> successful with users since we made it more discoverable on the site), and >> nobody cared. (And don't get me started on the uselessness of old LTS >> changelogs…) >> >> The technical 'changelog' is the (history in the) GitHub repository. What >> we're discussing here is user documentation, similar to the LTS upgrade >> guide. So it's not wrong for it to be in the site repository, where the >> rest of the documentation delivered via the site lives. >> >> > Am I the only one? Aren't we taking a risk to have it outdated? >> >> No less than before. At least for the past year, Oleg and I were the only >> ones filling in the changelog for releases (often on the Monday following >> the weekly release, so there were plenty of opportunities for others to >> contribute). >> >> In fact, we started actively discouraging changelog additions in PRs due >> to additional merge effort when they aren't merged the same week, and >> conflicts even when they are. >> >> Oleg and I wrote ~95% of the weekly changelog for the last year. Oliver >> and I wrote all of the LTS changelog. We were all in favor of this change >> as you can see in the PR referenced below. >> >> > Wasn't it possible to copy it from the project repo to the website >> build ? >> >> As I explained in >> https://github.com/jenkins-infra/jenkins.io/pull/661#issuecomment-280625408 >> that would not be a great idea unless we add significant infra support >> around the changelog (generate its HTML independently from the site build). >> Doesn't seem worth the effort. >> >> -- >> 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-de...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/257C76FC-E970-43FE-8096-72A44F9E68EA%40beckweb.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > ----- > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > -- 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/c9942c8d-88de-45ea-bf59-9e8611b5ad76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
