> Yeah, it's a difference of methodologies. I prefer the alternate method
> of providing detailed descriptions in source control commits of what has
> changed, and mentioning the bug number if there happens to be one. I
> find it very frustrating to see a commit message that simply says,
> "Fixed
On Thu, Jul 8, 2010 at 11:05, thron7 wrote:
>
>
> > The whole bugzilla process of having to create a bug report for every
> > minor fix is a PITA already,
>
> Like with so many things, it's just a matter of habit (like brushing
> your teeth before you go to bed). I don't even think about creating
> The whole bugzilla process of having to create a bug report for every
> minor fix is a PITA already,
Like with so many things, it's just a matter of habit (like brushing
your teeth before you go to bed). I don't even think about creating bugs
anymore, I just do it, and the benefit of being abl
On Thu, Jul 8, 2010 at 10:29, thron7 wrote:
>
> On 07/08/2010 04:03 PM, Derrell Lipman wrote:
> > How does one accept a bug in the new bugzilla? There appear to be a
> > whole bunch of missing features...???
>
> It's not much different from the old one: If you want to change the
> assignee, there
On 07/08/2010 04:03 PM, Derrell Lipman wrote:
> How does one accept a bug in the new bugzilla? There appear to be a
> whole bunch of missing features...???
It's not much different from the old one: If you want to change the
assignee, there is an "(edit)" link right to the "Assigned To" field. If
How does one accept a bug in the new bugzilla? There appear to be a whole
bunch of missing features...???
Derrell
--
The trick to education is to teach people in such a way
that they don't realize they're learning until it's too late.
- Harold Eugene "Doc" Edgerton ("Poppa Flash"), 1903-1990,
