Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-2007

Enhance process for development and incubation of new features

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • Enhance process for development and incubation of new features
    • False
    • False
    • No
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • No
    • N/A
    • None

      As we develop new features in RHODS, we want to enhance the process to accomplish the following objectives:

      1. Expand exposure to new features during an incubation period to increase our confidence in releasing new features to production. We would like enable users beyond QE to access, evaluate, and test new features prior to being released to production. The ultimate goal is to find any issues prior to production so we can enhance the quality of new features when they are released to customers.

      2. Ensure development for larger features that may take longer to develop doesn't impact our ability to release other features on a regular cadence when they are completed. In other words we don't want to hold up the release of a completed feature because it's tied to another feature that is still under development. Larger features should not affect regularly planned releases with other new features.

      3. Make it easier for developers to work on large new features (such as HA) that may developed over a longer period of time. For example, a larger feature may require development work on several months.

      4. Make testing RHODS changes (small or big) easier for RHODS developers.

      Requirements:
      1. P0: As part of the standard new feature release process, the build must be available in the pilot cluster for an incubation period prior to production release. Ideally, the pilot cluster could be updated periodically at certain milestones of feature development to have sufficient time to identify issues prior to production release.

      2. P0: Development of features that require longer development cycles must not impact the ability to release other completed features on a regular defined cadence. For example, if the standard release cadence is every 2 weeks, we must be able to release completed features when they're ready in a standard 2 week release even if other features are still in development. The goal is to ensure we can release new features when they're ready in a standard cadence while working on larger features that may require a longer development period.

      Feature release proposal doc: https://docs.google.com/document/d/1Pko6_H0q1xLuN4e-jdrc3KTZ4Cfk3nOa9zzHYknR3O4/edit#

            Unassigned Unassigned
            jdemoss@redhat.com Jeff DeMoss
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: