Open Stack

We also often use bugtracker as a TODO tracker. This template does not work for TODOs at all. I understand that it’s not technically mandatory to follow it, but if that Fuel Bug Checker is going to spam on every single TODO, our inboxes will overflow.

> 30 бер. 2016 р. о 17:37 Roman Prykhodchenko <me at romcheg.me> написав(ла):
> 
> Guys,
> 
> I’m not trying to be a foreteller but with a bug template this huge and complicated people will either not follow it or track bugs somewhere else. Perhaps we should make it simpler?
> 
> Detailed bug description:
> <put your information here>
> Steps to reproduce:
> <put your information here>
> Expected results:
> <put your information here>
> Actual result:
> <put your information here>
> Reproducibility:
> <put your information here>
> Workaround:
> <put your information here>
> Impact:
> <put your information here>
> Description of the environment:
> Operation system: <put your information here>
> Versions of components: <put your information here>
> Reference architecture: <put your information here>
> Network model: <put your information here>
> Related projects installed: <put your information here>
> Additional information:
> <put your information here>
> 
> 
> - romcheg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/7ccac710/attachment.pgp>