Difference between revisions of "Preview Repository"
(Created page with "_PAGE WORK IN PROGRESS_ == Overview == The aim of Preview is making available in a single point the updates of the middleware products as soon as they are released by the prod...") |
|||
Line 2: | Line 2: | ||
== Overview == | == Overview == | ||
The aim of Preview is making available in a single point the updates of the middleware products as soon as they are released by the product teams. | The aim of Preview is making available in a single point the updates of the middleware products as soon as they are released by the product teams. | ||
The same updates will also undego to the usual UMD verification and staged rollout processes, which requires several months to be completed; instead, through the Preview repository the resource centres administrators can avoid this waiting and can apply the updates on their machines as soon as they are announced. | The same updates will also undego to the usual UMD verification and staged rollout processes, which requires several months to be completed; instead, through the Preview repository the resource centres administrators can avoid this waiting and can apply the updates on their machines as soon as they are announced. | ||
Our plan is to release the Preview updates on a monthly basis, after having gathered the relevant information by the product teams. | Our plan is to release the Preview updates on a monthly basis, after having gathered the relevant information by the product teams. | ||
== Release process == | |||
The product teams usually announce a new version of their product by a GGUS ticket or email to URT team. | |||
In the announcement it is reported all the relevant information about the update: description of new features and bugfixes, installation and configuration details. | |||
The new packages are downloaed and signed, then it is created a new release of the Preview middleware uploading the new packages into the repository. | |||
After preparing the release notes, the Preview update is announced. |
Revision as of 16:47, 22 January 2016
_PAGE WORK IN PROGRESS_
Overview
The aim of Preview is making available in a single point the updates of the middleware products as soon as they are released by the product teams. The same updates will also undego to the usual UMD verification and staged rollout processes, which requires several months to be completed; instead, through the Preview repository the resource centres administrators can avoid this waiting and can apply the updates on their machines as soon as they are announced. Our plan is to release the Preview updates on a monthly basis, after having gathered the relevant information by the product teams.
Release process
The product teams usually announce a new version of their product by a GGUS ticket or email to URT team. In the announcement it is reported all the relevant information about the update: description of new features and bugfixes, installation and configuration details. The new packages are downloaed and signed, then it is created a new release of the Preview middleware uploading the new packages into the repository. After preparing the release notes, the Preview update is announced.