You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The PST/PHT development process is handled differently from other SSA projects. This project is allocated the equivalent of two weeks of development time for each release cycle. This page outlines the PST development and release process.

Ticket Creation

When a PST/PHT ticket is created the following fields must be filled out:

  • Project: SSA
  • Issue Type: Bug, Feature, etc.
  • Reporter: Your Name
  • Summary
  • Description
  • Priority - please do not label Bug Reports as 'Blocker'. If a bug is a Blocker, and is found in production, it should be submitted to the ssa-issues list
  • Component: Proposals
  • labels - if the prioritization label is known, add it
  • attachments - if applicable

Please leave all other fields blank. Any other relevant fields will be filled in by SSA.

Development

Prioritization

PST/PHT work is prioritized by the TTA Group, not via SSA Prioritization.

In order for a ticket to be accepted for prioritization, it needs to be findable via one of the TTA prioritization filters. This is done by adding one of the following labels to the relevant ticket:

  • ph0 - unknown?
  • ph1 - for Call Cycle Issues
  • ph2 - for Review Cycle Issues

At least two weeks prior to the scheduled TTA Prioritization Meeting, Allie Costa will send out the relevant filter to the TTA mailing list.

Stakeholders are responsible for verifying that their issues are present on the filter and adding the PST-DISCUSS label to any issues on the filter they believe should be candidates for the upcoming development cycle.

SSA will verify that all tickets identified for prioritization have work estimates and all needed requirements for work to begin after prioritization

Scheduling and Development

After the TTA Prioritization Meeting, the SSA Release Manager (Charlotte Hausman) will add all chosen tickets to an epic for the upcoming release, and set up all required JIRA release structures.

At this time, all selected tickets will be assigned to a developer by the Release Manager and development will begin.

Testing

Once initial development for a given feature is complete, and as long as another release is not undergoing testing on the my-test.nrao.edu environment, the feature will be deployed to the test environment and the reporting stakeholder will be informed that their issue is available for feature testing. At this time the ticket will be placed into 'Validation' state and assigned to the reporter.

Once feature testing is complete, the reporter/tester should comment on the ticket that the issue is resolved and assign the ticket back to either the developer or the release manager. SSA will move the ticket to 'Pending Release' state until after deployment to production.

Release

On deployment day, the SSA release manager will inform the TTA mailing list when deployment is beginning and when deployment has completed. 

  • No labels