+1, great to see it is being pushed through. This is not always pleasant
work, but it certainly makes our life easier.
130 vs 7275 in fuel-web (fuel-agent-7.0.0-1.mos7275.noarch.rpm)
Two questions:
a) how our patching suppose to work if we have lower version now?
b) why there is mos code name in
I'm glad to announce that everything about this task is done. ISO build job
uses this new repository [1]. BVT is green. Fuel Agent rpm spec has been
moved to the new repo and perestroika has also been switched to build
fuel-agent package from the new repo. The only difference that could
Nice work, Vladimir. Thank you for pushing this, it's really important step
to decouple things from consolidated repository.
--
Best regards,
Oleg Gelbukh
On Wed, Jul 15, 2015 at 6:47 PM, Vladimir Kozhukalov
vkozhuka...@mirantis.com wrote:
I'm glad to announce that everything about this task
Dear colleagues,
New repository [1] has been created. So, please port all your review
requests to stackforge/fuel-web related to Fuel Agent to this new
repository. Currently, I am testing these two patches
https://review.openstack.org/#/c/200595
https://review.openstack.org/#/c/200025. If they
Thanks Vladimir. Let's ensure to get it done sooner than later (this might
require to be tested in custom ISO..) - we are approaching FF, and I expect
growing queues of patches to land...
On Tue, Jul 14, 2015 at 6:03 AM Vladimir Kozhukalov
vkozhuka...@mirantis.com wrote:
Dear colleagues,
New
Guys, we are next to moving fuel_agent directory into a separate
repository. Action flow is going to be as follows:
1) Create verify jobs on our CI https://review.fuel-infra.org/#/c/9186
(DONE)
2) Freeze fuel_agent directory in https://github.com/stackforge/fuel-web
(will announce in a separate
Ok, guys.
Looks like there are no any objections. At the moment I need to create
actual version of upstream repository which is going to be sucked in by
OpenStack Infra. Please, be informed that all patches changing
fuel-web/fuel_agent that will be merged after this moment will need to be
ported
There were some questions from Alexandra Fedorova about independent release
cycle.
according to the configuration [1] Infra team won't be able to do
branching or any kind of release management for new repository.
Could you please clarify, do we plan to version new repository the
same way as we
