CAMP 1.2 release plan

[Anish Karmarkar <anish.karmarkar@oracle.com>]

We need to start creating a release plan for CAMP 1.2. To that end I looked at the issues that are current open. If we have time today I would like to go through the issues list, triage, and figure out a tentative target release date.

--Anish

Total: 24 (P1: 5, P2: 13, P3: 6)

Issues in order of priority:

CAMP-200	Extensibility of Attribute Types		Open	Actions
CAMP-209	need a mechanism to retrieve "has a" resources in a single HTTP GET		Open	Actions
CAMP-213	Parameterization of Assembly Instantiation based on contents of Plan		Open	Actions
CAMP-211	Deep serialization		Open	Actions
CAMP-214	Characteristics as Attributes		Open	Actions
CAMP-185	Attribute Types (Numeric)		Open	Actions
CAMP-193	handling of 'sensor_type' attribute of 'sensor resource' is vague		Open	Actions
CAMP-184	Entity Immutability		Open	Actions
CAMP-204	Add external_management_resource to Platform and Assembly		Open	Actions
CAMP-215	sensor resource has no "units" attribute		Open	Actions
CAMP-212	Asynchronous operations		Open	Actions
CAMP-198	select_attr for collections		Open	Actions
CAMP-187	Sort		Open	Actions
CAMP-216	API to get the index of an item within a collection		Open	Actions
CAMP-218	Enumerate use cases wrt external DBs, shared DB, components, services, assemblies and their relationship		Open	Actions
CAMP-219	Section 6.4 is contradictory		Open	Actions
CAMP-217	Use cases for "Row Filtering"		Open	Actions
CAMP-186	Pagination		Open	Actions
CAMP-191	Need a generic mechanism for constraining values of attributes		Open	Actions
CAMP-183	Decouple the Plan Repository from the Platform		Open	Actions
CAMP-208	Hierarchical Platforms		Open	Actions
CAMP-207	Assembly to Assembly bindings		Open	Actions
CAMP-206	Assembly Instantiation Hierarchies		Open	Actions
CAMP-197	User interfaces will need to be internationalized at some future point. Define a consistent approach to presenting user interfaces in multiple languages.		Open