Re: How tickets are resolved
On Thu, Dec 19, 2013 at 4:16 PM, Miroslav Suchý wrote: > Something like: > Fixed - puppet.git commit abc123 I need to note this case could be automated with a git hook http://trac.edgewall.org/wiki/CommitTicketUpdater -- Gianluca Sforna http://morefedora.blogspot.com http://identi.ca/giallu - http://twitter.com/giallu ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: How tickets are resolved
On Thu, 19 Dec 2013 19:05:57 +0100 Till Maas wrote: > On Thu, Dec 19, 2013 at 04:16:33PM +0100, Miroslav Suchý wrote: > > > I have suggestion. > > Can we please put into tickets how they have been resolved? > > I mean something else then "Fixed". > > > > Something like: > > Fixed - puppet.git commit abc123 > > or > > Fixed - I run command "rm foo.bar" > > > > This way people (and apprentice group especially) can learn how > > infra set up works. And if ticket need to be reopened (or audited) > > later, you can easily what was really done. > > > > I can understand exceptions in complicated tickets, but usually it > > is just few commits and one or few more commands. Isn't it? > > IMHO it is always good to at least shortly explain what happened. Not > only in tickets but also in IRC. Yeah. I'm happy to try and start being more verbose where possible and ask others to do the same. In some cases it may well not be however. kevin signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: How tickets are resolved
On Thu, Dec 19, 2013 at 04:16:33PM +0100, Miroslav Suchý wrote: > I have suggestion. > Can we please put into tickets how they have been resolved? > I mean something else then "Fixed". > > Something like: > Fixed - puppet.git commit abc123 > or > Fixed - I run command "rm foo.bar" > > This way people (and apprentice group especially) can learn how infra set up > works. > And if ticket need to be reopened (or audited) later, you can easily what was > really done. > > I can understand exceptions in complicated tickets, but usually it > is just few commits and one or few more commands. Isn't it? IMHO it is always good to at least shortly explain what happened. Not only in tickets but also in IRC. Regards Till ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
How tickets are resolved
Hi, I have suggestion. Can we please put into tickets how they have been resolved? I mean something else then "Fixed". Something like: Fixed - puppet.git commit abc123 or Fixed - I run command "rm foo.bar" This way people (and apprentice group especially) can learn how infra set up works. And if ticket need to be reopened (or audited) later, you can easily what was really done. I can understand exceptions in complicated tickets, but usually it is just few commits and one or few more commands. Isn't it? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
