Version update policy
This document describes workflow of planning, creating and delivering TravelWise.NET system.
Before reading this please check info about _existing_versions_ (create a page)
(a page describing team and roles should also be created, links from here should be added)
- Every Monday morning the Test versions are updated. PIC: Delivery Team. It can only happen by request if users need to test smth.
- Every second Wednesday BK Live version is updated. PIC: Delivery Team
- Each next Wednesday after the BK update, the Agent and NTS/JTB version is updated with the week-old BK’s version including some fixes.
- Friday (the week before BK update), or Monday (2 days prior to BK update) Release Candidate version is created, all involved people get informed and perform some testing according to their needs. By default, RC version is successful, unless anybody submit a showstopper problem.
- A day before each Live version update list of WIs is mailed to all involved and Release Notes written based on it PIC: list of WIs - Delivery Team; Release Notes - Tatiana T. (Ekaterina) & Local IT manager
- Release notes are uploaded not less than 1 day prior to update for BK: www.bikiwiki.dk (is it relevant?) and for NTS/JTB: http://intranet.nettravelservice.com and the mail informing users about that fact becomes sent. PIC: Tatiana T. (Ekaterina) & Local IT manager for BK; Kaj Jensen for NTS/JTB
- Local IT manager from user’s side has a right until Tuesday afternoon to cancel an update (by writing an email as a reply to Release Candidate email). In case he won’t do that, the live version will be updated.
- Critical WIs can be added in the release separately from the main change sets queue, but more rarely it happens the better, and it is not always technically possible.
Please see the drawing of updates schedule
