Documentation updates for upcoming Eloquent release

[mjcarroll]

• Add Eloquent release page with timeline
• Update roadmap
• Copy installation instructions for Eloquent

The Eloquent release schedule attempts to keep the spacing of the Dashing release, with some slight adjustments for ROSCon. I generally assumed that internal and external contributors will be distracted by travel and the conference, so avoided putting any deadlines in that week.

[maryaB-osr]

Great, we've been discussing putting this up now to be pointed to by the "latest" page, what do you think about that? I was putting together the file structure here, obviously without the content (and I'll just scrap that PR now). The idea is that references to the "latest" developments, if anyone's interested in installing them, will point to the upcoming release. For now that's Eloquent.

All that would mean is adding a note to Installation.rst, under the table, saying something like:

"The next (or upcoming) release is under development. You can install it here"

And link to Latest.rst, which redirects to Eloquent.rst.

That is, if you think it's a good idea to let people install eloquent while it's under development?

[mjcarroll]

That is, if you think it's a good idea to let people install eloquent while it's under development?

I think prior to at least the alpha, the installation instructions are going to be largely for collaborators to make updates about dependencies and Eloquent-specific instructions. We won't have a first round of packages out until after that date. I would suggest that we maybe delay adding the concept of Latest until that point?

[dirk-thomas]

The Maintaining-a-Source-Checkout doesn't seem to be distro specific at the moment.

This should be merged without squashing at the end (to keep the separate commits for duplicating and changing the Eloquent pages). Before that please squash into a minimal number of commits.

[dirk-thomas]

lgtm

[dirk-thomas]

I think prior to at least the alpha, the installation instructions are going to be largely for collaborators to make updates about dependencies and Eloquent-specific instructions. We won't have a first round of packages out until after that date.

Before Debian packages are available the instructions are used for from-source builds as well as can be used to obtain the nightly archives from Jenkins.

I would suggest that we maybe delay adding the concept of Latest until that point?

The concept of "latest" always exists. It is the state on the default branches which will become the upcoming release.

[maryaB-osr]

Before Debian packages are available the instructions are used for from-source builds as well as can be used to obtain the nightly archives from Jenkins.

The instructions for binaries are already linked on the Eloquent installation types page, so if we have latest point to it now that part would have to be changed...

[mjcarroll]

The Maintaining-a-Source-Checkout doesn't seem to be distro specific at the moment.

Yeah, I diffed between Crystal and Dashing and there weren't any changes there. Would you propose moving it up a directory?

[dirk-thomas]

Would you propose moving it up a directory?

Sure, if it is not distro-specific there is no point in duplicating it.

[mjcarroll]

I reworked this into a minimal number of commits, and consolidated the maintaining a source checkout to only one page.

[dirk-thomas]

Please don't change the file while also moving it. In this case the extra empty line can just be removed.

[mjcarroll]

Fixed, sorry I missed that.

[dirk-thomas]

👍 to not-squash merge