platform policy: add new targets

[paulidale]

If a new target doesn't modify the C sources and is considered low risk, it can be added to LTS releases.

This will require an OMC vote but it is being raised here for discussion.

[levitte]

Assembler?

[paulidale]

Deliberately not mentioned: it falls under the "low risk" part.

A new assembler file just for the platform would be something I consider low risk. Modifying an existing assembler file would be less clear.

I've no objection to adding assembler if others think it worthwhile.

[levitte]

I'm satisfied that it has been thought of

[mattcaswell]

This seems different to what we have previously talked about (LTS+). Is this idea instead of LTS+, or do you still see a place for that idea?

[paulidale]

I see this as in addition to LTS+. LTS+ would allow code changes for new platforms e.g.

I'm really just thinking about a way to approve PRs like openssl/openssl#14724 without votes.

[richsalz]

I don't have a view on whether assembler changes are in-scope, but I think this discussion shows that there is new code (such as for risc-v some day?) and modifying existing code (the recent ARM changes), and the policy should cover that. Not necessarily with explicit statements, but a general thought.

[t-j-h]

I would not have put "C" in the description - this is an easy thing if there are no code modifications.
But with code modifications (assembler) being allowed it is a lot less safe as it is basically adding new implementation logic rather than just compiling the same code on another platform. i.e. this went beyond build flags.

[paulidale]

I've removed the C from the text.

[mattcaswell]

"the required changes do not modify the source code" is still somewhat vague if you ask me. What exactly qualifies as source code? Is a .info file source code? What about a ".conf" file? What about a ".tmpl"?

[kroeckx]

I guess you can turn it into: "is acceptable so long as the required changes are deemed low risk by the OTC"

[kroeckx]

At which point you can argue that assembler changes from 1 branch to an other are also low risk ...

[paulidale]

@kroeckx, I was thinking along similar lines originally.

[paulidale]

Failing vote closed in anticipation of further discussions about what is and what is not allowed.