[Mydatabasepilot-cvs] Docs RoadMap.html,NONE,1.1
Status: Alpha
Brought to you by:
nanoface
Menu
▾
▴
[Mydatabasepilot-cvs] Docs RoadMap.html,NONE,1.1
|
From: <nan...@us...> - 2003-04-12 02:39:04
|
Update of /cvsroot/mydatabasepilot/Docs In directory sc8-pr-cvs1:/tmp/cvs-serv19299 Added Files: RoadMap.html Log Message: New File Added: RoadMap.html --- NEW FILE: RoadMap.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>MyDatabase Pilot Docs - DEVELOPMENT PLAN - Road Map</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> </head> <body> <div style="font-size: 24px;font-weight: bold;color: #003399; background-color: #FFFFCC; text-align: center; margin: 3px 0px;">DEVELOPMENT PLAN<br>Road Map</div> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">Scope: What is this all about?</div> <p style="text-align: justify;">MyDatabase Pilot will be developed to a mature product. This will be accomplished in a series of small planned steps. This road map shows the path to maturity as envisioned at the start of this journey. The road map is subject to change as new features are identified and/or requested, and as needed to accommodate our growing audience.</p> <p style="text-align: justify;">First we need to qualify a few words/phrases. This document starts with some definitions and explanations of development lingo as it applies to MyDatabase Pilot. These definitions will help you answer questions like: What do we mean when we declare a MyDatabase Pilot release as "Alpha" or "Stable"? What does v0.9.22 mean? What branch/version is right for me?</p> <p style="text-align: justify;">At the end of this document is the actual road map, which gives you an idea of what to expect at certain stages. As mentioned before, this is somewhat like looking through the crystal ball. The further you look into the future, the fuzzier things get. So changes/updates to this map are very likely, and are more likely the further down this path we travel.</p> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">Development Status: What the stages mean</div> <p style="text-align: justify;">Each release of MyDatabase Pilot will be labeled with one of five status identifiers. They are Alpha, Beta, Gamma, Stable, and Mature. Two other status identifiers will be used from time to time; however these will not be associated with any file releases. These identifiers are Planning, and Development.</p> <ul> <li><span style="font-weight: bold; color: #003399;">Pre-Release Status Identifiers:</span></li> <ul> <li style="text-align: justify;"><span style="font-weight:bold;">Planning</span> - A version of MyDatabase Pilot is said to be in <span style="font-weight:bold;">Planning</span> stage when a full development plan has not yet been completed, and is currently being laid out.</li> <li style="text-align: justify;"><span style="font-weight:bold;">Development</span> - Some developers refer to this stage as <span style="font-weight:bold;">Pre-Alpha</span>. We will refer to code that has yet to be released, as code of status <span style="font-weight:bold;">Development</span>. This code will be available through the CVS.</li> </ul> <li><span style="font-weight: bold; color: #003399;">Release Status Identifiers:</span></li> <ul> <li style="text-align: justify;"><span style="font-weight:bold;">Alpha</span> - A release will be named <span style="font-weight:bold;">Alpha</span> when a significant portion of the software plan is yet to be developed and tested. These releases will be made available only to show-case the latest snap-shot of development code, and should give an idea of some new features that are expected in the stable release.</li> <li style="text-align: justify;"><span style="font-weight:bold;">Beta</span> - Once ALL major features in the development plan have been implemented, the software will be labeled <span style="font-weight:bold;">Beta</span>. At this point extensive and documented testing will begin. No new major features will be introduced. Any new major features will have to be added to a new branch and labeled either Development or Alpha. A <span style="font-weight:bold;">Beta</span> release will show-case a product that is considered complete according to the plan, but untested. Unexpected results can still happen, and should be considered before working on mission critical data. (Make sure you have a backup)</li> <li style="text-align: justify;"><span style="font-weight:bold;">Gamma</span> - When all scheduled testing has been completed and documented, the product will be declared <span style="font-weight:bold;">Gamma</span>. At this point we believe the product is fully developed and tested in the lab according to the development plan. However the product is unproven in the field. A product will remain in <span style="font-weight:bold;">Gamma</span> state for a period of at least three months. This will give us a chance to collect user feed back. We may have missed a few bugs here and there. We may have overlooked/omitted something significant in the development plan. A <span style="font-weight:bold;">Gamma</span> release will show-case a product that is considered complete according to the plan and tested in the lab according to our testing standards. We do not expect any major problems (although it can't be ruled out), but there may be a few user issues that we may have overlooked.</li> <li style="text-align: justify;"><span style="font-weight:bold;">Stable</span> - If no major bugs or shortcomings are reported in a Gamma release for a period of three months, the product will be released as <span style="font-weight:bold;">Stable</span>. Some developers refer to this as <span style="font-weight:bold;">Production</span>. <span style="font-weight:bold;">Stable</span> release is considered complete, tested, and verified in the field. You can use this release with confidence, however no warranty is provided as according to the GNU license.</li> <li style="text-align: justify;"><span style="font-weight:bold;">Mature</span> - This designation will be assigned to branches of MyDatabase Pilot that have been well established. Based on number of downloads, and number of reported bugs. The exact download numbers will be left to the discretion of the team, but it will have to be a reasonably significant number. No major bugs for at least a year, before <span style="font-weight:bold;">Mature</span> status can be awarded to a branch.</li> </ul> </ul> <p style="text-align: justify;">A particular release can be considered both in Planning and in Development Status/Alpha release. Even though a plan is still unrefined, some developers may already have experimented with some code that represents a portion of the development plan which has been finalized. Similarly this development code may be made available via an Alpha release in order to show some of our current plans.</p> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">Versioning: What the Numbers Mean</div> <p style="text-align: justify;">The nomenclature of MyDatabase Pilot versioning will be straight forward. Each release will have three sets of numbers and one letter such as 0.7.0.a.</p> <p style="text-align: justify;">The letter identifies the status of the release; a for Alpha, b for Beta, g for Gamma, s for Stable, and m for Mature.</p> <p style="text-align: justify;">The first number represents the Major releases/branches of MyDatabase Pilot. This number will remain 0 until our first stable release. Our first stable release will be identified as 1.0.0.s. New branches of MyDatabase Pilot with new major functionality/improvements will subsequently increment the first number. This is true even with the first alpha release of a new branch. For example our second major release/branch will be designated as 2.0.0.a.</p> <p style="text-align: justify;">The second number will take on two roles. Until we reach our first stable release, this number will increment as we pass major milestones in the development of our first working product. Our first Alpha release was 0.7.0.a. Our first Beta release 0.8.0.b. Our first Gamma release 0.9.0.g. Once we reach our first stable release 1.0.0.s, the role of the second number will shift to identify, that a minor feature has been added or changed.</p> <p style="text-align: justify;">The third number again takes on two meanings. In the pre first stable releases (0.x.x) it will take on the role of changes/additions/bug fixes within a given development stage. After the first stable release (1.0.0.s), the third number will indicate a maintenance/bug fix release.</p> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">Branching: Different Levels of MyDatabase Pilot</div> <p style="text-align: justify;">We will create different product levels of MyDatabase Pilot. Currently we have three branches in mind. MyDatabase Pilot Basic, MyDatabase Pilot Pro, MyDatabase Pilot Dynamic.</p> <p style="text-align: justify;"><span style="font-weight:bold;">Basic Branch</span> - Our first release will mature into our MyDatabase Pilot Basic Branch. This release will be maintained as a minimal footprint product with basic functionality for administering MySQL Databases.</p> <p style="text-align: justify;"><span style="font-weight:bold;">Pro Branch</span> - Version 2.x.x will be developed with as many features as our team can dream up and users can request. This branch will be distributed as MyDatabase Pilot Pro. In order to make this product as appealing and widely excepted, this version will stick to standard HTML output. (JavaScript will be limited, and no Flash or other browser/plug-in dependent technology will be used).</p> <p style="text-align: justify;"><span style="font-weight:bold;">Dynamic Branch</span> - This branch will take all the features of MyDatabase Pilot Pro and make them interactive. The first release will be 3.0.0. Interactivity will be achieved through a combination of advanced JavaScript and/or Flash Integration. This branch will be geared to those users who want to go beyond advanced administration on a static web page and take it to a dynamic level. Expect such features as dragable/dockable tables; expanding/collapsing structures; and more.</p> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">Development Cycle: The Never Ending Story</div> <p style="text-align: justify;">We will constantly look at improving MyDatabase Pilot. Even when we have reached stable/mature status, our work will not be over. We will start a new planning/development stage for a new and improved release. Improvements can come in two forms after our first stable release. They can be major improvements that will create a new branch of MyDatabase Pilot. Or minor improvements to current stable/mature branches. In either case the improvements will go through the same development stages as listed in the "Development Status" section above. The only way a new improvement can short circuit the process is if it is being filtered down from an already tested version of MyDatabase Pilot. This will maintain the integrity of the development status label attached with a particular branch.</p> <p style="text-align: justify;">Gamma releases will not be necessary for minor improvements. Once a minor release has been fully developed and tested in the lab, it can be added directly to a stable/mature branch.</p> <div style="font-size: 18px; font-weight: bold; color: #003399; margin: 3px 0px;">The Road to Maturity: What to Expect</div> <table width="100%" border="0" cellpadding="2" cellspacing="2"> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.0.a (First Alpha Release)<br />Released March 26, 2003<br>Database Connection, List Tables, System Info, Table Structure</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.1.a<br />View Table Records</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.2.a<br />Add New Field</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.3.a<br />Alter Field</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.4.a<br />Drop Field</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.5.a<br />Add New Table</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.6.a<br />Drop Table</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.7.a<br />Alter Table (Rename Table, Alter Table Order)</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.8.a<br />Select</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.9.a<br />Insert</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.10.a<br />Update</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">0.7.11.a<br />Delete</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #FFCC33; text-align: center; border: ridge;">0.8.0.b (First Beta Release)<br />Extensive testing begins; Bug fixes and minor changes will increment the last version number (0.8.x.b); No new major features will be introduced; Any new major features will be released as 2.x.x.a;</td> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">2.0.0.a (Pro Branch)<br />A lot more functionality will be added; Plan is yet to be developed;</td> <td> </td> </tr> <tr> <td width="33%" style="background-color: #99CCFF; text-align: center; border: ridge;">0.9.0.g (First Gamma Release)<br />Product is fully developed according to the plan and tested in the lab; Field testing begins; User feed back will iron out last remaining issues and increment the last version number (0.9.x.g)</td> <td> </td> <td width="33%" style="background-color: #FFCCCC; text-align: center; border: ridge;">3.0.0.a (Dynamic Branch)<br />Interactive presentation will be introduced either via JavaScript as in DynAPI, or through Flash integration</td> </tr> <tr> <td width="33%" style="background-color: #CCFFCC; text-align: center; border: ridge;">1.0.0.s (First Stable Release)<br />Minor bug fixes will increment last version number (1.0.x.s); Minor features may be filtered down from higher branches after thorough testing; Feature additions and changes will increment the second version number (1.x.0.s); No new drastic changes will be implemented in this first stable branch; We will maintain this first stable branch as the "Basic" branch for those users who only need minimal functionality, without the bells and whistles, as outlined in the development plan;</td> <td rowspan="2"> </td> </tr> <tr> <td width="33%" style="background-color: #CCCCFF; text-align: center; border: ridge;">1.?.0.m (First Mature Release)<br />Well established without major bugs reported for at least a year;</td> <td rowspan="2"> </td> </tr> </table> </body> </html> |
