[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] New comitter information
|
Konstantin,
There are a some guidelines but they are quite flexible, and give you a
lot of freedom with some things to watch for:
You can commit code into cvs, but we try to make sure we know what
component/feature/subfeature it goes into.
-If it is an existing one, it is good to check things with the component
owners (typically a subfeature composed of bunch of plugins). The
reason is, when code is committed into cvs in an existing component, and
when this component is released, typically by its owner, your code that
is in the HEAD may also get released. It is always good to keep in sync
with other developers working on that component.
-If you have your own component, a plugin or a whole subfeature, you are
bit more flexible because of the relative ease of managing
dependencies. But there are still some rules. You should check with
the Architecture group to make sure that feature/subfeature/plugin is
inline with the wtp principles.
Finally, the act of "releasing" is a bit more than committing code into
CVS; when your code is in CVS, it does not get picked by a build
automatically. To become the part of a build, the code/component must
be assembled into a WTP "distributable". A distributable is a set of
top-level wtp components. The process of assembly is the act of adding
your component to the feature.xml of an approved wtp build feature.
And a final bit of developer trivia is that our builds always use "map"
builds. This means that only the tagged version of your component will
be able to gon into a build. These maps are in the /releng module in CVS.
Some of these concepts are described in:
http://www.eclipse.org/webtools/development/arch_and_design/subsystems/SubsystemsAndFeatures.html
https://bugs.eclipse.org/bugs/show_bug.cgi?id=108259
Little bit out-of-date but some concepts are helpful here. We will
update that document.
http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/Attic/readme.html?rev=1.6&search=None&hideattic=1&cvsroot=WebTools_Project
Interesting because it has a "how-to-release" workflow.
http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.wtp.releng/Attic/project_plan.html?rev=HEAD&hideattic=0&cvsroot=WebTools_Project&only_with_tag=HEAD&content-type=text/html
Is there a doc somewhere that describes wtp code submit/release
procedure? How does one release the code that was submitted
previously? What tests need to be run prior to submit vs. prior to
release? Anything else that a new committer needs to know (especially
one with very limited CVS experience)?
Any pointers would be much appreciated.
- Konstantin
------------------------------------------------------------------------
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
--
Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com/
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx
