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 "ATF/ATFPubPlanMinutes2009.06.04"

< ATF
(New page: == Attendees == Nick Boldt - RedHat Michael Spector - Zend Technologies Koen Aers - RedHat Roy Ganor - Zend Technologies == Proposed Continuation Review == Continuation review is avail...)
 
(Moving the project under Tools top-level project)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
 
== Attendees ==
 
== Attendees ==
Nick Boldt - RedHat
+
* Nick Boldt - RedHat
Michael Spector  - Zend Technologies  
+
* Michael Spector  - Zend Technologies  
Koen Aers - RedHat
+
* Koen Aers - RedHat
Roy Ganor - Zend Technologies
+
* Roy Ganor - Zend Technologies (organizer)
 
+
== Proposed Continuation Review ==
+
Continuation review is available at http://docs.google.com/Edit?id=dwx337f_84ch57sbfq
+
  
 
== Moving the project under Tools top-level project ==
 
== Moving the project under Tools top-level project ==
We propose to move the project from the Web Tools top-level project into the Tools top-level project. The move will stir up visibility to the Ajax tools. The Tools top-level project is also a natural place for tooling projects such as PHP Development Tools (PDT), AJDT, C/C++ Tools.
+
* We propose to move the project from the Web Tools top-level project into the Tools top-level project. The move will stir up visibility to the Ajax tools. The Tools top-level project is also a natural place for tooling projects such as PHP Development Tools (PDT), AJDT, C/C++ Tools.
 +
 
 +
* All four attendees voted +1
  
 
== The four phases plan ==
 
== The four phases plan ==
 
Four phases to revive the community:
 
Four phases to revive the community:
  
Phase 1 Plan:
+
* Phase 1 Plan:
- Build up the infrastructure needed for collaborative community under the Tools top-project.  
+
** Build up the infrastructure needed for collaborative community under the Tools top-project.  
- Automate the build process for the ATF project so people can be updated on our work.
+
** Automate the build process for the ATF project so people can be updated on our work.
- Align the code base to the latest Eclipse stream (Galileo)
+
** Align the code base to the latest Eclipse stream (Galileo)
- define the minimal set of features that are needed in order to run this project
+
** define the minimal set of features that are needed in order to run this project
  
Phase 2 Plan:
+
* Phase 2 Plan:
- stabilization, key bug fixing
+
** stabilization, key bug fixing
- add "eval source" debugger support
+
** add "eval source" debugger support
- introduce key experimental APIs and extensions points
+
** introduce key experimental APIs and extensions points
- packaging and integration with browser (and XULRunner) (pending IP review)
+
** packaging and integration with browser (and XULRunner) (pending IP review)
  
Phase 3 Plan:
+
* Phase 3 Plan:
- strengthen core
+
** strengthen core
- support for latest Firefox/Xulrunner versions (technical + IP review)
+
** support for latest Firefox/Xulrunner versions (technical + IP review)
- early cross server-side/client-side JavaScript debugging
+
** early cross server-side/client-side JavaScript debugging
- formalize build/test cycle
+
** formalize build/test cycle
  
Phase 4 Plan: Incubation Exit requirements
+
* Phase 4 Plan: Incubation Exit requirements
- NLS support, string externalization
+
** NLS support, string externalization
- Documentation
+
** Documentation
- API documentation
+
** API documentation
- Determine internal/external classes. Rename packages.
+
** Determine internal/external classes. Rename packages.
- Remove unneeded dependencies, General cleanup of code
+
** Remove unneeded dependencies, General cleanup of code
- Formalize APIs and Extension points
+
** Formalize APIs and Extension points
- Test plans and JUnit test.
+
** Test plans and JUnit test.
- Conform to next release milestone release plan
+
** Conform to next release milestone release plan
- Review bug
+
** Review bug
- Graduation Review/Requirements
+
** Graduation Review/Requirements
 +
 
 +
 
 +
== Proposed Continuation Review ==
 +
Continuation review is available at http://docs.google.com/Doc?id=dwx337f_84ch57sbfq

Latest revision as of 06:00, 6 June 2009

Attendees

  • Nick Boldt - RedHat
  • Michael Spector - Zend Technologies
  • Koen Aers - RedHat
  • Roy Ganor - Zend Technologies (organizer)

Moving the project under Tools top-level project

  • We propose to move the project from the Web Tools top-level project into the Tools top-level project. The move will stir up visibility to the Ajax tools. The Tools top-level project is also a natural place for tooling projects such as PHP Development Tools (PDT), AJDT, C/C++ Tools.
  • All four attendees voted +1

The four phases plan

Four phases to revive the community:

  • Phase 1 Plan:
    • Build up the infrastructure needed for collaborative community under the Tools top-project.
    • Automate the build process for the ATF project so people can be updated on our work.
    • Align the code base to the latest Eclipse stream (Galileo)
    • define the minimal set of features that are needed in order to run this project
  • Phase 2 Plan:
    • stabilization, key bug fixing
    • add "eval source" debugger support
    • introduce key experimental APIs and extensions points
    • packaging and integration with browser (and XULRunner) (pending IP review)
  • Phase 3 Plan:
    • strengthen core
    • support for latest Firefox/Xulrunner versions (technical + IP review)
    • early cross server-side/client-side JavaScript debugging
    • formalize build/test cycle
  • Phase 4 Plan: Incubation Exit requirements
    • NLS support, string externalization
    • Documentation
    • API documentation
    • Determine internal/external classes. Rename packages.
    • Remove unneeded dependencies, General cleanup of code
    • Formalize APIs and Extension points
    • Test plans and JUnit test.
    • Conform to next release milestone release plan
    • Review bug
    • Graduation Review/Requirements


Proposed Continuation Review

Continuation review is available at http://docs.google.com/Doc?id=dwx337f_84ch57sbfq

Back to the top