I think the main benefit of keeping the ProtoBuf opaque is avoiding the unnecessary effort of fleshing out a schema that will change very soon. However, since I have a full specification described here already, I prefer to go ahead with it, unless there other concerns I have missed.
I suggest that the process for upgrading this schema should be opening an RFC like this one (ideally linking a PR with the desired .proto changes). I would also like to point out some caveats with ProtoBuf usage. - It's highly encouraged that proto fields are never removed, but instead marked with a "deprecated" flag unless you are aware you will break backwards compatibility. For the ansor changes, if we are deprecating autotvm 1.0 entirely, I think it would be ok to remove fields as needed. If that's the case, the case for a fully specified schema as the resolution for this RFC makes more sense, as it would be good for people to have an explicit schema to refer to for pre-ansor logs. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-canonicalizing-autotvm-log-format/7038/12) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/dd22276db30d804e92311d12ca738b54fc116a42f4878c255650115148f935ab).
