[ADD] reference/external_json_api

[Julien00859]

No description provided.

[robodoo]

[AntoineVDV]

I think it would be better to move the RPC-related content to a new file and reuse the very well-referenced external_api.rst file for the new external API instead. Then, in 19.1, the file about deprecated-now-unsupported content can be removed.

This is also because we don't document when this or that feature was added, deprecated, or removed. The documentation for version X.Y documents which features exist in Odoo X.Y, no more no less.

[Julien00859]

I think it would be better to move the RPC-related content to a new file and reuse the very well-referenced external_api.rst file for the new external API instead. Then, in 19.1, the file about deprecated-now-unsupported content can be removed.

Done

This is also because we don't document when this or that feature was added, deprecated, or removed. The documentation for version X.Y documents which features exist in Odoo X.Y, no more no less.

That we are dropping XML/JSON-RPC is serious enough to mandate the deprecation danger. A common question I've been asked is "is the JSON-2 API available in 18?", hence the "new in 19.0" passage.

[Flotchet]

Great stuff! Clear and all! Just some little grammar stuff and a bit of nitpicks and that's basically all for me.
Thanks for the work 💪

[rco-odoo]

Good to me.

[jakubsmolka]

Would it be possible NOT to rely on OEXP and OCA github communication and send this information directly as a newsletter/through account and partner managers to Odoo partners and customers?

It is big and important enough IMHO to be communicated directly to all necessary stakeholders. The fact that Fabien was considering to completely remove the old API for V19 with basically just 2 months in advance was scary enough, but I believe it is good not to underestimate the time it can take various parties to align themselves with this change - and the only reliable source of communication where Odoo can say "we did our best to reliable inform everyone in time" are the ones mentioned above

[Julien00859]

Hello @jakubsmolka

I like your idea of pro-actively reaching with the stakeholders, I'll try to push the idea at work.

[Julien00859]

@jakubsmolka

We met with Antony about this matter. Our communication will only take place during OXP, we won't use other communication channels, emails to stakeholders have been explicitly ruled out.

[jakubsmolka]

@jakubsmolka

We met with Antony about this matter. Our communication will only take place during OXP, we won't use other communication channels, emails to stakeholders have been explicitly ruled out.

OK, thasnk for the info and confirmation. I do wonder in a year when Odoo 20 comes out, how many parties will be surprised and how many external platforms with Odoo integrations will "suddenly" stop working for new customers or after upgrades... but if that's a situation you are fine with occuring, I guess there is nothing else we can do. (and I know it will always happen to a degree that someone will be surprised, but it feels like not doing everything reasonably possible to communicate it properly.... is just inviting to make it worse)

[Julien00859]

Hello @odoo/documents-doc-review we are ready

[AntoineVDV]

@Julien00859 As discussed, we won't have time to review this until after the freeze. You said it only had to be merged for OXP but if you need the odoo/odoo PR to be merged ASAP, I recommend closing the documentation PR to let the other one go through ;)

[rco-odoo]

Let the odoo/odoo PR go through.

[robodoo]

Reopening a PR in a merged batch is not allowed, create a new PR.

[Julien00859]

Reopening now that the community PR is merged

[AntoineVDV]

Woops, that's new 😮

You can open a new PR, I will check it now.

Or ask runbot if it's really necessary to prevent this.