[platform-ant-dev] Re: [platform-debug-dev] Bugzilla practices proposal

[Kevin Barnes <krbarnes@xxxxxxxxxx>]

I think it's a good idea. It saves a
lot of time when verifying bugs to what files have changed and how they
have changed.
Kevin

Jared Burns <jaredburns@xxxxxxx>
Sent by: platform-debug-dev-admin@xxxxxxxxxxx

04/26/2004 07:33 PM

Please respond to
platform-debug-dev

To	platform-debug-dev@xxxxxxxxxxx, jdt-debug-dev@xxxxxxxxxxx, platform-ant-dev@xxxxxxxxxxx
cc
Subject	[platform-debug-dev] Bugzilla practices proposal

Some of you may have noticed that I started annotating
all of the bugs I
fixed with every file I checked in for that bug. Having just gone back
and looked at one of my previous check-ins using this information, I'm
convinced that it would be a useful practice for all of us.

Unfortunately, CVS can't tell us which files were checked in together.
But annotating Bugzilla this way lets us get the information back if we
really need it. The format I've been using can be seen here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=53222&comment=9#c9

It's basically -
Changes to:
File1 - Brief description
File2 - Brier description
etc.

The one additional thing I'd propose that I haven't been doing yet is to
include the fully qualified path of any files that we delete. In the
example I referenced above, I actually wanted to go back and restore a
file (DebugContextManager) from the repository. If I'd have included the
fully qualified name, it would have saved me a couple minutes.

Sound good/bad/ugly?

Thanks,
- Jared

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev