After having discussed with Greg - we decided to extend the opportunity for
scenario owners to issue their respective documentation patches to the Fuel
repo until EoB Wed Sep 21, if they are of good quality, following the DOCS
project standards and the Fuel@OPNFV docs style they will be considered for the
Fuel@OPNFV Colorado 1.0 release.
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jonas Bjurel
Sent: Tuesday, September 20, 2016 10:22 PM
To: email@example.com; David McBride
<dmcbr...@linuxfoundation.org>; Christopher Price
Subject: [opnfv-tech-discuss] Fuel@OPNFV RC3 was cut tonight
Tonight we have cut Fuel@OPNFV Colorado RC3.
This internal release candidate includes everything Fuel@OPNFV intends to bring
to the Colorado 1.0 release September 22.
>From this point on, only critical bug-fixes will be allowed to be merged into
>the stable/colorado branch.
Current status looks very promising - Quite a lot of feature projects
participating as plug-ins, high degree of successful builds , functional tests,
and Yardstick characteristics runs across the all scenarios.
So again - from this point on, we will be extremely restrictive on cherry-pick
merges from master to stable.
opnfv-tech-discuss mailing list