Evgeniy,
Right. There is only nailgun python project, development documentation [1]
and some minor scripts [2] which are outdated. Our further plan is to move
nailgun itself to a separate repo fuel-nailgun, remove outdated code, and
then move development doc pages to corresponding git repos.
[1
Hi,
Thank you for your work, really happy to see it done. So as far as I can
see from now on in fuel-web repository we have only Nailgun project. Is it
correct?
On Fri, Feb 26, 2016 at 3:53 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Dear colleagues,
>
> We are ready for moving
Vitaly,
As we decided yesterday custom job with fuel-ui and fuel-web refspec
parameters could help here. Is it not enough for our case? In general, the
case when two PRs depends on each other was deliberately denied to be
handled automatically. Please read this thread [1] for details.
[1]
http://
Fuel UI code has been completely removed from fuel-web repo and CI jobs to
verify fuel-web RR with fuel-ui code and fuel-ui RR with fuel-web code have
been set up. So the code separation can be considered as done.
Though there is one thing needs to be done and we don't know how to solve
that task
The new repo has been created: https://github.com/openstack/fuel-ui. Please
move all change requests there. Fuel UI code in fuel-web repo is going to
be removed soon.
2016-02-26 19:53 GMT+07:00 Vladimir Kozhukalov :
> Dear colleagues,
>
> We are ready for moving UI javascript code to a separate g
Dear colleagues,
We are ready for moving UI javascript code to a separate git repository.
Since now all review requests for fuel-web@master that are related to UI
must be marked -2 and later abandoned. Once new project fuel-ui is created
those changes should be backported to this new repository.
