summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Sherwood <paul.sherwood@codethink.co.uk>2016-03-13 20:18:40 +0000
committerPaul Sherwood <paul.sherwood@codethink.co.uk>2016-03-13 20:47:08 +0000
commitd2da5b8dbd12733307c3d158c56c67e8f6239fff (patch)
treea36579c1dbfebac60a7bdb1ce05d8cca9cd1d848
parent32dc673e5a12d929d7953de098e07d68e337cf8e (diff)
downloadybd-d2da5b8dbd12733307c3d158c56c67e8f6239fff.tar.gz
Start testing.md, and move to docs/
-rw-r--r--docs/releasing.md (renamed from releasing.md)0
-rw-r--r--docs/testing.md21
2 files changed, 21 insertions, 0 deletions
diff --git a/releasing.md b/docs/releasing.md
index 6c553b3..6c553b3 100644
--- a/releasing.md
+++ b/docs/releasing.md
diff --git a/docs/testing.md b/docs/testing.md
new file mode 100644
index 0000000..4b2ee75
--- /dev/null
+++ b/docs/testing.md
@@ -0,0 +1,21 @@
+check_cache_keys
+----------------
+Since ybd 15.44, the cache-key algorithm appears stable and can be
+applied to definitions as far back as baserock-14.40.
+
+So we can use the cache-keys as checksums to avoid regressions in the
+algorithm. This doesn't matter much for the cache-key algorithm itself,
+since it is versioned, but checking that we can get to these values also
+confirms that we can still parse the old definitions files themselves.
+
+baserock-14.40
+v0: ci.6788f6634d42f0a42682bd2208cb123f69a157b4a50ac40108d91029558ec623
+v1: ci.b9de86669ce182e60e3f9445e6394b478b67a2c73b4c0764491c158c5f2569e9
+
+baserock-14.46
+v0: ci.6357ea38e22bcbc3ebc399d36ed3bbfe03cab79079ab5b97096b7fc36e0e3351
+v1: ci.99203daccc211d634102f94cab7095c7dae31c6daadc7541380d53e1b3b2fe8e
+
+baserock-15.47.1
+v0: ci.a809e39d26fea31b2dc674e190f6367a10cedaffe644775a59a93719cc5d5290
+v1: ci.ce7f81b2e294c1893a08e4b18cf1d9a74f5e49bb58f7099ab55f656a05d887b4