We definitely need to assign these bugs to the fuel-docs team. And there is
a good point from Alexandra Fedorova that commit message needs to have
enough information for tech writer. And reviewers should not merge fixes
that do not apply this rule. Otherwise we will end up with new bottlenecks.
Filtering bugs by tags works fine in advanced search, the only problem is
that you can't combine it with filtering by releases (since that's broken
in advanced search and you have to use milestone page for that).
On Thu, Oct 9, 2014 at 12:18 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
We
Hi,
On Fuel Summit '2014 we discussed our Documentation process. According to
follow up we aligned it to OpenStack 'DocImpact' process. The new process
has been tested on background by me and Bogdan Dobrelya. Today, I have
updated Fuel Documentation Process
At the moment OpenStack infrastructure doesn't allow to customize the
bugs it creates, we should propose a patch at some point to implement
that. When we do, I think we should assign such bugs automatically to
fuel-docs team.
I don't think we should separate user and dev docs bugs, we're working
Thanks Dmitry,
let's try to go this way and correct process if needed when we get first
results.
Where is your 80% dev vs user docs figure coming from?
it's no more than my guess. We will see real number over time.
On Wed, Oct 8, 2014 at 10:31 PM, Dmitry Borodaenko dborodae...@mirantis.com
Hi,
Dima, that's really good approach.
Mike, technical writer may ask developer and assign bug to him/her if bug
impacts developer documentation only.
Best Regards,
Sergii Golovatiuk
On 08 Oct 2014, at 21:08, Mike Scherbakov mscherba...@mirantis.com wrote:
Thanks Dmitry,
let's try to go
Sorry I'm so late to the party. Yes, Andreas is right, we simply cannot
take on any more DocImpact in openstack-manuals, but it would be great to
change the infrastructure to log against a more exact match for the bug
tracker for the project with the impacted docs. Looks like you're doing so
with
On 09/24/2014 09:55 PM, Sergii Golovatiuk wrote:
Hi,
I would like to discuss the documentation process and align it to
OpenStack flow.
At the moment we add special tags to bugs in Launchpad which is not
optimal as everyone can add/remove tags
cannot participate in documentation process
Hi,
I would like to discuss the documentation process and align it to OpenStack
flow.
At the moment we add special tags to bugs in Launchpad which is not optimal
as everyone can add/remove tags
cannot participate in documentation process or
enforce documentation process.
I suggest to switch to
