[LTP] [PATCH 1/1] doc/maintainer: Add policy for new functionality

[Cyril Hrubis]

Hi!
> Yes. Although we could add "next" and "rc" flags to tst_test (or
> similar). Then require an environment variable to be set (or check the
> kernel version) otherwise the test will return TCONF.
> 
> For LTP releases we just need to check if the flags are still needed or
> if the feature has been merged. The metadata parser can generate a list
> of tests to check.
> 
> This seems like quite little work to me. In fact we don't even have to
> implement it until someone wants it. We can just add it to the policy.

I was thinking of this and if we really want this feature it would make
sense to add "remove_before_use" flag to the test structure what would
render the test resultless. Ideally it would include the kernel version
the functionality is going to be included into, then we can
automatically check in the CI the test metadata against latest release
kernel version and either remove the flag or bump it in case it didn't
get in.

Maybe just .remove_after_release = "5.9"

@Ritchie feel free to go ahead if you want to implement and maintain
         something like this.

-- 
Cyril Hrubis
chrubis@suse.cz