FYI: The latest proposed schedule for Eclipse Oxygen (2017-2018) and Photon (2018-2019)
by Nick Boldt
Here's the latest proposal from the Planning Council on the Oxygen and
Photon (Oxygen+1) releases.
Note that there's still some contention around doing an Oxygen.0a "JDK
9 Update" release in July, but it's sounding like the foundation wants
one, so there will be one. It might be simply an update to
platform/JDT/webtools, or it might be bigger.
https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg026...
https://wiki.eclipse.org/Planning_Council/March_01_2017
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years
- 4
- 3
FYI: parent pom releases this week: 4.4.3.Final and 4.3.2.Final
by Nick Boldt
Recently, the Integration Stack guys requested that we start releasing
parent poms.
So, today, the 4.4.3.Final parent pom has been released [1].
[1] https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~pare...
I also released 4.3.2.Final [1] parent pom as I was testing some
automation / scripting of nexus staging and release steps. I can now
do a release to Nexus completely from a Jenkins job, without having to
do any manual steps. \0/
If you depend on either the 4.3.2.Final-SNAPSHOT or the
4.4.3.Final-SNAPSHOT parent poms, please update your root poms
accordingly (to remove "-SNAPSHOT") as Nexus will purge the snapshots
soon.
For more on this, see: https://issues.jboss.org/browse/JBIDE-23768
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years
- 2
- 2
Versions bump policy change
by Jean-Francois Maury
Hello,
as we branched for Oxygen, we now have two different branches to maintain
and as we are pushed changes in the code base, we need to upversion the
components.
In order to be better aligned with OSGI/P2, we decided to change a little
how the bump is managed.
Previously, all sub-components of a component (eg jbosstools-openshift)
were upversioned as soon as a single sub component is modified). We will
upversion only the sub component that has changed.
For master, the minor will be incremented and for 4.4.x, the micro will be
increment.
As an example, we need to update org.jboss.tools.openshift.client in both
branches and as OpenShift is 3.3.2, this will give:
- master: org.jboss.tools.openshift.client only will switch to 3.4.0
- 4.4.x: org.jboss.tools.openshift.client only will switch to 3.3.3
We will experiment this during 4.4.4.AM1 and revisit if we found too many
problems
9 years
- 4
- 10