Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316485 - [API] should define a clear API policy
Summary: [API] should define a clear API policy
Status: CLOSED FIXED
Alias: None
Product: EEF
Classification: Modeling
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: EEF Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 11:33 EDT by Bouchet Stéphane CLA
Modified: 2016-05-30 11:06 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bouchet Stéphane CLA 2010-06-10 11:33:08 EDT 
Typically would include how 'APIs' are distinguished from non-API and 'provisional' API, if any. It is recommended that non-API be marked with x-internal in the bundles manifest. Also, should include what the commitment is to API, how long maintained after deprecated, etc.
Comment 1 Bouchet Stéphane CLA 2010-06-25 03:47:55 EDT 
take example on acceleo : 

http://wiki.eclipse.org/Acceleo/API_Policy
Comment 2 Stephane Begaudeau CLA 2016-05-30 11:06:51 EDT 
This issue has been fixed in the new runtime.