Re: [dtp-dev] Check-in Guidelines for DTP Projects

[Brian Payton <bpayton@xxxxxxxxxx>]

Rob,

The two check-in requirements you list are certainly
a simple and
reasonable minimum.  Given CVS's "anything
goes, and good luck
finding it later" nature, the more discipline
we can bring to the
check-in process, the better.

The automated CVS reporting tools from the EMF team
look very useful.
I'd love to have an easy way to tie together all the
CVS updates 
related to a particular bug.  (Without something
like this I've
had to be diligent in adding remarks to my bug entries
summarizing 
the changes for each file.)  And being able to
automatically generate
bug lists for builds is a clear win.  We will
need to be careful that 
our bug abstracts are clear and properly describe
the scope of the 
problem and the fix.

All we need now is a way to apply or roll back all
the changes for a 
bug fix at once.  (But then we would be using
Subversion or 
ClearCase... :)

Brian

Brian Payton
SQL Tools Development
IBM Silicon Valley Laboratory
(408) 463-2989, T/L 8-543-2989



dtp-dev-bounces@xxxxxxxxxxx wrote on 11/15/2005 04:53:01
PM:

> 
> Hey all,
> 
> I've been asked to put together some guidelines with respect to check-ins.
> Here's the proposal thus far...
> 
> 1.  All work checked into the CVS repository should correspond
to a
> bugzilla entry.  Work contributed by non-committers should be
appended to
> the bugzilla entry using a CVS patch.
> 2.  Check-in comments should include, as the first characters
in the
> comment, the bug number surrounded by square brackets (e.g. "[123456]
> modified blah to do blah blah blah").
> 
> The above would be required by all committers.  The benefit of
doing
> this....
> 
> 1.  We can have check-in notifications automatically forwarded
to a mailing
> list (if we choose to).
> 2.  We can generate a list of work done for each bug.
> 3.  We can generate a list of work/bug fixes included in a build.
> 
> For these last two items, please refer to the following bugzilla entry
> (Nick Boldt on the EMF team was kind enough to supply this information):
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=116542
> 
> Also refer to the EMF project site for examples of the functionality
> provided:
> http://www.eclipse.org/emf/news/release-notes.xml
> http://download.eclipse.org/tools/emf/scripts/news-whatsnew-cvs.php?
> source=emf&bug=113906&Bugzilla=113906
> 
> I think this is great functionality and that it would be nice if we
could
> enable it and incorporate it into the DTP build process.
> 
> What do you think?
> 
> Rob
> 
> _______________________________________________
> dtp-dev mailing list
> dtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dtp-dev