Hi, Ray,
It’s hard to say whether this will continue beyond E release.
Meanwhile, we will keep the docs dir in Armband, like we did in previous
releases.
BR,
Alex
From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Monday, October 16, 2017 6:26 AM
To: Alexandru Avadanii
Cc: Sofia Wallin
Hi Alex,
I think the best solution is to remove the document links for Armband on
docs.opnfv.org (or have them linked to Fuel documentation).
But keep the docs directory in your repo if things would change in the future.
//Sofia
From: Raymond Paik
Date: Monday, 16 October 2017 at 05:26
To: Alex
Hi Alex,
I think it makes sense for Armband team to have a separate documentation if
you are going have support of other installers (e.g. Apex or JOID) in the
future
I agree that replicating docs is wasteful, but do you think this would
continue beyond Euphrates?
Thanks,
Ray
On Sunday, Oct
I prefer to maintain it in installer project. If the affected content can
be documented in installer project properly, it will be easier for
maintainer, developer and end user.
Julien
Alexandru Avadanii 于2017年10月15日周日 下午11:27写道:
> Hi,
> During the E release cycle, Fuel and Armband projects merge
Hi,
During the E release cycle, Fuel and Armband projects merged their
documentation(s).
Currently, the contents of Fuel's 'docs/' dir describe usage for both
architecture.
To keep the old behavior unchanged, we duplicated that docs dir in Armband for
now.
Going forward, I think building the sa