Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Tasks (Buckminster)"

(Items to complete before the 1.0 final release. Completion Q4 2006)
(Items to complete before the 1.0 final release. Completion Q4 2006)
Line 3: Line 3:
 
We're currently working against our Buckminster 0.1.0 Europa release, which will be the first documented & production-quality Buckminster release.  This schedule for this release is synchronized with the milestones and release candidates of [[Europa_Simultaneous_Release#Milestones_and_Release_Candidates|Europa]].
 
We're currently working against our Buckminster 0.1.0 Europa release, which will be the first documented & production-quality Buckminster release.  This schedule for this release is synchronized with the milestones and release candidates of [[Europa_Simultaneous_Release#Milestones_and_Release_Candidates|Europa]].
  
=== Items to complete before the 1.0 final release. Completion Q4 2006 ===
+
=== Items to complete before the 0.1.0 final release. Completion June 21, 2007 ===
  
 
* '''Improve packaging'''
 
* '''Improve packaging'''

Revision as of 04:52, 25 May 2007

< To: Buckminster Project

We're currently working against our Buckminster 0.1.0 Europa release, which will be the first documented & production-quality Buckminster release. This schedule for this release is synchronized with the milestones and release candidates of Europa.

Items to complete before the 0.1.0 final release. Completion June 21, 2007

  • Improve packaging
    • Add common OSS feature (pde, cvs, svn)
    • Create a separate headless-site.xml for the update site
  • PDE Build improvements
    • Feature version consolidation
    • Ability to construct and then use a target platform from a cspec
  • Documentation improvements
    • General restructuring of wiki content
    • Create Trailblazers for common usecases
    • Make current documentation up-to-date with codebase
    • Document the action framework
    • More examples

Misc possibilities - undecided and no timeframe

  • Minimalistic installer
    • Java Web Start installer for our product
    • Able to materialize from bom or mspec
    • Self configuring
    • UI component (progress monitors etc.)

Back to the top