Lines Matching refs:API
25 ## Update API status comments
45 2. Update the API documentation in all header files (.h file) to have correct
52 to generate API status change report.
68 Update the API documentation to have correct @draft/@stable/@deprecated labels.
69 See the [User Guide, ICU Architectural Design, ICU API
77 To check the API status changes, run the ant target "apireport" to generate the
84 * @deprecated This API is ICU internal only.
94 example, a new @draft API introduced in ICU 60 will be kept @draft in ICU 61.
95 Then the API will be reviewed by ICU technical committee before ICU 62 release
96 and the API can be promoted to @stable status.
107 * Do the API promotion - search the sources for @draft, and make a best guess
110 * Run the API change report tool, see what looks inconsistent, fix up the
113 * Cross-check the API change report and the spread sheet.
123 API
128 * Any API added 2 or more releases ago is a candidate for promotion.
130 6. Check each API entry has a corresponding approved API proposal. For example,
131 [ICU 59 API proposal
133 Note: An API proposal might have been created before the API proposal doc
134 version, so you may need to look at older version of API proposal status
137 8. Update API comments in ICU4J source code. In this case, @draft is replaced
140 9. Run next ant target to generate an API change report html: `$ ant apireport`
148 ## Update the API Change Report
154 1. Update the API documentation in all header files (.h file) to have correct
171 3. Above will produce API change report file
178 Once official release version is shipped, we need to keep API signature
183 2. Above will produce API signature information file
189 ## Check in API signature data file (ICU4J)
191 Once APIs are frozen for a reference release, we should check in the API
193 API change report.
199 4. You may delete very old versions of the API signature files. Keeping 10
203 change public APIs in maintenance releases. The API signature file for an ICU4J
205 created for the major version, so we can keep track of API changes in
207 API changes although).
213 In ICU4C, we want every (consecutive group of) `@draft` API to be surrounded by
215 sure they don't use unstable API.
254 a) For each of these API status tags, for each API that is tagged with it,
255 verify that the API is surrounded by the appropriate #ifndef..#endif.
259 times. Use one #ifndef..#endif guard per API status and ICU version.
263 U_HIDE_DRAFT_API does not surround (newly) @stable API.
307 Run the ICU4J versus JDK API comparison tool against the target JDK (anything
310 and make sure ICU4J adequately covers the JDK API for the classes we replicate.
314 ## Build API documentation
318 Build the API documentation pages for the new release. Run Doxygen to create the
327 2. Generate the API document pages:<br>
329 3. The generated API docs are in <path>/icu4c/source/doc/html/<br>
356 h. `git commit -m "ICU-<TICKET-NUMBER> Update ICU4C API reference docs for
358 …Example: [ICU-21546 Update ICU4C API reference docs for 69.1](https://github.com/unicode-org/icu-d…
367 …his is also referenced below [Upload API documentations](docs.md#upload-api-documentations) for ho…
372 <https://icu.unicode.org/setup/java/ant#TOC-Building-ICU4J-API-Reference-Document-with-JCite>
374 Build the API documentation pages for the new release:
383 <https://icu.unicode.org/setup/java/ant#TOC-Building-ICU4J-API-Reference-Document-with-JCite>
394 * Then update the live API docs from the generated docs.jar.
396 See [Upload API documentations](docs.md#upload-api-documentations) below for how to make the API do…
398 ### Upload API documentations