|
We have one, but just not documented. Fix bugs until the
end. Be more careful about what you fix the close we get to the
end.
The question I raised at the conf call was whether to have
RC builds. I got no feedback on that really. So we can continue with our
Mon/Wed/Fri nightly builds as release candidates?
Doug.
We are currently delinquent on our Ganymede "must dos" due to not having a
ramp down policy.
Any thoughts on what our policy should
be?
===========================
Chris Recoskie
Team Lead, IBM
CDT Team
IBM Toronto
http://www.eclipse.org/cdt
----- Forwarded by Chris Recoskie/Toronto/IBM on 05/08/2008 03:06 PM
-----
Bjorn Freeman-Benson
<bjorn.freeman-benson@xxxxxxxxxxx>
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
05/05/2008 02:12 PM
|
Please respond to
Cross
project issues
<cross-project-issues-dev@xxxxxxxxxxx> | |
|
Ganymedians,
As per a suggestion on the mailing list, I took the
opportunity today (the M7+1 date) to check the must dos conformance of the
Ganymede projects:
1. work together - unable to
verify
2. own update site - yes for everyone
3.
4 part version numbers - yes for everyone
4. use orbit - the following projects appear to have non-Orbit jars:
TENEO
(commons-logging)
There are many other non-Orbit
uses, but I can't tell if they are violations of this
must do rule because
the rule only applies to new-for-Ganymede jars.
5. true bundle form - yes
for everyone
6. correct jvm requirements - unable to
verify
7. attend planning meetings - well, the
attendance at the EclipseCon f2f was low but we haven't had any calls, so I
guess we are ok
8. watch cross projects bugzilla - unable to verify
9. rel eng communication -
N/A yet
10. joined by M4 -
yes although I recall one project joining late I can't remember which one it
was; doesn't matter now
11. ramp down policy by M6+0 - the following projects do NOT have a ramp down policy on the
wiki
BIRT
Buckminster
CDT
DLTK
DSDP
NAB
EPP
GEF
RAP
STP
Subversive (the document linked from the
wiki is not a Ramp Down Policy)
12. IP approval -
IP logs and About Files are due to Janet
by COB EDT May 15th
13. pack200 - I can't figure
out how to detect whether the jars have been conditioned for packing. Any
suggestions?
14. signed - the following projects
have unsigned jars:
DSDP-DD
DLTK
ECF
EMF (and most? all? modeling
projects)
GMF
JEM
WTP (JPT, JST,
WST)
M2M
Mylyn
RAP
STP
UML2
15.
jar'ed plugins - yes for everyone
16. message bundles - unable to verify
If you are project is
listed in (4), (11) and (14), you need to remedy this situation ASAP.
And
everyone needs to deal with the legal issues (12) before the May 15th
deadline.
- Bjorn
--
[end of message]
_______________________________________________
cross-project-issues-dev
mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
