Page History

...

Please feel free to list features / contributions you plan to develop for 4.0.  You can also add a JIRA ticket and mark it for "4.0" which will put it on the automated list below (see "Tickets & actual codePossible JIRA tickets to resolve")

Conceptual Ideas / Proposals

• Metadata for All Objects: In the Developers Meeting on Jan 30, 2013, those in attendance discussed a need to release an updated version of this "Metadata for All" pull request (#12).  However, we may need the following:
  
  • An updated version of the pull request based on current "master"
  • We like the suggestion to rename "schemas" to "namespaces"
  • We'd like it to use "metadatavalue" (and similar) tables rather than creating a new set of Metadata tables specific to other objects.   We understand this may be more disruptive, but it seems odd to have different metadata namespaces
  • If possible we'd want this change to be "backwards compatible" with existing UIs. The goal would be to perform this change in stages – first update the APIs to allow for metadata on all objects, then update each UI one-by-one.  Hopefully we can get all of the UIs done before 4.0
  • We also obviously could use some basic documentation / overview of the thinking behind it, so that we can vote this through sooner rather than later.

Possible JIRA tickets

...

to resolve (automated list)

This is the list of JIRA tickets ("New Features" and Improvements) currently scheduled for 4.0.  There is no guarantee they will all be completed in time for 4.0 release, and tickets may be dropped/added to the list at any time. But, if you'd like to volunteer to help with one, please let us know by attaching a comment to the ticket in question.

...