| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This will cause them to be rendered on GitLab and other git hosts'
web interfaces.
|
| |
|
|
| |
Related to #5.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is intended to replace all uses of "Trove" that should really be
"Downstream Host" or "Upstream Host", except in the database schema
and the REST API (which will probably change later).
* ARCH: Update example code to reflect API name change
* yarns.webapp: Update test descriptions and uses of internal APIs
* units: Update and rename the ls-troves units (although they still
use the ls-troves endpoint for now)
Some references that really are specific to Trove integration are
retained.
Related to #3.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lorry Controller is not limited to working with Trove, and we probably
shouldn't limit it to mirroring to a co-hosted git server. So:
* In the Requirements section, introduce the terms "Downstream Host"
to replace "local Trove" and "Upstream Host" to replace "remote
Trove" and "upstream Trove".
* In the Requirements section, use the term "Host specification"
instead of "Trove specification".
* In the Entities section, refer back to those definitions.
* Replace all references to Troves accordingly, except the code sample
(since the API has not yet been changed) and an example that is
specific to Trove.
Related to #3, #5.
|
| |
|
|
|
|
| |
While we're here, seeing as Adam mentioned it.
Change-Id: I5ddb86c70d76a84cf12fbd4eb91f3802e490d745
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Things have been implemented, no need for the plan anymore.
|
| |
|
