ACTF initial commit - help!! [message #601591] |
Mon, 12 November 2007 01:07 |
Mike![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=masquill%40us.ibm.com) Messages: 4 Registered: July 2009 |
Junior Member |
|
|
Hello all:
The ACTF project wishes to make its first commit of source to CVS. I have
already completed CQs for third-party components upon which this code will
depend (1849, 1850, 1809). However, I'd like to know how to actually go
about the process of committing code and achieving due diligence. Our
initial
commit will include six plug-ins and a stand-alone RCP aplication which
depends upon these plug-ins. The plug-ins are the first in a series to be
committed as part of the framework.
I have several questions:
1. I was going to file a bug in bugzilla for the new components and the
RCP application as suggested by the CQ process but the version combo box
contains only the item 'Unspecified.' Do we need to move through some
other process prior to performing an initial commit? How do we introduce
the
initial version? The same problem holds for components. How do we
introduce a an additional component and get it to appear in the components
list?
2. When I file the CQ for the components and the RCP application, do I
file one per plug-in and one for the app or is it sufficient to file one
CQ for the entire commit of six plug-ins together with the RCP app? Also,
I take it that the attachment will include everything that will be
committed to CVS - source,
resources, images, docs, legal, and build scripts.
5. Finally, if I'm asking the wrong people these questions and should be
posting to the Eclipse Technology Project mailing list, pls let me know.
Thanks so much for your assistance.
--> Mike Squillace
IBM Human Ability and Accessibility Center
Austin, TX
|
|
|
Powered by
FUDForum. Page generated in 0.03097 seconds