On Tue, 9 Oct 2018, Noah Watkins wrote: > On Tue, Oct 9, 2018 at 2:54 PM Sage Weil <sage@xxxxxxxxxxxx> wrote: > > > > > > > > Release source: > > > https://github.com/ceph/ceph/blob/3a2a93351954585adbb912994d9d7ad306f35189/doc/releases/releases.yml > > > > > > Sample rendering: > > > http://docs.ceph.com/ceph-prs/24452/releases/schedule/ > > > > > > > - Let's add a "latest" to the CURRENT section for each stable release > > Are you thinking something like: > > Version | Release date | Latest | End of life > > where "latest" for the mimic row would show "3.2.1", or > > Version | Release date | End of life > mimic/3.2.0 ... > mimic/3.2.1 ... Hmm, well now I'm thinking something more like Release Initial Latest End of life (estimated) mimic 2018-06-01 v13.2.2 (2020-01-01) luminous 2017-08-01 v12.2.9 (2019-02-01) kraken 2017-01-01 v11.2.1 2017-08-01 to capture the first part of the old table. > > Is the timeline section being generated? I see all of the old releases in > > the table but they're not in the source yaml. > > On that page there are two "TIMELINE" sections. The first is > generated, and contains back to kraken plus development releases back > to 2016. I'll convert once the schema / output is settled on. The > second "TIMELINE" section is the original static version. I see! I kind of like the old per-release columns, although I'm not sure how useful they really are... sage
