[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dtp-dev] Check-in Guidelines for DTP Projects
|
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
