Skip to main content
Jump to: navigation, search

Difference between revisions of "Epsilon/Agenda"

Line 7: Line 7:
 
** EWL-GMF binding: expose a variable for referring to GMF notation model (Louis and Dimitris to investigate)
 
** EWL-GMF binding: expose a variable for referring to GMF notation model (Louis and Dimitris to investigate)
 
** More fine-grained traceability in EGL (Antonio and Louis to exchange solutions, Louis to investigate operations that receive the full AST as argument - see select operation)
 
** More fine-grained traceability in EGL (Antonio and Louis to exchange solutions, Louis to investigate operations that receive the full AST as argument - see select operation)
* Go through the Epsilon bug reports
+
* Go through the Epsilon bug reports (Deferred)
 
* Put a link to the Epsilon wiki in the Epsilon website (Dimitris)
 
* Put a link to the Epsilon wiki in the Epsilon website (Dimitris)
 
* Do the SVN keyword thing in the bugzilla (Dimitris)
 
* Do the SVN keyword thing in the bugzilla (Dimitris)

Revision as of 04:33, 24 May 2011

  • Analyse the performance of Epsilon using TPTP
  • Document the Eclipse.org specific files (project plan etc)
  • Document the building/uploading process
  • Add missing copyright notices in the code
  • Prepare docuware for move from GMT to EMFT
  • Briefly discuss some features needed for INESS / MADES:
    • EWL-GMF binding: expose a variable for referring to GMF notation model (Louis and Dimitris to investigate)
    • More fine-grained traceability in EGL (Antonio and Louis to exchange solutions, Louis to investigate operations that receive the full AST as argument - see select operation)
  • Go through the Epsilon bug reports (Deferred)
  • Put a link to the Epsilon wiki in the Epsilon website (Dimitris)
  • Do the SVN keyword thing in the bugzilla (Dimitris)
    • Email Louis and Antonio when done
  • Document bug lifecycle in the bugzilla (flags, keywords) (Dimitris)
  • Write the section on EOL literals (Antonio)

Back to the top