If `Release:` contains `.test` the task would not be committable into the repository but otherwise builds successfully into EPERM. This will be useful to create test-only tasks protected against accidental committing into the repository. Reasons: other people see this is a test task not _intended_ for committing, test builds are protected from accidental --commit (mis-copy paste of task its, or commit instead of other similar task, or --commit days later when forgotten task's test purpose). With this maintainer can work safely on new packages (or "forks" of other packages) without risk of accidental commit. Also, it is clearer and safer to have this flag in the spec and not as (possible) `task add --no-commit-forewer` option.
