On 6 aug. 2014, at 15:06, Rohit Yadav <rohit.ya...@shapeblue.com> wrote:
> Hi Hugo, > > +1 > > On a totally different issue, if we’re going to adopt git-flow let’s not use > bug fix branch names with the prefix “hotfix/“ because as the per convention > it’s for already released versions and for serious production issues. > Instead, I recommend that we can either go with “feature/CID-XXXX” as all > features should have bug ids and bugfixes should have them too. Feature sounds a bit strange to me for bugs coming out of static code analysis. Typically they are bugs in released versions (unless we really fix the lot of them ;-) ) The seriousness is up for debate and varies issue by issue. > > Lastly, we can in-fact use custom names in git-flow so we can use something > like “bugfix/ID” like “bugfix/1234” so we don’t even have to add the > "CLOUDSTACK-“ prefix and it’s more readable. The commits though should have > the full name “CLOUDSTACK-xxx” to be picked up by ASFBot. These are not jira issues, but coverity issues. ASFbot doesn’t now about them. They are for now manually tracked in the coverity interface. > > Cheers. > > > On 06-Aug-2014, at 2:39 pm, Hugo Trippaers <h...@trippaers.nl> wrote: > >> Heya, >> >> How about we name the branches for coverity fixes after the relevant CID? >> Something like /hotfix/CID-xxxxxx. That would make it very easy for >> everyone to track which coverity fixes are tracked where and who is working >> on which CID. >> >> The name hotfix coverity fix is a bit too generic and will probably not help >> developers pinpoint where an issue was introduced. >> >> >> Cheers, >> >> Hugo > > Regards, > Rohit Yadav > Software Architect, ShapeBlue > M. +41 779015219 | rohit.ya...@shapeblue.com > Blog: bhaisaab.org | Twitter: @_bhaisaab > > > > Find out more about ShapeBlue and our range of CloudStack related services > > IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//> > CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/> > CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> > CloudStack Infrastructure > Support<http://shapeblue.com/cloudstack-infrastructure-support/> > CloudStack Bootcamp Training > Courses<http://shapeblue.com/cloudstack-training/> > > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd or related companies. If you are not the > intended recipient of this email, you must neither take any action based upon > its contents, nor copy or show it to anyone. Please contact the sender if you > believe you have received this email in error. Shape Blue Ltd is a company > incorporated in England & Wales. ShapeBlue Services India LLP is a company > incorporated in India and is operated under license from Shape Blue Ltd. > Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is > operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company > registered by The Republic of South Africa and is traded under license from > Shape Blue Ltd. ShapeBlue is a registered trademark.
