As discussed on Bug #26866, to be able to generate code for Foo1 and Foo2 simultaneously, we need to include the version number in their filenames and node names.
Created attachment 57135 [details] [review] Version the names and node-names of all versioned interfaces Otherwise, either we can't generate code for Foo1 and Foo2 simultaneously, or the rules for when you version and when you don't are really confusing. See fd.o #26866.
Created attachment 57136 [details] [review] Put Call1 in the node name, filename of Call1 sub-objects
Created attachment 57137 [details] [review] Document Telepathy 1.0 versioning conventions
I believe this is a necessary consequence of what Jonny proposed on Bug #26866, and worth doing to have less confusing rules for versioning than we do on master.
This all looks good. We should point out more why some other interfaces are core (Text because if you break that Telepathy can be useless; Call1.Content.Interface.Media because that'll just break Calls; etc.) but we can do that at some point. No rush.
(In reply to comment #5) > We should point out more why some other interfaces are core (Text because > if you break that Telepathy can be useless; Call1.Content.Interface.Media > because that'll just break Calls; etc.) but we can do that at some point. Right, I'd missed that Text was still core. I reverted addition of its version number and uploaded a snapshot to: http://telepathy.freedesktop.org/spec-next/ Leaving this bug open for "point out which interfaces are/should be core".
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/128.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.