Below are the features/changes/fixes need to be done in the 1.0 release
of the Registry (as we discussed in today's meetings with Dr. Sanjiva,
Paul, Glen and Jonathan).
Core Registry
==========
* Add import method to the Registry interface to import resources using
URLs.
* Split the Registry interface to a MinimalRegistry and Registry
* Add "boolean tagExists(String resourcePath, String tag)" to the
Registry interface (this is requested by the Mashup team)
* Registry interface method to search resource by media type.
* Change put(...) method to take the suggested path and return the
actual path.
* Implement resource renaming (This may take lot of time and may extend
beyond the 11th deadline)
* Fix resource put protocol in APP. Use HEAD to check whether the
resource exists. Then use POST if resource does not exist. Use PUT if
the resource already exists.
* Fix some minor protocol issues in the APP interface to match with the
protocol defined in the wiki.
Web UI
======
* Functionality for browsing, adding and editing properties of resources
* Provide tagging box with add resource / add collection UIs
* Make the resource name and media type fields disabled. And provide
buttons next to them to edit them.
* UI for searching resources by media type
* Auto complete for taggings - optional
In addition to above we have 73 open JIRAs to resolve (many of them are
trivial, but some may take lot of time). So I think we can follow below
plan for achieving our goal of releasing Registry 1.0 on 28th January.
9th to 11th - Complete all core Registry features (we have to allocate
time for meetings as well)
11th to 18th - Complete UI features + work on JIRAs
18th to 27th - QA + work on JIRAs
Please add any missing features or remove unnecessary features from
above lists.
Thanks,
Chathura
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
