[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [stp-dev] building stp
|
- From: "Eclipse WebMaster (Denis Roy)" <webmaster@xxxxxxxxxxx>
- Date: Thu, 30 Mar 2006 10:40:35 -0500
- Delivered-to: stp-dev@eclipse.org
- Organization: Eclipse Foundation, Inc.
- User-agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)
Naci,
> *IMPORTANT*
> 5) Notify webmaster@xxxxxxxxxxx
> -) to create an account stpBuild on build.eclipse.org
Done. I will e-mail you the password directly.
> -) to create a shared stpbuild group and a directory
> /shared/stp to store build files
Done.
> -) to give access to ndai & ozan and other build masters to
> this area and local account @ build.eclipse.org
You have access, but I don't know who ozan is.
> -) create an email alias stp.builder@xxxxxxxxxxx for build
> reporting
Done. You are the only one on the list.
> -) create a mail list stp-releng for build reporting
This request needs to come from the STP PMC.
> -) to create a download area @ download.eclipse.org for stp
This was done as part of the STP project provisioning. Your (Naci)
eclipse.org committer account doesn't currently allow you to write
there, but you are an STP committer, so please get the STP PMC to ping
us for this.
If you need anything else, please let me know.
Denis
> That is all I could think of so far :-)
Naci Dai wrote:
For your info - we have the STP builds running on our local build server
already. We will start documenting this at:
http://wiki.eclipse.org/index.php/Main_Page#Project_Wiki_pages
http://wiki.eclipse.org/index.php/STP
I already created the pages
Some initial action items:
1) Renaming the packages (com.ibm -> org.eclipse.stp )
2) Placing them under the cvs tree (stp/components/sca/plugins)
3) Creating top level assembly features for the sca/core subproject
cvs tree (stp/components/sca/features)
4) Form a team of build masters 2-3 people usually suffice.
*IMPORTANT*
5) Notify webmaster@xxxxxxxxxxx
-) to create an account stpBuild on build.eclipse.org
-) to create a shared stpbuild group and a directory
/shared/stp to store build files
-) to give access to ndai & ozan and other build masters to
this area and local account @ build.eclipse.org
-) create an email alias stp.builder@xxxxxxxxxxx for build
reporting
-) create a mail list stp-releng for build reporting
-) to create a download area @ download.eclipse.org for stp
That is all I could think of so far :-)
(no chat topic is set)
[15:56] DavidBosschaert left the chat room. (Read error: 110
(Connection timed out))
[17:05] jrohn joined the chat room.
[17:14] oisin: FYI: due to the summertime increment in EU, we are
keeping this channel open from 1100-1300 EST
[17:14] dparikh joined the chat room.
[17:15] dparikh left the chat room. (Client Quit)
[17:49] DavidBosschaert joined the chat room.
[18:03] RobCernich joined the chat room.
[18:03] oisin: hi guys
[18:03] DavidBosschaert: Hi Oisin
[18:03] oisin: we could be a little quiet today, because of the time
shift
[18:05] oisin: hi Rob
[18:05] RobCernich: hey guys
[18:06] oisin: we have a couple of things to talk about
[18:06] oisin: 1. STP Build
[18:06] oisin: 2. IBM Code Contrib Analysis
[18:07] oisin: 3. STP Architecture {design | deploy | run}time
[18:07] oisin: 4. Web site
[18:08] oisin: obviously by a 'couple' I actually mean 'several'
[18:08] oisin: AOB?
[18:09] DavidBosschaert: Maybe pombreda wants to introduce him/herself?
[18:11] oisin: intros are welcome along the way, let's carry on anyway
- we have a v. small group here, but let's get going
[18:11] oisin: 1. STP Build
[18:12] oisin: I assume that you have seen Naci's request to Ozan to
dup the WTP build system and get it ready to transition to STP
[18:12] DavidBosschaert: I havent. Was that sent to stp-dev?
[18:13] oisin: apologies - I just double-checked it was not sent to
stp-dev, just as an fyi to myself
[18:13] oisin: he will be directing it to compile/test/etc the IBM code
[18:13] oisin: this will not be delivered to build.eclipse.org yet, as
the IBM code is still in the 'zilla
[18:14] oisin: but it will imply a functioning build
[18:14] oisin: we **really** need buildmasters for this project
[18:14] DavidBosschaert: Cool, any idea when Ozan will be working on
this>?
[18:14] oisin: Naci and his colleagues will *not* be maintaining this
for ever, they have other jobs
[18:15] DavidBosschaert: On the buildmasters, maybe we could organize
something like a rota...
[18:15] oisin: we need initial buildmasters, with lots of coverage.
[18:15] DavidBosschaert: IONA doing it a month, Sybase a month, IBM a
month and so on?
[18:15] oisin: not a good use of resources David
[18:16] oisin: also, company orientation is not really appropriate
[18:16] DavidBosschaert: How does DTP do it then?
[18:16] oisin: we will be running continuous builds, implying that we
need time zone coverage to fix up fails
[18:16] oisin: in a timely fashion
[18:17] oisin: please note that just because you decide to be a
buildmaster at the outset it doesn't mean that you have to be one forever
[18:17] oisin: it is a transferable skill, unlike double-jointedness
[18:18] RobCernich: dtp does not, as yet, have automated builds
[18:18] oisin: we have lots and lots of people listed as committers --
we need at least 4 persons for this initial foray
[18:19] oisin: to give Naci support and to form a mind-meld between
themselves
[18:19] oisin: ok - that's my piece - I will be putting pressure on
all around
[18:19] oisin: can I move on to 2?
[18:20] DavidBosschaert: I noticed that Devang has added build
instructions to the bugzilla entry at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=132747
[18:20] DavidBosschaert: (This applies to 2)
[18:20] oisin: Ok, we are now on 2
[18:20] oisin: Yes I have built it and run the tests -- there is one
failing unit
[18:21] RobCernich: i haven't had a chance to review the code yet
[18:21] oisin: what I haven't done is put together a structural
analysis (for tangles, etc) on the code
[18:21] RobCernich: it's on my list of things to do
[18:21] oisin: I think we are all in the same boat Rob, a lot to do
after returning from eclipsecon
[18:22] oisin: but let's keep it a high priority all the same
[18:22] DavidBosschaert: Are we happy with the amount of dependencies
this code has?
[18:22] oisin: right now it is very early in the play so some
dependencies are ok
[18:23] oisin: the WTP dependency is on the WST part of the project
and I am told by Dan it's actually just a small area of the code that
is required
[18:23] oisin: this is something that we can put in as a request to
WTP to turn into a 'feature' as part of their build to make the
consumable smaller
[18:23] oisin: the JEM dependency I was not aware of until I tried to
compile it initially
[18:24] oisin: this is part of the VE stuff and is a separately
packaged thing
[18:24] oisin: I am unsure of the strength of the requirement for JEM
[18:25] oisin: Let's all try to get the code reviewed by the end of
next week, eh?/
[18:25] oisin: Dan + Michael are committed to addressing all questions
etc and hope to post some documentation soon
[18:25] DavidBosschaert: Sounds like a plan.
[18:25] oisin: ok let's go to 3
[18:26] oisin: our architecture is, well, more of a markitecture (c.f.
proposal/charter pages)
[18:26] RobCernich: works for me
[18:26] oisin: I've nearly got a first draft architecture diagram
ready to go
[18:27] oisin: This focusses directly on the part which is considered
by ESB vendors to be the most interesting -- design/deploy
[18:27] oisin: There is nothing in there right now wrt runtime tooling
[18:27] oisin: by that I mean tools to interact with an operation SOA
system
[18:27] oisin: this could very well be a place where we can feed stuff
into TPTP
[18:29] oisin: i hope the arch can act as a focus for consumption of
elements of WTP
[18:30] oisin: well I guess it's not interesting until you see the
architecture, so I'll move on to 4 if that's ok
[18:30] oisin: Our website is a little....lightweight
[18:30] oisin: it also has the old look and feel
[18:30] oisin: we need to address these two issues
[18:31] oisin: I would certainly like someone to take point on
maintaining action items pertaining to the web site content
[18:32] DavidBosschaert: Pretty much all the links are broken
[18:32] oisin: the PMC will probably do this in the short term, but
project leads will be asked to maintain content relevant to their
subproject/incubator
[18:35] oisin: before subproject leads are fully in place, all
committers may be asked to do some work in this area
[18:35] oisin: ok. that's up to 4
[18:35] oisin: anything else on anyone's mind?
[18:37] RobCernich: too much on mine
[18:41] pombreda: DavidBosschaert: sorry, I was not in front of my
computer: I am an Eclipse open source fan, and I maintain an open
source distro called EasyEclipse plus a few plugins like EasyStruts...
[18:41] pombreda: I amde a few talks at EcliseCon too, like
http://eclipsecon.org/2006/Sub.do?id=68
[18:42] pombreda: DavidBosschaert: you can expect me to be there as an
observer
[18:43] oisin: hi Philippe!
[18:44] oisin: Rob -- what would you like to talk about
[18:44] pombreda: oisin: hi!
[18:44] DavidBosschaert: Thanks Philippe!
[18:45] RobCernich: nothing to talk about
[18:45] RobCernich: unless you can slow the rotation of the earth so
there are more hours in the day
[18:46] oisin: ho ho! did you know that I am trying to invent a time
machine too
[18:46] RobCernich:
[18:46] oisin: but have had no success, so the only option is to
divest work
[18:47] oisin: ok, we can leave it on that optimistic note -- I'll
post the irc content to the mailing list later as per usual
[18:47] oisin: thanks all and have a good evening/afternoon
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev
--
Eclipse WebMaster - webmaster@xxxxxxxxxxx
Questions? Consult the WebMaster FAQ at
http://wiki.eclipse.org/index.php/Webmaster_FAQ
View my status at http://wiki.eclipse.org/index.php/WebMaster