*****************************************************************
*								*
*			    BUGGER V2				*
*			Planned Features for V1			*
*								*
*		       Document Date: 23 May 2011		*
*								*
*****************************************************************


Background
-----------

The previous incarnation of BUGGER is currently online in a readonly
state. Whilst this is sufficient to ensure continued access to old
records, the updating and maintaing of projects is currently impossible.


It's therefore important to release a version of BUGGER as soon as 
possible (security and bugs allowing).

It would be unrealistic to attempt to acheive both an early release date
and full replication of BUGGERs original features.

As BUGGER V2 is entirely database based, it should be reasonably simple
to apply patches and major changes to the interface without requiring
re-configuration by users.

This document is intended to detail the features BUGGER should have
before Release 1.




Features Currently Implemented
--------------------------------


- Project Summary Pages
- Release viewing/recording
- Document viewing/recording
- License association with Release/Documentation
- Viewing of licenses
- Bug viewing (partial)
- User Addition
- Authentication framework
- Site display settings (hide bugs/documents/releases etc.)




TODO
-----

- Add new project
- Edit/delete users
- Changelogs
- Page headings
- Bugs





Notes
------

Bug support is currently only partially implemented. The bugview
page is a proof of concept and needs correctly formatting. There is
currently no mechanism for a user to report a bug






Feature Deferral
----------------


The following features should be deferred to Release 2, or an intermediate
release


- Bug comments (including CAPTCHA)
- Feature Requests
- TODO lists
- Screen shots
- "Remember Me" feature on login
- Auto-updates interface
- License management (for proprietary code)
- Template support




Other features may be added to Rel 2, but in order for efficient 
project management to resume, Rel 1 should be made available as soon
as possible without forsaking security.



*****************************************************************
*								*
*			DOCUMENT END				*
*								*
*****************************************************************