Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

This classification is more suitable for items in thier early stage of formation not yet mature enough to be labelled as a 'Task' or 'New Feature'.

It provides a bucket where thoughts and ideas from interested parties can be recorded as the discussion and exchange of ideas progresses.

For instance, if we were contemplating moving the Flume NG source code to a new version control system; before classifying it as a 'Task', a 'Brainstorming' issue could be created to track thoughts from committers, users and PMC members.

Once a resolution is made, then a Task can be created with all the details defined during the brainstorming exercise.

...

Logic errors, out-of-memory errors, memory leaks, run-time errors, failure of the product to perform as expected and any other unexpected or unwanted behavior can be registed as registered as Bugs.

Missing, incorrect or insufficient documentation on wiki pages, api javadocs and guides should be classified as Documentation issues rather than Bugs.

Dependency Upgrade

This is a Task that relates directly to the upgrade of a dependency to a more recent or newer version.

...

The documenation/information can be provided in the form of Javadocs (directly in the source code), on the FLUME wiki pages or by updating the FLUME websiteuser and developer guides.

Epic

This is an Agile software development terminology that describes a group of closely related user stories.

...

These types of requests would typically be entered as infrastructure requests under INFRA rather than issues within the FLUME project.

...

As part of the voting process, this is necessary when there is a need to execute a commit policy which requires that changes to the source code receive consensus approval in order to be committed to the version control system. Before opening such issues, there should be a discussion within the developer mailing list.

Story

A user story is an agile software development terminology that comprises of one or more sentences that captures features or behaviors a developer or end user of the product expects or would like to see in the product.

...

Suitable Name Search

This classification is can be used for a brainstorming exercise that is more specifically geared towards a search for a suitable name for an Apache product.

...