Jump to: navigation, search

Difference between revisions of "Buckminster Project/Buckminster Roadmap"

 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Backlink|Buckminster Project}}
 
{{Backlink|Buckminster Project}}
  
=== Not yet prioritized items to complete before the 1.0 final release. Completion Q4 2006 ===
+
Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals.   Our roadmap for the next 9-12 months appears below.  The roadmap is currently organized thematically, and the project team is currently considering re-factoring the roadmap so that each theme can be advanced in parallel.
  
* Better editors for several basic formats (tentative: use Eclipse Forms)
+
== Release 0.2.0 ==
** [[Buckminster Resource Map|RMAP]] Editor
+
=== Theme: Usability ===
** [[Buckminster Component Specification|CSPEC]] Editor (more generally expressed: a 'Buckminster Component Editor' that is extendable and is the umbrella editor for all component aspects)
+
** [[Buckminster Component Query|CQUERY]] Editor (rewrite of the existing editor to conform to Forms)
+
  
* '''Create Trailblazers for common usecases'''
+
*Graphical editors for the RMAP and CSPEC
* '''Replace metadata persistence mechanism'''
+
**Use EMF for all models (awaits EMF support for generics)
** Use a DB (e.g. Derby) instead of XML
+
**”Form” style editors with Eclipse look and feel
* '''Integrate full Manifest services (checksums etc) into Bill-of-materials'''
+
**Intuitive and with extensive help
* '''General refactoring'''
+
           
** {{Strikeover|Make headless core product much smaller}}
+
*Graphical representation of a Component Model
** Improve separation of concern
+
**Can view a complete model spanning many components
 +
**Should be zoomable
  
=== Misc possibilities - undecided and no timeframe ===
+
*Graphical representation of the resolve process
 +
**Provides feedback to the user during the resolve process
 +
**The graph of chosen paths can be persisted
 +
 
 +
*Standards
 +
**Support for Java Content Repository (JSR170)
 +
 
 +
== Release 0.3.0 ==
 +
=== Theme:  Support for wider range of component models ===
 +
*WAR and EAR recognition
 +
**project models produced by CSPEC actions
 +
**Reuse models supported by Eclipse Web Tools Project
 +
**Target common servers. Tomcat, Jboss, JOnAS
 +
**Commercial servers, such as Websphere, Weblogic, Oracle
 +
*Support for Ivy projects
 +
*Support for Java Modules (JSR277), subject to JSR finalization
 +
 
 +
== Release 0.4.0 ==
 +
=== Theme:  Support for additional languages ===
 +
*PHP/Python/Perl, C
 +
**Repository provider for CPAN
 +
**Support LAMP (Linux Apache MySQL PHP) component stack
 +
   
 +
*Additional component models
 +
**Recognize CDT generated projects
 +
**Perhaps recognize automake/auotconf/configure projects
  
* '''Disconnect headless entirely from Buckminster, possibly offer for general RCP use'''
 
** Turn into article: 'Implementing a headless framework' and 'Implementing a headless progress monitor'
 
 
[[Category:Buckminster]]
 
[[Category:Buckminster]]
 +
[[Category:Buckminster Management]]
 +
[[Category:Buckminster Release]]
 +
[[Category:Buckminster Deprecated]]

Latest revision as of 22:45, 14 February 2009

< To: Buckminster Project

Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals. Our roadmap for the next 9-12 months appears below. The roadmap is currently organized thematically, and the project team is currently considering re-factoring the roadmap so that each theme can be advanced in parallel.

Release 0.2.0

Theme: Usability

  • Graphical editors for the RMAP and CSPEC
    • Use EMF for all models (awaits EMF support for generics)
    • ”Form” style editors with Eclipse look and feel
    • Intuitive and with extensive help
  • Graphical representation of a Component Model
    • Can view a complete model spanning many components
    • Should be zoomable
  • Graphical representation of the resolve process
    • Provides feedback to the user during the resolve process
    • The graph of chosen paths can be persisted
  • Standards
    • Support for Java Content Repository (JSR170)

Release 0.3.0

Theme: Support for wider range of component models

  • WAR and EAR recognition
    • project models produced by CSPEC actions
    • Reuse models supported by Eclipse Web Tools Project
    • Target common servers. Tomcat, Jboss, JOnAS
    • Commercial servers, such as Websphere, Weblogic, Oracle
  • Support for Ivy projects
  • Support for Java Modules (JSR277), subject to JSR finalization

Release 0.4.0

Theme: Support for additional languages

  • PHP/Python/Perl, C
    • Repository provider for CPAN
    • Support LAMP (Linux Apache MySQL PHP) component stack
  • Additional component models
    • Recognize CDT generated projects
    • Perhaps recognize automake/auotconf/configure projects