1 / 7

ESDIS Content Release and Update Process

ESDIS Content Release and Update Process. Overview. The User Acceptance Test (UAT) host shall be the primary location for content modification. The Production host shall be the primary location for collaborative tools work (wikis, document management, calendars, etc).

inez-logan
Download Presentation

ESDIS Content Release and Update Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ESDIS Content Release and Update Process

  2. Overview • The User Acceptance Test (UAT) host shall be the primary location for content modification. The Production host shall be the primary location for collaborative tools work (wikis, document management, calendars, etc). • Production (OPS) will be locked out for editing and will be updated by a process from UAT. • Primary roles include Super Owners (SO), Owners (O), and Managers (M) • A standard content update process will govern regular content changes/updates/deletions. • Regular content changes/updates/deletions will be performed by SO, O, or M. • An archival process will be performed on the 1st and 3rd Thursday of each month. This is . • Abbreviated process will only be performed by SO or trusted M/O. • A special process will govern any non-standard content updates (i.e. for major new version releases) • All content shall be version controlled and tracked in the Drupal CMS. • Regular content versions are stored/tracked in the Drupal CMS process. It is possible to revert to previous/older versions under the “moderate” option. • SAs are responsible for content updates (via repository) on SIT • Developers are responsible for content updates (via repository) on DIT

  3. Roles and Responsibilities • Super Owner (SO) • Administrator of the overall content process • Manages overall process, repository, and content in the UAT & Production environments • Approves/Controls release of content into Production • Can be delegated down to a trusted Content Owner or Content Manager • Owner (O) • Overall responsibility for content area in Production and UAT environments • Civil Servant • Cannot be delegated • Manager (M) • Manages content in UAT environment and works with Owner • Moderates and publishes content into repository for push into Production environment • Responsibility can be delegated to other trusted Content Creators • Provisions and coordinates content for new projects • Assigned by the Owner

  4. Permissions

  5. Content Update Process STANDARD EMERGENCY Content Updated Content Reviewed/ Moderated Content Updated • Performed by Manager or Owner • Performed by O, M(T), or SO Publish Content Publish Content Publish Content UAT UAT • Performed by O, M(T), or SO Production Production • Performed by Owner, Manager, or designated Creator

  6. Content Archival Process UAT UAT Repository Repository • Every month on the 1stand 3rdThursday, O/M or SO performs final review of content in repository in preparation for migration to Production • All content in UATis frozen. Anything not published is not locked (and not used for testing). • O/M or SO promotes content from UAT into the repository • The O/M or SO then makes the content available for the Web Manager, SAs, and Developers to use for the SIT and DIT environments.

  7. New Release Cycle UATprod SITprod SITnew Repository DITprod-n DITnew-n UATprod SITnew SITprod DITprod-n DITnew-n UATprod UATprod SITprod SITnew DITprod-n DITnew-n • Developers and SAs update DIT and SIT environments with content from Repository • Coherent Web develops new release • All content in UATprodis frozen • Coherent Web/SAs migrate version from SITnew over to UATprod

More Related