The doc8 linter found several syntax problems in our docs; primarily a
large number of places we used single-backticks to surround something
when we should've used double-backticks.
This is frontrunning a change that will add these checks to CI.
Change-Id: Ib23b5728c072f2008cb3b19e9fb7192ee5d82413
- move ipa-builder to projects that follow normal release
- add a new section Manual release for ironic-staging-driver
- update Things to do after releasing.
Change-Id: Ie6d02096dc15fc8c3f881556f1638d94ba2d8ece
The database schema upgrade check had support for an
explicit list of known versions to handle the upgrade.
who knew!
Anyhow, we haven't used it in three years since the addition,
and it seems to make more sense to just be able to indicate
"we know initial field versions may not be able to be retrieved
and act accordingly". As such, when no table is found, the
pre-upgrade version check execution will continue onward fearlessly!
Call it a spiritual successor to Ibcf0728bc5d1b0cbdd78796526f9c93fc99e8c08
Change-Id: Icae5162c2501b0d1217ad0e6ee34ebef40e95204
Fix the command to submit new releases and adds command reference
for the intermediate bugfix branches.
Change-Id: I79a039a6effcf8bd13e5c3ab5a231d5b515c8297
Based on latest changes [1] in the releases project that changed the
behavior of list_unreleased_changes.
[1] 4912f7d5d0
Change-Id: If5fd848bf3fddeb1ae66dc9aafa882588b83f41a
After a release we need to update the `templates` for zuul
in master to have the job for the new cycle.
Change-Id: Ic275ea9ec97f74732f4bafa99037c2d8a8229b91
The version check is run before tables are created, so it cannot
succeed for them.
Change-Id: Ibcf0728bc5d1b0cbdd78796526f9c93fc99e8c08
Story: #2004589
Task: #28467
This updates the release documentation to indicate that we have
to wait until grenade is testing the latest release against master,
before making code changes related to rolling upgrades.
Change-Id: I60a3343cfb4565da725a7b39c6ee8b04e4389dec
This test is not helpful for development at all - it only fails
after the version is issued, when it's too late to fix. Furthermore,
it blocks using the sem-ver tag in a commit message to bump minor or
major pre-version, as it expects the future release to exist.
Change-Id: I48034d1433b7e67f1ce2853227dd5a539e15a360
Also remove mentioning of the example configuration file from the
releasing docs, as we've removed it.
Change-Id: I8e2a2adcac7de69c3a03ddd560de96b0972b99e1
This uses reno's `earliest-version` directive to explicitly point out
where the release notes for a given branch should begin. There is a bug
in reno when dealing with stable branches, where it does not always find
the correct version to begin with.
It also updates our release docs to indicate we should continue marking
this. This step can be removed when the reno bug is fixed, though it
doesn't hurt to continue marking this explicitly.
Change-Id: I6502ff95a52c2c855356e9875291f27ec44e7ffa
Related-Bug: #1746076
This updates the Releasing Ironic Projects documentation to
highlight (in red) anything code-related or file paths.
It also fixes a typo.
This is a follow-up to 7e4857851dc8945eff935da351b7a56c923aff52.
Change-Id: If17be2fa4c20c32740b1b32766abf54897d3370b
This updates our releasing documention to reflect the releasing
process we went through for the Pike release.
Change-Id: I4e74f8bfe56e859d68ad7e9f81525a72db424ff5
This corrects the URLs in the contributor documentation as well as the
main index. The changes include:
- changing http to https
- changing absolute links to relative links (where applicable)
Change-Id: Iea392f8108ca4b5203682609dd78b980c1540b89
This adds the new command 'ironic-dbsync online_data_migrations'.
To limit downtime during upgrades, data migrations will be done online
with migration scripts that could be run during normal operation of an
ironic cluster, after the upgrade but before the next one.
Each migration script should ensure that all related DB records are
migrated to the new format. Scripts can detect the format based on
the object version which is stored in the version column.
The online data migration has one script; a function that backfills
the new version column, using versions of objects from the release
prior to this.
This includes code to check the object versions for compatibility with
an ironic release. However, the check is turned off (and will be turned on
in Queens), since we need to boot-strap the new version column before
we can turn the check on. To do this check, we need to keep a list of all
supported versions for every object; release_mapping.RELEASE_MAPPING was
modified so that the object versions is now a list instead of one value.
Change-Id: I1a9fa829951ecf98cae6896d82ba20cf89062394
Closes-Bug: #1585141
Partial-bug: #1526283
Co-Authored-By: Ruby Loo <ruby.loo@intel.com>