Community
Participate
Working Groups
There are some log files which contain records which are not self contained. Portions of the record need to be stored and then referenced at a later point in time, beyond the lifeline of the current record processing.
Changed component from DataCollection&Control to Exec.logging. (This enhan cment is being tracked in the Execution technology domain, and other GLA enhancements are all under Exec.logging.)
Swapping my i1 & i2 feature work because of dependencies.
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
This feature will require changes to the Parser schema to introduce new fields on the rules. This will impact both the UI and documentation. The GLA Editor needs to be regenerated to reflect the parser schema changes and documentation needs to be written to describe how to use this new feature.
The rules editor regeneration will be completed under bugzilla 89267.
This is being deferred to 4.1 as it could not be contained in 3.3/4.0. Decision approved by owner of requirement and the TPTP Planning Group.
marked so requirements process will review as this has been deferred from 3.3
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
Please set version to 4.2
Theme: Simple to use Justification: Reduces the amount of work for adapter/parser writers because they can create a rules adapter instead of developing a static parser class to handle secondary records.
Reducing priority as requested by IBM AC who asked for this.
Setting target to future so it doesn't show up in 4.2 feature query.
Resolving this as WONTFIX because it is no longer required by the consuming product which requested it.
Closing.
