Skip to content

Commit a54b4aa

Browse files
elsazacelsazac
committed
Project Plan for Eclipse SDK 4.35 release.
1 parent 6adf280 commit a54b4aa

File tree

1 file changed

+388
-0
lines changed

1 file changed

+388
-0
lines changed

‎development/plans/eclipse_project_plan_4_35.xml‎

Lines changed: 388 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,388 @@
1+
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
2+
<!-- Use this to test local rendering in firefox. Comment out this line once this plan is linked to portal data. -->
3+
<?xml-stylesheet type="text/xsl" href="project-plan-render.xsl"?>
4+
5+
<!-- <?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?> -->
6+
7+
<p:plan
8+
plan-format="1.0"
9+
xmlns:p="http://www.eclipse.org/project/plan" xmlns="http://www.w3.org/1999/xhtml"
10+
name="Eclipse Project">
11+
12+
<p:release projectid="eclipse" version="2025-03"/>
13+
14+
<!-- ============================================== -->
15+
16+
<p:introduction>
17+
<div>
18+
<p>
19+
Last revised January 06, 2025.
20+
21+
22+
</p>
23+
<p><i>Please send comments about this plan to the</i> <a href="mailto:[email protected]">[email protected]</a> <i>developer
24+
mailing list.</i>
25+
</p>
26+
<p>This document lays out the feature and API set for the next feature release
27+
of the Eclipse SDK after 4.34, designated release 4.35 and code-named 2025-03.
28+
</p>
29+
30+
<p>The first part of the plan deals with the important matters of release deliverables,
31+
release milestones, target operating environments, and release-to-release compatibility.
32+
These are all things that need to be clear for any release, even if no features
33+
were to change. </p>
34+
<p>Not all plan items represent the same amount of work; some may be quite large,
35+
others, quite small. Some plan items may involve work that is localized to
36+
a single component; others may involve coordinated changes to several components;
37+
other may pervade the entire SDK. Although some plan items are for work that
38+
is more pressing than others, the plan items appear in no particular order. </p>
39+
<p>With the previous release as the starting point, this is the plan for how
40+
we will enhance and improve it. Fixing bugs, improving test coverage, documentation,
41+
examples, performance tuning, usability, etc. are considered routine ongoing
42+
maintenance activities and are not included in this plan unless they would
43+
also involve a significant change to the API or feature set, or involve a significant
44+
amount of work. The intent of the plan is to account for all interesting feature
45+
work. </p>
46+
47+
</div>
48+
</p:introduction>
49+
50+
<!-- ============================================== -->
51+
52+
<p:release_deliverables>
53+
<div>
54+
55+
<p>The release deliverables have the same form as previous releases, namely: </p>
56+
<ul>
57+
<li>Source code release for all Eclipse Project deliverables, available as
58+
versions tagged &quot;R4_35&quot; in the Eclipse Project Git
59+
repositories <a href="https://github.com/eclipse-equinox/">Equinox</a>, <a href="https://github.com/eclipse-jdt/">JDT</a>,
60+
<a href="https://github.com/eclipse-pde/">PDE</a> and <a href="https://github.com/eclipse-platform/">Platform</a>.</li>
61+
<li>Eclipse SDK (runtime binary and SDK for Equinox, Platform, JDT, and PDE) (downloadable).</li>
62+
<li>Eclipse Equinox (runtime and source repositories) (downloadable).</li>
63+
<li>Eclipse Platform (runtime and source repositories) (downloadable).</li>
64+
<li>Eclipse ECJ (runtime and source for the Eclipse Compiler for Java) (downloadable).</li>
65+
<li>Eclipse PDE (Installable from repository for the Plug-in Development Environment).</li>
66+
<li>Eclipse SDK Examples (Installable from repository).</li>
67+
<li>SWT distribution (downloadable).</li>
68+
</ul>
69+
70+
71+
</div>
72+
</p:release_deliverables>
73+
74+
<!-- ============================================== -->
75+
76+
<p:release_milestones>
77+
78+
<p:preamble><p>
79+
Release milestones will be occurring at roughly 6 week intervals, and will be aligned with the
80+
<a href="https://github.com/eclipse-simrel/.github/blob/main/wiki/SimRel/2025-03.md">
81+
2025-03 Simultaneous Release</a> train.</p>
82+
</p:preamble>
83+
<p:milestone date="2025-01-03" milestone="M1"><div>4.35 M1</div></p:milestone>
84+
<p:milestone date="2025-01-24" milestone="M2"><div>4.35 M2 (only submit I-build)</div></p:milestone>
85+
<p:milestone date="2025-02-14" milestone="M3"><div>4.35 M3 - <b>Release Record Deadline</b></div></p:milestone>
86+
<!--
87+
NOTE: This is only necessary once per year. For us with the 202x-03 release.
88+
<p:milestone date="2023-11-18" milestone=""><div>IP Log Submission Deadline</div></p:milestone>
89+
-->
90+
<p:milestone date="2025-02-21" milestone="RC1"><div>4.35 RC1 - <b>API and feature freeze</b></div></p:milestone>
91+
<!--
92+
NOTE: This is only necessary once per year. For us with the 202x-03 release.
93+
<p:milestone date="2023-11-25" milestone=""><div>Review Material Submission Deadline</div></p:milestone>
94+
-->
95+
<p:milestone date="2025-02-28" milestone="RC2"><div>4.35 RC2 - <b>New and Noteworthy Material Deadline</b></div></p:milestone>
96+
<p:milestone date="2025-03-12" milestone="GA"><div>4.35 GA</div></p:milestone>
97+
98+
<p:postamble>
99+
<div>
100+
<p>Our target is to complete 4.35 in March 2025.
101+
All release deliverables will be available for download as soon as the release has been
102+
tested and validated in the target operating configurations listed below.</p>
103+
<p>PMC approval is required for API changes and additions after M3.</p>
104+
</div>
105+
</p:postamble>
106+
107+
</p:release_milestones>
108+
109+
<!-- ============================================== -->
110+
111+
<p:target_environments>
112+
113+
<div>
114+
<p>In order to remain current, each Eclipse Project release targets reasonably current
115+
operating environments.</p>
116+
<p>Most of the Eclipse SDK is &quot;pure&quot; Java code and has no direct dependence
117+
on the underlying operating system. The chief dependence is therefore on the
118+
Java Platform itself. Portions are targeted to specific classes of operating
119+
environments, requiring their source code to only reference facilities available
120+
in particular class libraries (e.g. Java 21, Java 22, etc).</p>
121+
<p>
122+
In general, the 4.35 release of the Eclipse Project is developed on Java SE 21 VMs.
123+
As such, the Eclipse SDK as a whole
124+
is targeted at all modern, desktop Java VMs. Most functionality is available for
125+
Java SE 21 level development everywhere, and extended development capabilities are made
126+
available on the VMs that support them.</p>
127+
<p>There are many different implementations of the Java Platform running atop
128+
a variety of operating systems. We focus our testing on a handful of
129+
popular combinations of operating system and Java Platform; these are our <em>reference
130+
platforms</em>. Eclipse undoubtedly runs fine in many operating environments
131+
beyond the reference platforms we test. However, since we do not systematically test
132+
them we cannot vouch for them. Problems encountered when running Eclipse on a
133+
non-reference platform that cannot be recreated on any reference platform will
134+
be given lower priority than problems with running Eclipse on a reference platform.</p>
135+
<p>Eclipse 4.35 is tested and validated on the following reference platforms
136+
(this list is updated over the course of the release cycle):</p>
137+
<style type="text/css">
138+
table.platforms {
139+
border-width: 1px;
140+
border-spacing: 0px;
141+
border-style: solid;
142+
border-collapse: separate;
143+
}
144+
table.platforms th {
145+
border-width: 1px;
146+
padding: 3px;
147+
border-style: inset;
148+
border-color: black;
149+
background-color: #B9A9FF;
150+
}
151+
table.platforms td {
152+
border-width: 1px 1px 1px 1px;
153+
padding: 3px 3px 3px 3px;
154+
border-style: inset inset inset inset;
155+
border-color: gray gray gray gray;
156+
}
157+
table.platforms tr.c0 td {
158+
background-color: #FDFDFD;
159+
}
160+
table.platforms tr.c1 td {
161+
background-color: #F4EEFF;
162+
}
163+
</style>
164+
<center>
165+
<table class="platforms">
166+
<tr>
167+
<th>Operating System</th>
168+
<th>Version</th>
169+
<th>Hardware</th>
170+
<th>JRE</th>
171+
<th>Windowing System</th>
172+
</tr>
173+
<!-- ************ WINDOWS ************** -->
174+
<tr class="c0">
175+
<td rowspan="1">Windows</td>
176+
<td rowspan="1">
177+
10<br/>
178+
11
179+
</td>
180+
<td rowspan="1">x86 64-bit</td>
181+
<td rowspan="1">
182+
OpenJDK 21.0.5 (LTS)<br/>
183+
Oracle Java 21.0.5 (LTS)<br/>
184+
</td>
185+
<td rowspan="1">Win32</td>
186+
</tr>
187+
<!-- ************ RHEL ************** -->
188+
<tr class="c1">
189+
<td rowspan="2">Red Hat Enterprise Linux</td>
190+
191+
<td rowspan="2">9.5
192+
</td>
193+
<td rowspan="1">
194+
x86 64-bit<br/>
195+
aarch64<br/>
196+
</td>
197+
<td rowspan="1">
198+
OpenJDK 21.0.5 (LTS)<br/>
199+
Oracle Java 21.0.5 (LTS)<br/>
200+
</td>
201+
<td rowspan="2">GTK 3</td>
202+
</tr>
203+
<tr class="c1">
204+
<td rowspan="1">Power 64-bit LE</td>
205+
<td rowspan="1">
206+
OpenJDK 21.0.5 (LTS)<br/>
207+
</td>
208+
</tr>
209+
<!-- ************ SLES ************** -->
210+
<tr class="c0">
211+
<td rowspan="2">SUSE Linux Enterprise Server</td>
212+
<td rowspan="2">
213+
15 SP6
214+
</td>
215+
<td rowspan="1">x86 64-bit</td>
216+
<td rowspan="1">
217+
OpenJDK 21.0.5 (LTS)<br/>
218+
</td>
219+
<td rowspan="2">GTK 3</td>
220+
</tr>
221+
<tr class="c0">
222+
<td rowspan="1">Power 64-bit LE</td>
223+
<td rowspan="1">
224+
OpenJDK 21.0.5 (LTS)<br/>
225+
</td>
226+
</tr>
227+
228+
<!-- ************ Ubuntu ************** -->
229+
<tr class="c1">
230+
<td rowspan="1">Ubuntu Long Term Support</td>
231+
<td rowspan="1">24.04</td>
232+
<td rowspan="1">
233+
x86 64-bit<br/>
234+
aarch64<br/>
235+
</td>
236+
<td rowspan="1">
237+
OpenJDK 21.0.5 (LTS)<br/>
238+
</td>
239+
<td rowspan="1">GTK 3</td>
240+
</tr>
241+
242+
<!-- ************ Mac ************** -->
243+
<tr class="c1">
244+
<td rowspan="2">Apple macOS</td>
245+
<td rowspan="1">
246+
13<br/>
247+
14<br/>
248+
15
249+
</td>
250+
251+
<td rowspan="1">x86 64-bit</td>
252+
253+
<td rowspan="1">
254+
OpenJDK 21.0.5 (LTS)<br/>
255+
Oracle Java 21.0.5 (LTS)<br/>
256+
</td>
257+
258+
<td rowspan="2">Cocoa</td>
259+
</tr>
260+
<tr class="c0">
261+
<td rowspan="1">
262+
13<br/>
263+
14<br/>
264+
15
265+
</td>
266+
<td rowspan="1">
267+
M1 (arm64)
268+
</td>
269+
<td rowspan="1">
270+
OpenJDK 21.0.5 (LTS)<br/>
271+
</td>
272+
</tr>
273+
</table>
274+
</center>
275+
276+
<p>As stated above, <i>we expect that Eclipse works fine on other current
277+
Java VM and OS versions but we cannot flag these as reference platforms without
278+
significant community support for testing them.</i></p>
279+
<p>With respect to GTK 3 versions: the <i>required</i> version of GTK 3 which Eclipse SDK 4.35
280+
will run on is 3.22 or newer.
281+
</p>
282+
283+
<p>With respect to GTK 3 themes: Adwaita theme is guaranteed to work. Eclipse SDK will run with other GTK 3 themes,
284+
however we cannot flag these as reference versions without significant community support for testing and/or development
285+
of fixes. Bugs that are reproducible only with themes other than Adwaita will be given a lower priority (or may not be fixed at all),
286+
compared to bugs which are reproducible on the target environments listed above.
287+
</p>
288+
</div>
289+
290+
<p:internationalization>
291+
<p>The Eclipse SDK is designed as the basis for internationalized products. The
292+
user interface elements provided by the Eclipse SDK components, including dialogs
293+
and error messages, are externalized. The English strings are provided as the
294+
default resource bundles.</p>
295+
<p>Latin-1, DBCS, and BiDi locales are supported by the Eclipse SDK on all reference platforms.</p>
296+
<p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard,
297+
on Windows, Linux and the Macintosh.</p>
298+
</p:internationalization>
299+
300+
</p:target_environments>
301+
302+
<!-- ============================================== -->
303+
304+
<p:compatibility_with_previous_releases>
305+
<div>
306+
307+
<h3>Compatibility of Release 4.35 with 4.34</h3>
308+
<p>Eclipse 4.35 will be compatible with Eclipse 4.34</p>
309+
310+
<p><strong>API Contract Compatibility:</strong> Eclipse SDK 4.35 will be upwards
311+
contract-compatible with Eclipse SDK 4.34 except in those areas noted in the
312+
<a href="https://help.eclipse.org/2025-03/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_35_porting_guide.html" target="_top">
313+
<em>Eclipse 4.35 Plug-in Migration Guide</em>
314+
</a>. Programs that use affected APIs and extension points will need to be ported
315+
to Eclipse SDK 4.35 APIs. Downward contract compatibility
316+
is not supported. There is no guarantee that compliance with Eclipse SDK 4.35
317+
APIs would ensure compliance with Eclipse SDK 4.34 APIs. Refer to
318+
<a href="https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/Evolving-Java-based-APIs.md">
319+
<em>Evolving Java-based APIs</em>
320+
</a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
321+
322+
<p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.35 will be upwards
323+
binary-compatible with Eclipse SDK 4.34 except in those areas noted in the
324+
<a href="https://help.eclipse.org/2025-03/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_35_porting_guide.html" target="_top">
325+
<em>Eclipse 4.35 Plug-in Migration Guide</em>
326+
</a>. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK
327+
4.35 will not be usable in Eclipse SDK 4.34. Refer to
328+
<a href="https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/Evolving-Java-based-APIs.md">
329+
<em>Evolving Java-based APIs</em>
330+
</a> for a discussion of the kinds of API changes that maintain binary compatibility.</p>
331+
332+
<p><strong>Source Compatibility:</strong> Eclipse SDK 4.35 will be upwards source-compatible
333+
with Eclipse SDK 4.34 except in the areas noted in the
334+
<a href="https://help.eclipse.org/2025-03/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_35_porting_guide.html" target="_top">
335+
<em>Eclipse 4.35 Plug-in Migration Guide</em>
336+
</a>. This means that source files written
337+
to use Eclipse SDK 4.35 APIs might successfully compile and run against Eclipse
338+
SDK 4.34 APIs, although this is not guaranteed. Downward source compatibility
339+
is not supported. If source files use new Eclipse SDK APIs, they will not be
340+
usable with an earlier version of the Eclipse SDK. </p>
341+
342+
<p><strong>Workspace Compatibility:</strong> Eclipse SDK 4.35 will be upwards
343+
workspace-compatible with earlier 3.x and 4.34 versions of the Eclipse SDK unless noted.
344+
This means that workspaces and projects created with Eclipse SDK 4.34, 4.33,4.32...4.29, 4.25, .. 3.0 can be successfully
345+
opened by Eclipse SDK 4.35 and upgraded to a 4.35 workspace. This includes both
346+
hidden metadata, which is localized to a particular workspace, as well as metadata
347+
files found within a workspace project (e.g., the .project file ), which may
348+
propagate between workspaces via file copying or team repositories. Individual
349+
plug-ins developed for Eclipse SDK 4.35 should provide similar upwards compatibility
350+
for their hidden and visible workspace metadata created by earlier versions;
351+
4.35 plug-in developers are responsible for ensuring that their plug-ins recognize
352+
metadata from earlier versions and process it appropriately. User
353+
interface session state may be discarded when a workspace is upgraded. Downward
354+
workspace compatibility is not supported. A workspace created (or opened) by
355+
a product based on Eclipse 4.35 will be unusable with a product based on an earlier
356+
version of Eclipse. Visible metadata files created (or overwritten) by Eclipse
357+
4.35 will generally be unusable with earlier versions of Eclipse. </p>
358+
359+
<p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes,
360+
and certainly everything in a package with &quot;internal&quot; in its name or
361+
x-internal in the bundle manifest entry,
362+
are considered implementation details which may vary between operating environment
363+
and are subject to change without notice. Client plug-ins that directly depend
364+
on anything other than what is specified in the Eclipse SDK API are inherently
365+
unsupportable and receive no guarantees about compatibility within a single
366+
release much less with earlier releases. Refer to
367+
<a href="https://www.eclipse.org/articles/Article-API-Use/index.html">
368+
<em>How to Use the Eclipse API</em>
369+
</a> for information about how to write compliant plug-ins. </p>
370+
371+
</div>
372+
</p:compatibility_with_previous_releases>
373+
374+
<!-- ============================================== -->
375+
376+
<!-- <p:themes_and_priorities> -->
377+
378+
<p:preamble>
379+
We no longer group the plan items into separate themes as this does not provide real value to our users.
380+
<div>
381+
</div>
382+
</p:preamble>
383+
384+
<!-- </p:themes_and_priorities> -->
385+
386+
<!-- ============================================== -->
387+
388+
</p:plan>

0 commit comments

Comments
 (0)