Hello Peter, > -----Original Message----- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, October 17, 2021 11:27 AM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > Hi Jörg, > > > I am not sure what you refer to.
I refer to the fact that changes in the API documentation are marked in time (the typical entry is "since ..."), so that the API documentation can be used in practice for all program versions. > The documentation has no > influence on > backward compatibility. right. What I am referring to is only that we should not make changes if the QA is not 100% guaranteed. And what I currently experience is that there is a tiny(!) problem in the API documentation, but immediately demanded now to regularly renew the documentation routinely. Explain to me bitterly where there are at all changes in the API that would make it necessary to update the documentation inflationary frequently? I follow every release carefully, only from API changes I have not noticed for years. > It would be beneficial if we update the documentation > with each release, > allowing a process that the documentation improves. And where is this process? What I see is that we don't even have a regulated QA for the program. Why do you want to make more work for which quality assurance never has the time? > I would not see documentation update as a blocker to a release thought. Neither do I in the least, but that's not the point, it's the quality assurance of the API documentation. Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
