- no metadata was mandatory before
- now if you include a metadata entry, it has to have *all* entries: name, version, format, and description. any one of those will make lava-test-shell break
- existing test definitions will break when we upgrade production
I suggest that before rolling this out we:
- identify users who submit lava-test-shell tests to v.l.o and have incomplete testdefs
- notify those users that starting at 2013-04-XX, v.l.o will require the metadata to be complete.
- we wait at least a couple days after before we upgrade so people have time to fix their testdefs.
This has to be done quickly, because we should not wait too long with undeployed code in trunk.
So, the situation is that
- no metadata was mandatory before
- now if you include a metadata entry, it has to have *all* entries: name, version, format, and description. any one of those will make lava-test-shell break
- existing test definitions will break when we upgrade production
I suggest that before rolling this out we:
- identify users who submit lava-test-shell tests to v.l.o and have incomplete testdefs
- notify those users that starting at 2013-04-XX, v.l.o will require the metadata to be complete.
- we wait at least a couple days after before we upgrade so people have time to fix their testdefs.
This has to be done quickly, because we should not wait too long with undeployed code in trunk.