Hi Jim,
I’m interested in contributing to
the top-to-bottom review, so you can put me on the list.
Best Regards,
Onno
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Ruehlin
Sent: dinsdag 15 augustus 2006
22:53
To: epf-dev@xxxxxxxxxxx
Subject: RE: [epf-dev]
Architecture Content Completed
Based on what we agreed on at the last
committers meeting, if the content has gone through an initial (informal)
review, then it can be changed Verified – Fixed in Bugzilla (after the
appropriate changes have been made). This review should include making sure the
content conforms to the published guidelines.
The next step is to make sure the content
is consistent across the process and robust enough for use. This second (formal)
review should include the package owner, and probably someone from outside the
discipline to give a different perspective. The Bugzilla entry can be changed
to Closed after the changes have been made from this review.
In addition to those steps we’ve agreed
to, there should be a top-to-bottom review of the process before final
committer approval of version 1.0. We should enlist people who are monitoring
this list but who haven’t contributed yet. Anyone interested? J
- Jim
____________________
Jim Ruehlin, IBM
Rational
RUP Content
Developer
Eclipse Process
Framework (EPF) Committer
email:
jruehlin@xxxxxxxxxx
phone:
760.505.3232
fax:
949.369.0720
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Mark.Dickson@xxxxxxxxx
Sent: Tuesday, August 15, 2006
11:12 AM
To: "Epf"
<epf-dev@xxxxxxxxxxx>
Subject: Re: [epf-dev]
Architecture Content Completed
Hi Ricardo
I've recently asked Brian and Per for guidance on closure. No answer yet but
I'm happy to close bugs if that's the process.
As for the references issue - yes, I'm familiar with what your saying, as I
added a bunch of references to the general package over the weekend. I
obviously missed a couple, so thanks for spotting those.
Cheers
Mark
Mark Dickson
SE&E Practice
Xansa
0780 1917480
*** sent from my blackberry ***
----- Original Message -----
From: Ricardo Balduino
[balduino@xxxxxxxxxx]
Sent: 15/08/2006 19:03
To: Eclipse Process Framework
Project Developers List <epf-dev@xxxxxxxxxxx>
Subject: Re: [epf-dev]
Architecture Content Completed
Mark, I know we briefly mentioned something in the Architecture call
this morning, but I was wondering if the process is to have each package owner
conducting the required reviews to close the bugs in Bugzilla, as opposed to
relying in one person (as content leadership/ownership has been sliced and
shared).
Regarding
the current entries for Architecture in Bugzilla, I found minor things we can
do to keep consistent with other areas, like removing 'Reference' sections from
the text and creating links to the appropriate guidance References, under
General package. As I found this change specific to some elements, I reopened
the related bugs, but I guess if that behavior is generalized, we could open a
new bug instead, as you suggested below. Let's sync up on this, please.
Cheers,
Ricardo Balduino
Senior Software Engineer
IBM - RUP Team | EPF Committer
www.ibm.com/rational
www.eclipse.org/epf
Mark.Dickson@xxxxxxxxx
Sent
by: epf-dev-bounces@xxxxxxxxxxx
08/15/2006
09:37 AM
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx>
|
|
To
|
epf-dev@xxxxxxxxxxx
|
cc
|
|
Subject
|
[epf-dev] Architecture Content Completed
|
|
Hi
The Architecture content is pretty much done and
verified. We might get a
few more issues as people move through the content
from an
"integration/system test" perspective - if
so, can I ask that new bugzilla
entries are raised against these specific issues?
I have left the completed bugzillas as
"Verified" where I believe they
comply with authoring and style guidelines, etc.
My guess is that Brian (as
OpenUP content lead) should decide when to move
bugs to "Closed" as it
gives us a final "we're really, really
sure" status code we can move
through if needed.
This means that we don't need to have any
Architecture Content status calls
anymore unless we really have to. I'll cancel the
ones already in the Yahoo
calendar. If we need one in the future then we can
schedule one up to suit
the occasion.
Finally, "thank you" to everyone who has
helped with the Architecture
content so far, especially Ana Valente Pereira,
Chris Doyle, Ricardo
Balduino and Jim Ruehlin.
cheers
Mark
Mark Dickson
Principal Solution Architect
SAE Practice
m 0780 1917480
w www.xansa.com
e mark.dickson@xxxxxxxxx
Whilst this email has been checked for all known
viruses, recipients should undertake their own virus checking as Xansa will not
accept any liability whatsoever.
This email and any files transmitted with it are
confidential and protected by client privilege. It is solely for the use
of the intended recipient.
Please delete it and notify the sender if you have
received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of
the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames
Valley Park,
Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Whilst this email has been checked for all known viruses, recipients should
undertake their own virus checking as Xansa will not accept any liability
whatsoever.
This email and any files transmitted with it are confidential and protected by
client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420
Thames Valley Park Drive,
Thames Valley
Park, Reading, RG6 1PU,
UK.
Registered in England
No.1000954.
t +44 (0)8702 416181
w www.xansa.com
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev