Well defined project plan
Using the Jira issue tracker, WET tracks all its bugs, feature
requests and tasks. These are constantly being monitored and
maintained by the project leader. Based on the criticality /impact
of the issue, these are then prioritized and assigned a fix
Before making a release, all issues that were planned to be fixed
for that release must have been fixed or reprioritized for a future
version with a valid explanation about why the issue is not very
important to fix for this version. After all these conditions are
satisfied, the build goes through a round of testing before being
A question that is often asked when it comes to picking opensource
software is "How active is the development of this project?" Are bugs
being fixed ? Are new features being developed at all? Does the
project follow any process at all?
One common concern about opensource software is that the application
was released to the community by some developers who worked when they
were 'between jobs'. Eventually the developer found a job elsewhere
and as a result there is nobody to take care of the software. Or the
developers of the software work in their free time and maintain the
software when they have time, without a planned or structured approach.
To demythify, think of some of the most succesful opensource projects
- Linux, Apache, Sipfoundry and many more. These not only have a well
defined project plan, but also, in many cases, their plans are far more
structured and transaparent when compared to their commercial
When it comes to WET, we have a very structured and planned process and
a dedicated team of developers and testers working exclusively on WET.
We'd like to extend our thanks to Thwameva Technologies for extending their financial
support which makes this possible.
Note: This page has not yet been updated for the 1.0 release. This will be updated after the final release of 1.0