[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [wtp-dev] Request PMC approvals for J2EE defects
|
John,
Thx for the reference. I hope this doesn't
mean that in practice fixes will only get one PMC member looking at them.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
John Lanuti <jlanuti@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
10/10/2006 05:27 PM
|
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
|
To
| "General discussion of project-wide
or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [wtp-dev] Request PMC approvals
for J2EE defects |
|
>From David on 10/03/2006
"This morning the PMC agreed to make official something that had become
something of a defacto standard ...
committers can release a proposed fix, based on 1 positive review, as long
as they are prepared to modify it
or retract it, if other PMC members had concerns. This is to help reduce
"bottlenecks" and get it into a build quickly,
so it can be even better regression tested. "
John Lanuti
Software Engineer, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861
"Konstantin Komissarchik"
<kosta@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
10/10/2006 05:18 PM
|
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
|
To
| "General discussion of
project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [wtp-dev] Request PMC approvals
for J2EE defects |
|
David should correct my memory, but the way I remember the policy being
stated in the last several dev meetings is... a fix can be released with
only one PMC member approving, but the committer should be ready to rollback
if other PMC members object when they get a chance to review. Whether that’s
a good policy or not is a separate question.
- Konstantin
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Arthur Ryman
Sent: Tuesday, October 10, 2006 2:12 PM
To: General discussion of project-wide or architectural issues.
Cc: General discussion of project-wide or architectural issues.; wtp-dev-bounces@xxxxxxxxxxx
Subject: Re: [wtp-dev] Request PMC approvals for J2EE defects
Chuck,
I think it depends on where we are in the cycle. If we are approaching
a deadline then we need rapid response. However, as far as I understand,
we still require 3 +1 votes. The note requesting approval is timestamped
10/09/2006 03:16 PM and when I reviewed the bugs, far less than 24 hours
had elapsed. I think 48 hours is reasonable for business as usual. In my
case, yesterday was a holiday in Canada so I didn't see the request until
this morning. Also, some PMC members were travelling to the Eclipse Summit
today. Let's give people a fair chance to comment on the bugs before they
are released.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
Chuck Bridgham <cbridgha@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
10/10/2006 04:28 PM
|
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
|
To
| "General discussion of
project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [wtp-dev] Request PMC approvals
for J2EE defects |
|
Well we were told we could release because in the past getting 3 votes
wasn't timely....
Maybe some clarification is needed.
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)
Arthur Ryman <ryman@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
10/10/2006 04:18 PM
|
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
|
To
| "General discussion of
project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
|
cc
| "General discussion of project-wide
or architectural issues." <wtp-dev@xxxxxxxxxxx>, wtp-dev-bounces@xxxxxxxxxxx
|
|
Subject
| Re: [wtp-dev] Request PMC approvals
for J2EE defects |
|
Chuck,
I've been reviewing these bugs and noticed that they are being released
based on a single vote from David. I thought we required 3 votes. Has the
process changed?
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
Chuck Bridgham <cbridgha@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
10/09/2006 03:16 PM
|
Please respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx> |
|
|
To
| "General discussion of
project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [wtp-dev] Request PMC approvals for
J2EE defects |
|
The J2EE Team here in RTP has several defect ready for PMC review:
158619 maj P2
jlanuti@xxxxxxxxxx cbridgha@xxxxxxxxxx
ASSI
jst.j2ee
1.5.2 M152 PMC
performance [project creation]
Need default setting for java output f...
158623 cri P1
jlanuti@xxxxxxxxxx cbridgha@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC
[performance] ComponentDeployable members()
to recognize ...
158825 cri P1
jlanuti@xxxxxxxxxx jlanuti@xxxxxxxxxx
ASSI
wst.comm 1.5.2 M152
PMC
[emfWorkbench] Use of EMF2DOMAdapterImpl now
requires OSGI
159026 maj P2
jsholl@xxxxxxxxxx tjbishop@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC
[hotbug][j2ee] 'EAR Libraries' does not include
JAR files...
159158 cri P2
jsholl@xxxxxxxxxx jsholl@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC
[j2ee] InvertClientJARDependencyCompoundOperation
throwin...
159160 maj P2
jsholl@xxxxxxxxxx deboer@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC
[import/export] J2EE module import adds invalid
reference
160019 maj P2
cbridgha@xxxxxxxxxx cbridgha@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC performance
[modulecore] Problem with DependencyGraph timestamp checking
160226 maj P2
jsholl@xxxxxxxxxx jsholl@xxxxxxxxxx
ASSI
jst.j2ee 1.5.2 M152
PMC
[modulecore] VirtualComponent: Concurrent Modification
Ex...
links are below:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=158619
https://bugs.eclipse.org/bugs/show_bug.cgi?id=158623
https://bugs.eclipse.org/bugs/show_bug.cgi?id=158825
https://bugs.eclipse.org/bugs/show_bug.cgi?id=159026
https://bugs.eclipse.org/bugs/show_bug.cgi?id=159158
https://bugs.eclipse.org/bugs/show_bug.cgi?id=159160
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160019
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160226
Each defect has an explaination of the problem for justification, and also
a detailed explaination of the fix involved.
These defects/patches have already undergone internal review and testing,
and we'll be glad to provide any additional details if required.
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
and affiliated
entities, that may be confidential, proprietary, copyrighted
and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
