Thanks to those who attended the documentation community meeting this morning. We've updated the etherpad (https://pad.ceph.com/p/Ceph_Documentation) with all of the feedback from the meeting and from this e-mail thread. The current plan is to select and complete one enhancement from the pile of options, and then revisit the topic once a month to select a new improvement. We'll be starting with adding a link to github source / PR, and a mechanism for reporting issues. If you'd like to tackle one of the improvements, please reach out at anytime. - Noah On Fri, Sep 28, 2018 at 6:01 AM Lenz Grimmer <lgrimmer@xxxxxxxx> wrote: > > On 09/25/2018 09:30 PM, Alfredo Deza wrote: > > > On Tue, Sep 25, 2018 at 3:02 PM Gregory Farnum <gfarnum@xxxxxxxxxx> > > wrote: > >> > >> This is interesting, because there's a conflict between using the > >> "stable" and current "master" branches in our docs — a lot of > >> documentation changes are actually general improvements which > >> apply to all our live releases, not just the master branch they go > >> in on. > >> > >> Should we start tagging documentation PRs for backport? > > > > We backport docs with code changes for ceph-volume. If components are > > getting backported without its corresponding doc update it is a bug > > (otherwise why have per-release versions of docs). > > I agree - if a backported bug fix introduces a change in behavior, the > docs of that version should be updated accordingly. > > IMHO: general documentation enhancements that apply to older versions as > well should also be backported similar to bug fixes for older releases. > > Lenz > -- > SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) > GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg) > > >
