Table of Contents
- Introduction
- How to Get a Feature into the Product
- Voting on RFEs
- Understanding the Portal Page
- Understanding the Release Page
- Understanding the Patch Page
- Understanding the Release Table
- Understanding the RFE Table
- Understanding the Bug Table
Introduction
This help document describes the Zimbra product management websiteb. If you are viewing the public version of the site, some of the
fields/content described in the various tables and pages will not be visible to you as they contain private and/or customer
senstive information.
If you have any suggestions or comments, please send email to ross@zimbra.com.
How to Get a Feature into the Product
- File an RFE in Bugzilla. Make the description as clear as possible. If there is a customer behind the feature request, make
sure you mention it in a comment but make sure to mark that comment as priviate in order to prevent folks outside Zimbra
from seeing our customer names.
- Enter any support cases in the support case field
- Vote for it
Voting on RFEs
RFEs (and bugs) are in part triaged by both the number of support requests and votes. So the more votes a RFE has, the more likely
it is to make it into a release. The product team looks at issues on a weekly basis to determine what goes into which release so
voting is very important.
Understanding the Portal Page
The portal page is the main landing page for the pmweb site. It consists of the following information:
- Release Table - This table describes the current and future ZCS releases
- RFEs with most support cases - This is the top 10 list of RFEs with the most support cases. (See Understanding the RFE Table for more info)
- RFEs with most votes - This is the top 10 list of RFEs with the most votes.
- RFEs that are Deal Blockers - These are RFEs that sales has indicated are blocking deals
- Critical+ Bugs - This table provides the list of bugs that have a Critical and above severity in the system.
- Bugs with most support cases - This is the top 10 list of bugs with the most support cases. (See Understanding the Bug Table for more info
- Bugs with most votes - This is the top 10 list of bugs with the most votes.
- Bugs that are Deal Blockers - These are bugs that sales has indicated are blocking deals
- Open issue summary table - This table provides a count of all the bugs/RFEs in the system totaled by severity and priority.
- Bug Charts - The four charts provide an important overview of the product quality.
Understanding the Release Page
The release page provides an details about a particular release. This page is accessed from the Release
Table on the Portal page.
There is lots of useful information on the release page:
- Release Summary - The summary provides a quick overview of the releases status including the planned and targeted GA dates
- Milestones Table - This table lists out the release milestones and the date the milestone has or is going to be be releases
- Platform Table - This table details the platforms supported by this release of the ZCS. Items in bold/blue are additions to
this release. The platform table is broken out by the Open Source and Network additions.
- Patches Table - The patch table lists the set of released and upcoming patches for the release. In addition it provides the
status of the patch. Clicking on the patch version will take you to the Patch Page
- Requirements Table - The list of requirements in the release. Please see Understanding the RFE Table
for more information on this table
- Fixed Issues Table - The list of bugs that have been fixed in the release. Please see Understanding the Bug Table
for more information on this table
Understanding the Patch Page
The patch page provides an details about a patch to a release. This page is accessed from the patch table on the Release Page
The following is the information provided by the patch page
- Platform Table - This table details the platforms supported by this patch. Items in bold/blue are additions made by
the patch. The platform table is broken out by the Open Source and Network additions.
- Requirements Table - The list of requirements included in the patch. Please see Understanding the RFE Table
for more information on this table
- Fixed Issues Table - The list of bugs that have been fixed in the patch. Please see Understanding the Bug Table
for more information on this table
Understanding the Release Table
The release table provides information about current and future ZCS releases. It consists of the following columns
- Release - The release version and code name. Clicking on this will take you to the release's release page
- Status - The current status of the release. This can be one of the following values:
- Not Committed - The release is not yet committed in either features nor date. This is typically the case when
release planning is not yet concluded
- Locked - The release plan is locked i.e. the set of features in the release has been agreed upon and targeted.
Changes at this point must occur through the change process and must be driven by a business or engineering need
- Slipped - The release has slipped beyond the planned GA date. This may be due to engineering issues and/or
significant changes to the scope of the release
- Released - The release has been er... released
- EOL - The release is end of life'd meaning that it is no longer supported. Customer should be strongly
encourage to migrate to a newer version of the ZCS.
- Patch Level - The current patch level for the release. Customer's on this release should be upgraded to this
patch level.
- Beta 1 - Beta 3 - These are various (planned) beta releases. A release may have one or more beta builds. These columns
will list the (planned) release dates for each beta. Not all releases will have 3 beta builds. Generally quality should improve
with each subsequent beta build. If there is a date in parenthesis, then this was the original target date which was
missed due to a slip
- RC 1 - RC 3 - These are various (planned) Release Candidate (RC) releases. A release may have one or more RC releases.
These columns will list the (planned) release dates for each RC. Not all releases will have 3 RC releases. Generally quality should improve
with each subsequent RC build. If there is a date in parenthesis, then this was the original target date which was
missed due to a slip
- GA
- This is the (planned) GA date. If there is a date in parenthesis, then this was the original target date which was
missed due to a slip
Understanding the RFE Table
The RFE (Request For Enhancement) table lists a set of product requirement. The RFE table appears in multiple places. For
example: RFE's with the most support cases on the portal page, or the requirements table on the release page. The RFE table has the
following columns:
- If there is an icon in this column, then the RFE has been marked as private
- LOE - Engineering level of effort. One of:
- High - One or more months of engineering effort
- Med - Less than one month, but more than a week of engineering effort
- Low - Less than a week of engineering effort
- ID - This is the RFE id in Bugzilla. Clicking on this will open up a new window with the bugzilla data.
- Pri - The priority of the RFE. Priority can range for 1 - 3, with one being the highest priority. Priority is
determined by a number of factors including: The number of support cases, the number of votes, the strategic value of the RFE, the
sales value of the RFE
- Description - The description of the RFE. Note that if there is a requirements document for the RFE, then the
description will be a link which when clicked will open up the requirement in a new window. Requirements are typically stored in the
Wiki (and hopefully soon in ZCS documents)
- Patch - When present indicated the patch in which this RFE was included. If blank, then it is in the initial release.
all instances of the RFE table
- Component - The RFE component
- Status - The status of an RFE can be one of:
- Not Committed - In the RFE table on the release or patch pages, this column means that the feature is under
consideration for the release, but may not make it into the release. when appearing on the portal page, it means that the RFE is
under consideration for the release detailed in the target column. If the target column is does not specify a release, then the RFE
is not committed to any release.
- Targeted - The RFE is targeted for the release. Unless something bad happens it should make the release
- At Risk - A targeted RFE is at risk for not making it into the release. this is usually to a technical roadblock
that may be overcome in time to make the release
- At High Risk - A targeted RFE is at highh risk for not making it into the release. This is usually due to a major
technical roadblock
- Completed - The RFE is completed and in the release
- DB - Deal Blocker - If the
icon is present in this column, then the RFE is blocking one or more deals. The comments in the RFE will detail the deal(s) gated by this issue
- Votes - The number of votes for the RFE
- Support Cases - number of support cases for the RFE
- Target Milestone - The target release for the RFE. This column will not appear on the release and patch pages for
obvious reasons
- Last Modified - The date the RFE was last modified in bugzilla
Understanding the Bug Table
The bug table lists a set of bugs filed against the ZCS. The bug table appears in multiple places. For
example: bugs with the most support cases on the portal page, or the fixed issues table on the release page. The bug table has the
following columns:
- - If there is an icon in this column, then the RFE has been marked as private
- ID - This is the bug id in Bugzilla. Clicking on this will open up a new window with the bugzilla data.
- Severity - The severity of the bug. Bugs may have the following severity:
- Blocker - Blocks development or testing and has no workaround
- Critical - The bug causes the system (client or server) to crash, freeze, perform poorly, or leak resources
- Major - Bug causes a major loss of functionality or a major subcomponent is not working
- Normal - Typical bug that impacts feature usage
- Minor - Minor loss of function, or other problem where easy workaround is present
- Description - The description of the bug.
- Patch - When present indicated the patch in which this bug was included. If blank, then it is in the initial release.
- Status - The status of a bug. Please see Bugzilla for more info
- Votes - The number of votes for the bug
- Support Cases - number of support cases for the bug
- Target Milestone - The target release for the bug. This column will not appear on the release and patch pages for
obvious reasons