Difference between revisions of "Development Status"

From Covecube - Wiki
(33 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
== Development Workflow ==
 
== Development Workflow ==
 
Our workflow for implementing feature requests and fixing bugs works like this:
 
Our workflow for implementing feature requests and fixing bugs works like this:
* Users contact us with issues using our [http://stablebit.com/contact contact us page.]
+
* You can contact us with any issues or feature requests using our [http://stablebit.com/contact contact us page.]
* The contact request is forwarded to the appropriate department and a human replies to the contact request.
+
* One of our support personnel will reply to the contact request.
* If the problem requires additional assistance, an Issue Analysis Request (IAR) is sent to another department (such as Software Development, Sales, etc...).
+
* If the problem requires additional work, an ''Issue'' request is sent to another department (such as Software Development or Sales).
* IARs can turn into Code Change Requests (CCR) if the issue is a bug that's confirmed or a feature request that's approved.
+
* Issues can then turn into ''Code Change'' requests, if the department head deems that it's necessary.
* Meanwhile, while this is all happening in the background the user gets feedback on the status of their IAR / CCR on their contact request page and continues to interact with Technical Support.
+
* Meanwhile, while this is all happening, you get feedback on the status of your ''Issue'' or ''Code Change'' on your contact request page.
 +
* You can also see the status of all the pending ''Code Changes'' below.
  
Here is the current status of this system:
+
=== Code Changes ===
  
 
{{#widget:Iframe
 
{{#widget:Iframe
Line 20: Line 21:
 
}}
 
}}
  
== StableBit ==
+
== Future Products ==
=== StableBit DrivePool 1.X ===
+
In addition to the regular ''Code Changes'' above, here are the things that we're working on in the long term:
No new features are planned for this version, however bug fixes will be applied for any confirmed issues.
 
  
=== StableBit DrivePool 2.X ===
+
=== StableBit CloudDrive ===
 +
'''Status: Release Candidate'''
  
==== Currently in Development ====
+
This product is available as a release candidate. Please take a look at it! A final release is expected to be made available soon.
  
===== Action Feedback UI =====
+
* [https://stablebit.com/CloudDrive StableBit CloudDrive]
'''Completion estimate: 0%'''
+
* [http://blog.covecube.com/ Covecube Blog]
  
* Certain actions should generate user feedback of various importance:
+
=== StableBit FileVault ===
** Damaged drive removed, but some files were not moved. User should be notified of which files were not removed.
+
'''Status: (future)'''
** Drive removal aborted due to files in use, and user chose not to automatically close applications using those file. Use should be notified of which files are in use and by what applications.
 
** User should be able to see when the last balancing / background duplication pass took place and how long each took.
 
** If an incomplete file is discovered on the pool, user should be notified which file and what corrective actions were taken.
 
** All errors to actions, such as an error adding a drive to the pool or creating a new pool should be displayed in the action feedback UI.
 
  
===== Add Pool Parts from Virtual Volumes =====
+
StableBit FileVault is planned to deal with data integrity and file protection, and will fit well into our existing line of StableBit products.
'''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.
+
Top level features:
 +
* Indexing of your data for enhanced statistics and data integrity verification.
 +
* Kernel-level protection of your data from accidental modification by applications or users.
 +
* Reporting and auditing of your data.
  
==== Planned for Future Implementation ====
+
=== StableBit.Me ===
 +
'''Status: (future)'''
  
===== Per-folder Balancing Rules =====
+
* A simple and secure locally hosted solution to create your own cloud that is accessible from anywhere on the Internet or locally.
You should be able to limit file placement to a set of pool parts based on the path name.
+
* You will be able to use a StableBit CloudDrive drive or a StableBit DrivePool drive to host your data, or even a non-StableBit drive.
  
===== Drive Removal Improvements =====
+
=== StableBit Cloud ===
Drive removal should have more flexible options in terms of:
+
'''Status: (future)'''
* 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.
 
* Inform the user what files were skipped after forcing damaged drive removal.
 
  
===== Better Management of Running Out of Disk Space =====
+
The StableBit Cloud is going to be a new online service part of the StableBit brand.
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 ===
+
It's going to have these goals:
No new features are planned for this version, however bug fixes will be applied for any confirmed issues.
+
* One secure place online where you can go to see the status of your StableBit products.
 +
* Extensive centralized notifications that can be configured in one place.
 +
* Simple and responsive styling that can adapt to different sized screens.
  
=== StableBit Scanner 2.X ===
+
''The StableBit Cloud is planned to supersede BitFlock, which will be retired when the StableBit Cloud becomes available.''
==== Deeper BitFlock integration ====
 
'''Completion estimate: 20%'''
 
  
Expect to see much deeper and more functional BitFlock integration in the future, in particular:
+
=== StableBit PowerGrid ===
* More metadata about drives from the manufacturer spec sheets integrated with the SMART interpretation system.
+
'''Status: (concept)'''
** 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 ====
+
StableBit PowerGrid is going to be an Uninterruptable Power Supply (UPS) management software that will tie into the StableBit Cloud giving your insight into the power situation at any of your sites running our software.
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 ====
+
This software product has no release timeframe at this point.
The UI needs to be refined for better usability.
 
* You should be able to copy / paste data from the drive details window.
 
* There should be an option to view detailed chkdsk results after fixing a file system.
 
* There should be a way to list disks that we've seen before, but are not currently connected to the system.
 
* ''Potential: Have a wire frame view of the disks.''
 
 
 
==== 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.
 

Revision as of 18:18, 23 March 2017

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.

Development Workflow

Our workflow for implementing feature requests and fixing bugs works like this:

  • You can contact us with any issues or feature requests using our contact us page.
  • One of our support personnel will reply to the contact request.
  • If the problem requires additional work, an Issue request is sent to another department (such as Software Development or Sales).
  • Issues can then turn into Code Change requests, if the department head deems that it's necessary.
  • Meanwhile, while this is all happening, you get feedback on the status of your Issue or Code Change on your contact request page.
  • You can also see the status of all the pending Code Changes below.

Code Changes

Future Products

In addition to the regular Code Changes above, here are the things that we're working on in the long term:

StableBit CloudDrive

Status: Release Candidate

This product is available as a release candidate. Please take a look at it! A final release is expected to be made available soon.

StableBit FileVault

Status: (future)

StableBit FileVault is planned to deal with data integrity and file protection, and will fit well into our existing line of StableBit products.

Top level features:

  • Indexing of your data for enhanced statistics and data integrity verification.
  • Kernel-level protection of your data from accidental modification by applications or users.
  • Reporting and auditing of your data.

StableBit.Me

Status: (future)

  • A simple and secure locally hosted solution to create your own cloud that is accessible from anywhere on the Internet or locally.
  • You will be able to use a StableBit CloudDrive drive or a StableBit DrivePool drive to host your data, or even a non-StableBit drive.

StableBit Cloud

Status: (future)

The StableBit Cloud is going to be a new online service part of the StableBit brand.

It's going to have these goals:

  • One secure place online where you can go to see the status of your StableBit products.
  • Extensive centralized notifications that can be configured in one place.
  • Simple and responsive styling that can adapt to different sized screens.

The StableBit Cloud is planned to supersede BitFlock, which will be retired when the StableBit Cloud becomes available.

StableBit PowerGrid

Status: (concept)

StableBit PowerGrid is going to be an Uninterruptable Power Supply (UPS) management software that will tie into the StableBit Cloud giving your insight into the power situation at any of your sites running our software.

This software product has no release timeframe at this point.