en | Github Issue Tracker

Looking for help? Please visit the help resources and discuss your idea or problem on the forum before opening an issue.

The github issue tracker allows KeeFox developers to keep track of planned feature development, bug fixes and other tasks.

Each issue can have one or more labels attached. "enhancement", "bug" and "task" should be self-explanatory; others are explained in sections below.

Closed issues

A closed issue with no label other than the three mentioned above is considered "finished" - it has been implemented, tested and deployed (or will be deployed with the next version of KeeFox). That doesn't mean there are no bugs but normally we'd create a new issue for a bug associated with a "finished" issue.

Other reasons for an issue to be closed are: "invalid" - This could mean many things. E.g. it's not a real bug or enhancement request, there is not enough information to define the issue well enough to act upon it, other changes have made it obsolete, etc.

"wontfix" - For some reason (usually explained in the issue comments) we've decided to not implement the change requested in this issue. Such a state is not a permanent ban on the enhancement or bug fix but it's a good indication that we don't feel that our limited development time should be spent on this particular issue in the foreseeable future.

"duplicate" - The underlying request or problem is already covered by an existing issue.

Open issues

An open issue is one that we have not yet had time to implement. For new issues it's possible that we've just not yet had time to assess the issue and make a decision about how to procede.

You can see what each developer is working on by looking at the issues that are assigned to them. Depending on the scope of the issue, a developer may be working on it for hours, days or even months.

Milestones

Each open issue may have a milestone attached to it. These give an indication (but by no means a guarantee) of when we expect a particular issue to be finished.

Two numbered issues (at time of writing: 1.2 and 1.3) group together those issues that we intend to work on for the next release and the one after.

The "future" milestone indicates that we want to implement this feature soon but that it is far enough down the list of priorities that it is unlikely to be implemented in the next couple of versions of KeeFox.

If there is no milestone this implies that we may implement the feature one day but a major concern is keeping us from committing to it at the moment (e.g. unclear security or privacy implications, limitations of current technology, size of task makes it unlikely we could find time to implement it, etc.)

Note

The issues have been imported from the old Trac ticket system on Sourceforge so there are a number of anomalies but if you read the comments in the tickets you should be able to make sense of them.