E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page History
...
{section} {section}
h1. Bug VS. Improvement VS. New Feature
h1. Bug // Improvement // New Feature // Task
Once in the studio's category, you have the choice between creating a bug entry, an improvement entry or a feature request.
Once in the studio's category, you have the choice between creating a bug report, an improvement report, a feature request or a task.
Pay attention to the kind of entry to create.
...One example of a new feature would be the addition of a new editor in the studio (e.g. for XSLT).
h2. Tasks
A task defines « *a change that does not impact directly the user* ».
One example of a task would be upgrading the version of a parsing library.
A task defines « *a change that does not impact directly the user* ».
One example of a task would be upgrading the version of a parsing library.
h1. Tooling categories
Petals Studio has (for the moment) 3 4 sub-categories in which you can post tickets.
* *Petals Core Tooling* includes all the Petals plug-ins, except those for BPEL and SCA.
* *Petals BPEL Tooling* includes all the plug-ins related to BPEL (creation wizard, sketch export, BPEL Designer, validation...).
* *Petals SCA Tooling* includes all the plug-ins related to SCA (creation wizards, editors, validation...).
* *Petals BPEL Tooling* includes all the plug-ins related to BPEL (creation wizard, sketch export, BPEL Designer, validation...).
* *Petals SCA Tooling* includes all the plug-ins related to SCA (creation wizards, editors, validation...).
* *Studio Product* includes all the plug-ins related to the studio itself (e.g. perspective, welcome page, executable), plus the build mechanism.
When you create a JIRA ticket, pay attention to the category in which this ticket fits.
...