"latest" repo per major version or per SimRel release like
Kaloyan said would be really great.
+1 for Dawid's idea ;)
De : pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> de la part de Dawid Pakuła <zulus@xxxxxxxxx>
Envoyé : vendredi 30 juin 2017 14:38
À : PDT Developers
Objet : Re: [pdt-dev] The Oxygen Simultaneous Release is available!
I like updates/${eclipse-name} option. Similar to mylyn if I have good memory ;)
On 30 June 2017 at 13:58:17, Kaloyan Raev (kaloyan.r@xxxxxxxx) wrote:
Hi Thierry,
At the moment we put the latest official release in the "latest" repo, regardless of the major or minor version number.
So, let's say we include the "latest" repo in the PHP EPP for Oxygen.1. When Photon is released with (probably) PDT 6.0 then users running Oxygen.1 will be suggested to update to PDT 6.0.
However, this may be an issue if we don't keep minimum version constraints carefully in PDT. Let's say PDT 6.0 relies on some features of DLTK or Platform that was introduced in Photon. If we don't mark this in the PDT plugins metadata then upgrading PDT 5.0
to 6.0 in an Oxygen installation would cause problems.
From this perspective it might make sense to have "latest" repo per major version or per SimRel release, i.e.
http://download.eclipse.org/tools/pdt/updates/5.x
http://download.eclipse.org/tools/pdt/updates/6.x
or
http://download.eclipse.org/tools/pdt/updates/oxygen
http://download.eclipse.org/tools/pdt/updates/photon
This would be the safer approach, but will have some additional cost in terms of releng efforts.
On 06/30/2017 12:59 PM, thierry blind wrote:
Hi Kaloyan,
if you add the "latest" repo to the PHP EPP package, will it contains latest
updates for a given branch (for example 5.0.x patches when the user installed the 5.0 release) or will it automatically update to newest PDT release + maintenance branch?
In other words, would it be interesting to "split" http://download.eclipse.org/tools/pdt/updates/latest into http://download.eclipse.org/tools/pdt/updates/5.0/latest , http://download.eclipse.org/tools/pdt/updates/5.1/latest ,
... ?
Thierry.
Hi,
As we have discussed [1], we are wanted to have a 5.0.1 maintenance release with the official Oxygen release. So, I promoted the "5.0.1-nightly" repo to "5.0.1" and updated the "latest"[2] composite update site to point to the 5.0.1 repo.
The list of all fixed bugs in 5.0.1 is available here [3].
I think it is a good moment to discuss how to push such maintenance releases automatically to PDT users. Those who have registered the "latest" [2] repo would get the notification popup for the available update. But this repo is not registered in the PHP EPP
package and these users have to add it manually.
Should we just add the "latest" repo to the EPP package? Any concerns about this?
[1]
https://dev.eclipse.org/mhonarc/lists/pdt-dev/msg03355.html
[2]
http://download.eclipse.org/tools/pdt/updates/latest
|
Eclipse is probably best known as a Java IDE, but it is more: it is an IDE framework, a tools framework, an open source project, a community, an eco-system, and a foundation.
|
[3]
https://projects.eclipse.org/projects/tools.pdt/releases/5.0.1/bugs
Kaloyan Raev
| Zend Studio Team Lead
Rogue Wave Software, Inc.
Innovate with Confidence
M +359 887 648 663
www.roguewave.com /
kaloyan.raev@xxxxxxxxxxxxx
We’re the largest independent provider of cross-platform software development tools and embedded components in the world. Come see how we can help.
|
On 06/28/2017 05:27 PM, Dawid Pakuła wrote:
Hi,
PDT 5.0 has been released :D
I updated wiki / website / marketplace and update sites.
Thank You!
The twelfth yearly Simultaneous Release since Callisto in 2006 is
available now!
The main repository is at
http://download.eclipse.org/releases/oxygen/
The EPP (all-in-one) packages are available at
https://www.eclipse.org/downloads/eclipse-packages/
The main download page is still at
https://www.eclipse.org/downloads/
And the beautiful main landing page is at
https://www.eclipse.org/oxygen/
Tell your friends, tweet, facebook, snapchat, instagram about it or ...
just send a plain old email! ;)
Thanks to all users, bug reporters, contributors, committers, releng
engineers and everyone else involved with making this release possible!
--
Frederic Gurr
Release Engineer
Eclipse Foundation
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev
|