Through c8b3b553 (Merge pull request #1338 from
flaper87/sec-groups-update, 2019-05-01).
I've left 8d0847c02 (openstack: Support setting network UUID via
terraform variable, 2018-12-05, #794) undocumented, since it seems
like an unstable-enough user-facing API approach that I don't think we
want to noise it about and deal with the fall-out when we change the
API ;). That commit also made it into this history via 44a9cd38
(#1294).
I've also left off eecf4968 (openstack: remove neutron dns,
2019-02-19, #1294), because I have no idea what that's about ;). I'll
fill in an entry for it later once one of the OpenStack devs explains
it to me :p.
Also roll the tips-and-tricks docs into the overview's
multi-invocation docs, since they'd been covering the same ground with
slightly different wording before. I've expanded the unified
description to go into a bit more detail and tie in the new versioning
docs.
I've also documented the manifest-templates target from 166a9f1e
(pkg/asset: new target manifest-templates, 2018-10-30, #592).
And I've shifted a few "target directory" references to "asset
directory", since that's the language we use for --dir (as shown by
--help).
Since we completely removed the old subcommands, I'd added entries to
the "Added" and "Removed" sections while rebasing 220a5f75 (CHANGELOG:
Document changes since v0.3.0, 2018-11-01, #595). But I forgot to
remove the entry from the "Changed" section when I did that. I'm
removing it now.
Also fix a broken indent for the bootstrap-kubelet entry.
Through 9a730307 (Merge pull request #507 from
wking/drop-tectonic-version, 2018-10-20).
I've also updated the v0.2.0 docs to soften the claims about staged
installs, since v0.3.0 adds "loading assets from user-edited files"
while v0.2.0 only had "remembers previously-generated assets".
I'd partially replaced this with the generic $EDITOR in ec34840
(CHANGELOG: Document changes since v0.1.0, #461), but forgotten to
remove my personal choice ;).
This project has been evolving rapidly, which makes it hard for
occasional users to keep up. By cutting releases and documenting new
features, deprecations, etc., we can make it easier for users to get
back up to speed. Cutting releases also reduces our maintenance
burden by focusing users on the weekly (or whatever) release instead
of "wherever master was when I cloned".
