Bug 6929 and Status field in Bugzilla in relation to git master
I'm working on a system which would allow me to automatically apply arbitrary number of patches from bug tracker to new koha instance (using unique git branch for it) for easy testing of multiple-patch interaction. It's in planning stage, but I started going through my Cc bugs in Bugzilla and stumbled upon 6929 which was in git master, so I chaged it's Status to RESOLVED FIXED Then it occured to me that this not be OK, since Robin might depend on bug beeing assigned to him as reminder to apply it to production somewhere. Should I keep my hands off Status field in bugzilla or try to update them to current master? -- Dobrica Pavlinusic 2share!2flame dpavlin@rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin
Op 25-11-11 08:35, Dobrica Pavlinusic schreef:
Should I keep my hands off Status field in bugzilla or try to update them to current master?
No, it would be bad for me to rely on bugzilla for my own internal processes. If it's in master and working, I think it should be always OK to mark it resolved. Robin.
participants (2)
-
Dobrica Pavlinusic -
Robin Sheat