Difference between revisions of "Development Status"

From Covecube - Wiki
Line 53: Line 53:
 
==== Add Option to Ignore Existing Unreadable Sectors ====
 
==== Add Option to Ignore Existing Unreadable Sectors ====
 
Give the option to ignore existing unreadable sectors, just like we have the option to ignore current SMART warnings. This can be useful if the user chooses to continue using a drive that is showing unreadable sectors. For example, while not recommended, the user can choose to continue using a damaged drive if no user data was harmed by the unreadable sector.
 
Give the option to ignore existing unreadable sectors, just like we have the option to ignore current SMART warnings. This can be useful if the user chooses to continue using a drive that is showing unreadable sectors. For example, while not recommended, the user can choose to continue using a damaged drive if no user data was harmed by the unreadable sector.
 +
* Add an explanation on what an unreadable sector really is, in plain english.
  
 
==== UI Usability ====
 
==== UI Usability ====

Revision as of 20:48, 2 February 2014

This page lists features that are either planned for future implementation or are currently in development. Planned features are subject to change.

You can contact us at any time to report issues or request new features to be implemented.

Issue Analysis Requests

In addition to implementing new features we have an internal system for tracking potential issues (we call these IARs) which can turn into bugs once confirmed. Bug fixes are rolled into future internal BETAs and the IAR # is noted in the change log.

IARs are managed by technical support @ stablebit.com. To report an issue you can contact us at any time.

StableBit

StableBit DrivePool 1.X

No new features are planned for this version, however bug fixes will be applied for any confirmed issues.

StableBit DrivePool 2.X

Currently in Development

Add Pool Parts from Virtual Volumes

Completion estimate: 50%

This has been requested often. One example of a volume that doesn't reside on a physical drive is a mounted TrueCrypt volume.

Planned for Future Implementation

Per-folder Balancing Rules

You should be able to limit file placement to a set of pool parts based on the path name.

Drive Removal Improvements

Drive removal should have more flexible options in terms of:

  • Optionally, automatically closing handles to files that are in-use on the pool part being removed.
  • Optionally, automatically restarting services / applications that have files open on the pool part being removed.
Better Management of Running Out of Disk Space

When an existing file cannot expand due to running out of disk space on some particular pool part, instead of returning the out of disk space error, we should force an immediate and quick re-balance in order to free up the disk space required for the file expansion and allow the expansion to go forward uninterrupted.

StableBit Scanner 1.X

No new features are planned for this version, however bug fixes will be applied for any confirmed issues.

StableBit Scanner 2.X

Deeper BitFlock integration

Completion estimate: 20%

Expect to see much deeper and more functional BitFlock integration in the future, in particular:

  • More metadata about drives from the manufacturer spec sheets integrated with the SMART interpretation system.
    • Maximum operating temperatures, per model.
    • Maximum load / unload cycles, per model.
    • Warranty time period for your model.
    • Links to the manufacturer's web site and RMA request pages.
  • Enhanced SMART interpretation using aggregated statistics for your drive model.
    • Your drive age will be compared to other drives in the system of the same model giving you a better idea of how often your model fails.
  • Create password protected BitFlock nests containing your SMART data, right from the StableBit Scanner UI.

Add Option to Ignore Existing Unreadable Sectors

Give the option to ignore existing unreadable sectors, just like we have the option to ignore current SMART warnings. This can be useful if the user chooses to continue using a drive that is showing unreadable sectors. For example, while not recommended, the user can choose to continue using a damaged drive if no user data was harmed by the unreadable sector.

  • Add an explanation on what an unreadable sector really is, in plain english.

UI Usability

The UI needs to be refined for better usability. For example, you should be able to copy / paste data from the drive details window.

Reporting

You should have the ability to print out detailed drive health reports digitally signed by us.

Product 3

Completion estimate: 25%

Product 3 has not been revealed yet. It will run on the Microsoft Windows family of Operating Systems and will consist of:

  • 2 kernel drivers.
  • A system service.
  • A user interface.

BitFlock

StableBit Scanner Changes

Completion estimate: 50%

Changes related to the forthcoming tighter StableBit Scanner integration:

  • Password protected nests.
  • A clean REST API for posting updates and querying for information.
  • Keep track of SMART statistics as they change over time.

Responsive Design

  • BitFlock should look good on all devices of varying screen sizes.

Drive Health Statistics

  • Show aggregate useful drive health statistics for each drive model.