International Components for Unicode
| About ICU |
| · ICU Home |
| · Download ICU |
| Demos & Tools |
| · ICU4C Demos |
| · ICU4J Demos |
| · Data Customizer |
| Documents |
| · User Guide |
| · FAQ |
| · ICU4J FAQ |
| · Docs & Papers |
| API References |
| · ICU4C |
| · ICU4J |
| Data & Charts |
| · Conversion Tables |
| · Feature Comparisons |
| · Performance & Size |
| Development |
| · Project Information |
| · Source Repository |
| · Processes |
| · Members-Only Area |
| Bugs & Contacts |
| · Mailing Lists/Contacts |
| · Bugs & Features |
ICU Processes and Procedures
Ticket Life Cycle
Here is a description the life cycle of an ICU Trac ticket, a feature request or a bug report, from initial submittal through implementation and review to release.
Feature Proposals and Design
All API design proposals must be proposed on the icu-design mailing list. The proposal should contain the proposed API signature, and a deadline for comments (usually one week from proposal). Background information in the proposal can be helpful if the topic is complex.
ICU Coding Style Guidelines
The ICU coding guidelines are described in the user guide at http://icu-project.org/userguide/conventions.html
ICU Release Process
The release task list contains the list of things to complete when releasing a a new version of the ICU libraries.
Design Documents
Design Documents for various ICU services are maintained in the SubVersion repository, and can be browsed from this location: http://source.icu-project.org/repos/icu/icuhtml/trunk/design/