Never mind.
You all must have used wide ranges, or something, since it appears all
still aggregates even though DTP reverted.
So, no changes from WTP required (as far as I can tell).
Thanks,
From: David M Williams/Raleigh/IBM@IBMUS
To: "General discussion of project
WTP and Dali Teams,
In case you have not been closely following bug 481095, it appears DTP
will be ready with a revert of the "major field" change for Neon M3.
(Brian Payton is, at this moment, doing yet another build to correct part
of what is mentioned in the bug -- should be done "in an
I can help with the first question.
That is the only place its used and is useful. (And, not sure its all that
useful there, any more :)
Long ago, it was a place holder to use in production builds that did
nothing, but during special test builds there would be a implementation
included that
+ 1 for Nick Sandonato for Source Editing lead (where I am a committer ...
I am not a committer for JSDT, but would vote +1 there too, if I were. :)
And, thanks to you Nitin, for your many years of leadership of both
projects.
From: Wayne Beaton wa...@eclipse.org
To:
The original creation was
https://bugs.eclipse.org/bugs/show_bug.cgi?id=379598
You could re-open or create a new bug, I'd guess.
From: Raev, Kaloyan kaloyan.r...@sap.com
To: wtp-dev@eclipse.org wtp-dev@eclipse.org,
Date: 08/27/2012 10:24 AM
Subject:[wtp-dev] WTP
Specifically, I'd like to resign from the following sub-projects:
webtools.datatools
webtools.ejbtools
webtools.jeetools
webtools.servertools
webtools.webservices
On the one hand, this make conceptual sense since I never have contributed
much to these projects, beyond fixing a few features,
[I have sent a similar note to cross project list, but in case anyone
follows wtp-dev, but not cross-project list, I'll repeat it here.]
WTP has updated to a Juno based p2 publisher so the repository it produces
will treat optional dependencies as non greedy.
See bug 247099 [1] and the p2
Heads up
As mentioned in the status meeting today, Equinox will be picking up a new
version of javax.servlet (and hence, will be in the platform we use).
This just today showed up in an Orbit I build, which will become Orbit's S
build on Friday (unless someone contributes something else
I have attempted to beef up the Target Environments section in our WTP
Plan to say a little more about platforms supported, and especially the
minimum level of Java we assume.
Please check it out, and see if this wording matches everyone's
expectations.
I mostly just want to be explicit and
Similar to the Target Environments, I am going to encourage all projects
to better specify their Compatibility with previous releases.
I went and looked at our wtp-plan.xml file to see if we provided a good
example, and it appears we have left that section of our plan completely
blank for the
The Eclipse Foundation recently added 'juno' to their list of
'simultaneousrelease' flags in their metadata for projects. I wanted to
test if some of the summary pages were working, so needed some data, so I
signed up webtools to be in Juno. No controversy there ... I hope!
By looking at
And I know there is :)
Those that depend on it tightly ... either directly from platform or WTP
or from adopter runtimes ... will want to be sure to follow or comment
on bug 360245.
360245 - javax.servlet package versions for the serlvet 3 specification
Thanks,
As promised at status and PMC meetings, I have written down a proposed
plan item for Juno related to our proposed support for 2 platforms in Juno
time-frame; it is pasted at end of this note, as well as in our standard
format plan.
As we move forward, this will be part of our overall WTP
Committers,
We currently have custom access control to our website files which are
stored in cvs, under www/webtools, as well as a custom, separate, hand
administered write access to our downloads area.
(And, its not entirely our fault ... we just got an early start, before
there were
This change is largely a technicality, but, posting here in the spirit of
being open and transparent.
Those of you that have been involved with WTP for a long time, will recall
long ago, for the first year or so, we had a datatools project in WTP,
before the committers and code there split
As I have mentioned to some of you before, I think it best we cancel the
JavaScript IDE Package. There's nothing wrong with it, and some interest
in it, judging from the 70,000 downloads for Indigo version ... but, in
the interest of economy, I think installing its few features with p2 is
not
Yes, we do have a WTP Releng Project :)
And, it is my honor to nominate Carl Anderson to become the new Lead of
that project, replacing myself. (I would continue as a committer on the
project).
Carl has taken over the main week-to-week releng duties and is poised to
guide the project as it
, that David was
referring to. :-)
FWIW,
- Carl Anderson
WTP Build guy
|
| From: |
|
--|
|David M Williams/Raleigh/IBM@IBMUS
To conclude, the committer vote has succeeded, the PMC has approved, the
EMOD has approved, and the databases and records at the Eclipse Foundation
have been updated [1].
Thank you, Angel, for your leadership over the years, and welcome, Elson,
as the new Project Lead for Server Tools.
[1]
I broke it while cleaning up milestones in preparation for release.
I can restore it, but, be warned. M7 was the last time we ever updated it.
So, I'll restore that. Adopters/builders/packagers should use the
build-specific repository URLs (and, update to latest, as new builds
become
I think we are done now. Some potential last minute problems I think
have been solved satisfactorily without us having to respin, which means
our RC4b build will become our Indigo R build next week, as we prepare
the final stages of the release.
The Helios extended maintenance release for WTP 3.2.4 is now available.
Downloads can be found at
http://download.eclipse.org/webtools/downloads/drops/R3.2.4/R-3.2.4-20110511033327/
Or obtained from the webtools repository:
http://download.eclipse.org/webtools/repository/helios
It depends
Our WTP 3.2.4 release (extended maintenance on Helios stream) was due to be
released on 5/13, this Friday.
But, our quality conscious committers found we had introduced a regression
[1] and proposed fixing it, even though it required a re-build during our
quiet week which we use as a safety
It is finally here.
http://download.eclipse.org/webtools/downloads/drops/R3.2.3/R-3.2.3-20110217214612/
Most existing installs should be able to update to this level with the
Check for Updates function, or installed directly from the common
repository at
Done. Let me know if I missed any, or you need anything else.
From: Gabriel Petrovay gabipetro...@gmail.com
To: wtp-dev wtp-dev@eclipse.org
Cc: David M Williams/Raleigh/IBM@IBMUS
Date: 02/09/2011 01:06 PM
Subject:Can we have some more milestone tags in Bugzilla?
Hi
, to test they are downloadable, installable, etc.
Thanks to everyone for making this candidate (and release) possible. I
think the ramp-down went well, and appreciate everyone reacting to the
last minute churn to move to the new compiler version.
From: David M Williams/Raleigh/IBM@IBMUS
Committers and adopters,
please test the latest EPP Packages and software repositories. Especially
look for regressions in Helios SR2 candidates since we are nearly done
(that is, we do not plan to fix too many more known bugs for SR2, but
would if anyone soon reports a bad regression). Note:
Hard to believe we are up to 6 ... but if I can count right, we are. I've
created a bare outline document at
http://wiki.eclipse.org/New_Help_for_Old_Friends_VI
I have included subproject headings similar to what we've had before ...
but feel free to remove, add, or edit how ever you'd like.
I'll paste below what are currently the 19 sdk features we build from our
3 build-time-assembly features. We currently build only sdk features and
they of course pull in runtime and source (and doc) features. It appears
we end up with 102 features in current builds (which surprises even me!).
Apologies for the error, but a typo (that I made) in the cross-project
SimRel calendar (bug 335184) got carried over into our WTP calendar as
well.
This means our Indigo M5 +2 date is 2/1 (instead of 2/8) which means our
final build for M5 is this week, not next. I hope everyone can adjust
Since we didn't meet last week, after this first announcement, I thought
it'd be worth one more reminder that our status call number has changed.
Talk to you this afternoon.
From: David M Williams/Raleigh/i...@ibmus
To: wtp-pmc wtp-...@eclipse.org, wtp-dev@eclipse.org
Date: 11/21
Is this the same as bug 168556? (Just curious ... your question would
still be valid, and in need of an answer, either way ... but if same,
perhaps could be discussed there ... or a new bug open, if a different
startup participant.
From: Cameron Bateman cameron.bate...@oracle.com
To:
Its been mentioned on this list before, but now it is being implemented
this week.
Instead of the 6 archived p2 repositories that we have been making
available with each build, I plan to package things up into only two.
One would be all the WTP code (executable, and SDK features) and
cases (it depends
a bit on exactly how and what is installed in current IDE).
In any case, greatest thanks to you all ... committers and users!
From: David M Williams/Raleigh/i...@ibmus
To: wtp-dev@eclipse.org, wtp-dev@eclipse.org
Date: 09/24/2010 03:50 PM
Subject:[wtp-dev
tweak the download page to put final URLs for our pre-reqs.
This final download page will not be linked from main download page until
release day, 9/24.
Thanks,
From: David M Williams/Raleigh/i...@ibmus
To: wtp-dev@eclipse.org, wtp-dev@eclipse.org
Date: 09/16/2010 02:35 AM
Subject
Just to keep everyone informed, we in WTP caught a last minute regression
(caused by a last minute fix) so we are going to respin our final build.
The change involves how previous version EJB projects are handled and
shouldn't effect downstream consumers, or require anyone to rebuild or
We (the WTP PMC and Source Editing Project) wanted to be sure to
communicate well to
the community that our upcoming service release will contain preliminary
source editing
support for HTML5. See bug 292415.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=292415
We wanted to announce this on
used in Bugzilla account? Have
I somehow mangled the name?
Thanks,
From:
David M Williams/Raleigh/i...@ibmus
To:
WTP Incubator Dev list wtp-incubator-...@eclipse.org
Cc:
General discussion of project-wide or architectural issues.
wtp-dev@eclipse.org
Date:
08/12/2010 04:34 PM
Subject:
RE
Thanks for this proposal. I wanted to keep you (and community) up to date.
The proposal looks good but one of the people wanting to review it more
is on vacation, so I'd like to be polite and give him a chance to get back
and comment further, if he has any further comments. We should get that
Many thanks to the committers for fixing the few compile errors when
building against 4.0 this week. Such as, see
http://build.eclipse.org/webtools/committers/wtpe4-R3.3.0-I/20100812113302/I-3.3.0-20100812113302/
And while we haven't done unit tests or full smoke tests yet, we do have
some
I've marked 3.2.1 as complete.
And, changed the repository to
http://download.eclipse.org/webtools/repository/helios
as that is the most current and moving forward repository.
The old http://download.eclipse.org/webtools/updates/ will be left in
place for a long time, as that has some old
wait and someday we'll have a more focused effort and do a more
complete cleanup, instead of asking webmasters for a few at time. Hope
they are not too confusing in the meantime.
Thanks,
From:
Gabriel Petrovay gabipetro...@gmail.com
To:
wtp-dev wtp-dev@eclipse.org, David M Williams/Raleigh
Do we expect that the 3.2.1 release appears on the WTP update site too?
Yes and no.
Yes, it will be added to the webtools specific repository, at
http://download.eclipse.org/webtools/repository/helios/
once we officially release, on Friday.
But, not the common repo at
Well, Happy Birthday, Canada. :)
And thanks for the warning. I actually had this on my calendar but failed
to think through the significance until now.
And, the significance (in this context) is that Thursday is also our
planned day for our first declared 3.2.1 build, which, as always,
Earlier today I agreed to post some information about Eclipse 4.0. Last I
heard, they are still planning an Early Adopter release the end of July
(RC1 is this week).
As discussed in status meetings, the hope is that in WTP 3.3 our plugins
will work with both 4.1 and 3.7 (both planned for
Thanks Dave! And Mukul and Jesper. This is community building at its
best!
From:
David Carver d_a_car...@yahoo.com
To:
General discussion of project-wide or architectural issues.
wtp-dev@eclipse.org
Date:
06/19/2010 12:30 PM
Subject:
[wtp-dev] Fwd: [ANNOUNCEMENT]: Apache Xerces-J 2.10.0
How embarrassing.
Despite all the tools and tests we've added to fix and check license
files, one bug has gone unnoticed until now.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=316979
The files were there in cvs ... but the build.properties not updated to
include them.
I think the only
This note only concerns the (traditional) zip file name for the web
development subset
of features. In putting some final touches on the build (bug 315919), it
was easier (and safer) to use some
common scripts, and accept the default name for the zip files ... rather
than try and special case
It is far later than it should be, to be making this kind of change, so I
am sending this notice to wtp-dev list and cross-project list to make sure
it gets proper visibility.
In WTP, the JEE and the JSF subprojects have regrouped a set of JSF
bundles that used to be mingled in with the JEE
Lance,
subversion hasn't really caught on at Eclipse (though a few projects
happily use it) and now GIT is considered the future at Eclipse (if not
next generation).
But I can not imagine what led you to this mailing list to ask this
question.
You'll probably want to read some of the new
Yes, we intentionally have not, in the past, maintained any old builds at
the update site repository.
We will start doing so (at a different repository URL) for Helios.
They are still at archives.eclipse.org, in various zip file distributions.
Thanks,
From:
Gabriel Petrovay
Thanks for letting us know, Gabriel, and opening the bug. In the mean
time, I can offer two tips that might help, now, and even routinely.
1) I recently learned you can use ext (extssh) with your committer id even
for projects where you are not a committer. You can't write to them (of
course)
We do, for one. See
http://wiki.eclipse.org/WTP_Capabilities_Helios
I've written this document to comply with simultaneous release
requirements. And, we do make use of them in the Java EE IDE package (or,
will, in M7).
I'm posting this here for general awareness, especially for WTP
assuming no at this point.
Best Regards,
-- --
Mr. Angel Vera
Server Tools Developer
E-Mail: arv...@ca.ibm.com
Tel: 905-413-5919
-
Those who think that something is impossible,
should not interfere with those who are willing to do it. - Angel Vera
From:
David M Williams david_willi
Anyone?
If so, there's a few issues to work out and test, etc.
1. The bundle in orbit was split up from what 2.0 used to be. So to get
it all we'll need to get several new bundles.
For details, see
http://dev.eclipse.org/mhonarc/lists/orbit-dev/msg01739.html
I'll need you experts (Nitin?,
I'm not sure what that means. :-) I guess I'm supposed to unzip
them and see what happens?
Where 'ya been? :)
Off hand, I'm not sure where this is documented well, but there's a lot of
mailing list and bugzillas about them. They are exactly like
a repository you'd get via HTTP, but zipped
I completely forgot to mention during status meeting yesterday ...
I think we should skip the usual weekly status call on Thursday, 3/25,
since several of us will be at EclipseCon.
But if someone still wants it, let us know. And feel free to ask questions
or raise issues on mailing lists ...
. :)
I hope others can report success or similar problems and maybe get the
issues narrowed down. As far as I know, there could be order effects, or
something.
Thanks, David!
Brian
[attachment p2.JPG deleted by David M Williams/Raleigh/IBM]
___
wtp-dev
After I promoted this build, I thought to renamed it to reflect that is it
M2, so its download URL is now
http://download.eclipse.org/webtools/downloads/drops/R0.7.0/S-0.7.0M2-20100317233124/
From:
David M Williams/Raleigh/i...@ibmus
To:
wtp-dev@eclipse.org
Date:
03/18/2010 01:31 PM
Subject
but I rather release the changes now than having to file for an
exception in M7 and give the PMC more work in M7
I'm not saying if releasing this potentially breaking change the last week
of M6 is a good or bad thing to do ... that's mostly between your project
committers and adopters,
but I
for our new website, that is.
http://dev.eclipse.org/blogs/eclipsewebmaster/2010/03/04/have-you-seen-the-new-webtools-website/
Now all we have to do is get content that equals the graphics :)
Thanks Naci and Ugur
___
wtp-dev mailing list
: [wtp-dev] Webservices Committers: need vote for JAX-WS Move Valentin
Baciu
Re: [wtp-dev] Webservices Committers: need vote for JAX-WS Move Keith
Chong
[wtp-dev] Webservices Committers: need vote for JAX-WS Move David M
Williams
This will become formally effective after the Move Review
I just wanted to give some warning that the structure of the download
pages has changed so that the zipped p2 repositories have moved up on
the page, above the traditional zips.
This is to encourage their use, over time, but may cause some confusion at
first, if anyone just downloads them and
For those of you going to EclipseCon this month, I have reserved a time
and
place we can meet to discuss WTP.
It will be Tuesday evening, 6 to 7 (local, Pacific time) in the Central
room (it is on the second floor of the Hyatt).
To check some build changes I made, I was building everything this
evening, and was surprised Pave has a bunch of compile errors ...
unrelated to my changes, I think looks more like some non-API use of
something in one of the prereqs changed.
I wasn't all that surprised by compile
Its probably supposed to be their 1.7.2 RC3 candidate. I blindly updated
our page based on what was in their released download directory.
Same question was asked on cross-project and I suspect they'll answer
and update soon I'll update ours so nothing shows up, until they
get current.
Webservices Committers,
I hope you all know by now that the JAX-WS team has formally applied to
move from the WTP Incubator Project to the Webservices Project, where it
will plan to Release with Helios, in June.
They have been well integrated with WTP's builds, processes, and weekly
rhythm,
I have update our WTP retention policy, found at
http://wiki.eclipse.org/WTP/Retention_Policy
The substantial change was that our update site repositories will now
exist forever, to line up with current recommended practice.
This is partially a result of the Equinox Team twisting my arm ...
If you are able, please help test the probably final Java EE IDE Packages.
Today (Friday) is best, but anytime before next Wednesday would be
helpful.
(If a bad problem is found, at least we'd know about it before the
release).
Currently, it is the 20100218-1611 build on
Congratulations!
One thing that's next is the bugzilla components. The jsdt and javascript
that's in WTP Source Editing product can (and should) be moved to the
new JSDT product. (I know, it's nice seeing no bugs, eh? :)
The webmasters can help with that. Just open a bug under 'community',
It was last release too ... or do you mean you see something new?
There are functions in RSE to SSH to remote servers, copy files from
workspace to or from a remote machine. These are things that many (or, at
least some) web developers do, so seemed like a natural way to include
some useful
it’s a positioning issue, but unlike Mylyn,
it’s not immediately obvious that RSE has general applicability.
- Konstantin
From: wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] On
Behalf Of David M Williams
Sent: Monday, February 08, 2010 11:07 AM
To: General discussion
Konstantin Komissarchik has resigned his role as WTP Common Project
Lead, due to increasing time commitments in other areas of his work. We
thank him for his many, great, past contributions to WTP ... and his
future ones! He will remain as a committer, and we sincerely look
forward to continuing
The later.
emf.validation is a pre-req of only JAXWS features, which is in only WTP
3.2.
I've opened bug 301591 to track repair of web page that is generated
during a build.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=301591
From:
Konstantin Komissarchik
Tough one to track down. Well, I'm still guessing a little, but I think
its related to JUnit 3 vs. 4, maybe complicated by the fact you are still
running (mostly) with Galileo pre-reqs.
But, to guess ... I notice you added back tight ranges for JUnit
pre-req, e.g.
Today is the deadline for marking intent to participate in Simultaneous
Release.
webtools.dali
webtools.sourceediting
webtools.webservices
where's server tools? jsf? jee? ejb? common?
For any of you not at the status meeting yesterday, this is requested by
the EMO as the formal mechanism
For those of you that don't follow cross-project list ... it is now
official!
Greatest thanks for making our WTP M4 so easy for me ...
Happy New Year!
- Forwarded by David M Williams/Raleigh/IBM on 12/18/2009 12:46 PM
-
From:
Markus Knauer mkna...@eclipsesource.com
To:
EPP
lists, since that's
primarily for committers and adopters. If casual (but brave) end-users
went to get M4 now, they might be confused to find the final M4 of
Platform, EMF, etc., are not even ready yet.
Thanks,
From:
David M Williams/Raleigh/i...@ibmus
To:
wtp-dev@eclipse.org
Date:
12/10
Or all of the above?
With the recent notes about the inclusion of org.junit version 4, and from
following several bugs, I got the impression that we _had_ to make the
kind of adjustments so well described in
http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes or else our tests
would fail.
At our status meeting last week, we decided we would not have a declared
build this week, since so many were out on holiday.
But a few days after the meeting, some committers (not in the US :) said
they would like a build promoted to 'downloads' to enable some early
adopter testing and
During this week's status meeting, I'd like to decide what to do about
next week's I-build and status meeting.
Thursday, 11/26, is a holiday in the US, and some people take off several
days of the week, if not all week.
So, I'd like to propose we skip having a declared I-build and status
From a quick look, these are the performance test bundles we still
compile each build, but never use.
./org.eclipse.jst.j2ee.core.tests.performance
./org.eclipse.jst.j2ee.tests.performance
./org.eclipse.jst.jsp.ui.tests.performance
./org.eclipse.jst.server.tomcat.tests.performance
Sorry to say we needed a respin for 3.1.1 after all. One of the blocking
hotbugs we fixed for this release
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=287096) had a small flaw
that rendered it useless in context and unfortunately
this error was not discovered until just today. I think there
WTP Committers and Community,
I have written a new hotbug process document. See
http://wiki.eclipse.org/WTP/Hotbug_Policy
My intent was to clarify the process to avoid some common misconceptions I
have heard,
as well as make it match more closely what we actually, currently do with
just rename it to an S build.
So, no reason for committers to hold off on further commits today (Yes,
that includes you, Carl :)
But I wanted to warn adopters that this declared S-build is not quite our
final M1. I'll re-declare another S-build once it's ready.
Thanks,
From:
David M
if you just look at the main download URL
http://download.eclipse.org/webtools/downloads/
... just in case case anyone wants signed content, or or something.
Sorry for the churn.
From:
David M Williams/Raleigh/i...@ibmus
To:
wtp-dev@eclipse.org
Date:
08/14/2009 05:48 PM
Subject:
[wtp-dev
Thanks Dave and Mukul for letting us know.
My personal apologies for not talking to you first-hand about this before
the announcement. But, given the talks with everyone else, we (the PMC)
knew the decision about WTP as a whole would not change based on the few
committers we had not talked to
I believe they are all in sse.core, e.g.
/org.eclipse.wst.sse.core/DevTimeSupport/SedModel/CSSTokenizer/devel/CSSTokenizer.jflex
From:
Roy Ganor r...@zend.com
To:
wtp-dev@eclipse.org
Date:
08/12/2009 11:15 AM
Subject:
[wtp-dev] CSSTokenizer CVS location
Sent by:
wtp-dev-boun...@eclipse.org
After discussions with Committers and Adopters, the WTP PMC has
decided that WTP as a whole will not have a December Release, as
originally planned. Thus, WTP 3.2 will be in June, 2010, as part of
the Helios Simultaneous Release.
The original reason for the off-cycle release was to release some
Do you have a need/interest that is specific to Web Tools and JDK7? I'm
curious.
Unless there is some web related feature in JDK 7 you are asking about,
I'd suggest you ask on the Eclipse Platform newsgroup, or the JDT
newsgroup. I didn't look very hard, but found one related, but old,
Ready to crank it up again?
I suggest we start having declared weekly I-build starting this week
(which means tomorrow; back to the no-code-Thursdays rhythm).
I'll issue a smoke test request tomorrow (Thursday) morning and if anyone
has trouble complying due to short notice, just say so.
Remember there is no status meeting today, 6/25, nor next week, 7/2. If
there's any questions or issues that come up, please just ask on one of
our lists.
In our next meeting, 7/9, we'll spend some time having a software
postmortem for our Galileo release; try and capture any facts about the
Upgrading to Galileo from 3.4.2 (or WTP 3.0.4) is not supported.
I recommend you start with one of the distributions at
http://www.eclipse.org/downloads/
such as Eclipse IDE for Java EE Developers
and then install other things, if not provided in that distribution.
HTH
From:
Campbell,
Message-
From: wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org]
On Behalf Of David M Williams
Sent: Thursday, June 25, 2009 1:59 PM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Trouble updating
Upgrading to Galileo from 3.4.2 (or WTP
I hope it's just me ... but I tested for about an hour on two platforms
and immediately found 3 bugs!
All of them bad, even if a few are probably intermittent.
279191 JEE Preview Server won't start
279193 NPE while programmatically switching to console view
279195 Debug breakpoints don't break
and Tools Usability sections in
the document.
I did it in the odt version in CVS. Hopefully all other potential
editors were asleep at that very moment.
Greetings,
Kaloyan
-Original Message-
From: wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org]
On Behalf Of David M
I've made a first pass at or Release Review docuware, but now need to ask
other PMC members and Project Leads to review and fix up your special
sections:
A web version is visible at
http://www.eclipse.org/webtools/releaseReviews/200906/WebTools3.1.pdf
and you can find/edit the 'odt' version
We accounted for Memorial Day (U.S.) in our calendar, but I've just
learned that Canada has holidays too!
One of them, Victoria Day, is on Monday, the 18th.
So, I think it best if we skip Monday and just plan on doing the tests
and signoffs on Tuesday 19th, as we will for Memorial day, the
I guess it is ridiculously late to request you update test documentation,
so I will leave it up to each subproject if you do or do not -- or, maybe
you already have! But, I did at least create a 3.1 page, and just copied
over the content from the 3.0 page.
Why, that is answered right here:
http://wiki.eclipse.org/WTP/Retention_Policy
Which I just put there. I would have sworn we had one written somewhere,
but I couldn't find it. So wrote that new one.
I think it's the kind of policy we all sort of know and understand, but
have never written
1 - 100 of 497 matches
Mail list logo
