|Re: [pdt-dev] The Oxygen Simultaneous Release is available!|
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 ,
De : pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> de la part de Kaloyan Raev <kaloyan.r@xxxxxxxx>
EnvoyÃ : jeudi 29 juin 2017 05:15
Ã : pdt-dev@xxxxxxxxxxx
Objet : Re: [pdt-dev] The Oxygen Simultaneous Release is available!
As we have discussed , 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" composite update site to point to the 5.0.1 repo.
The list of all fixed bugs in 5.0.1 is available here .
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"  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?
Kaloyan Raev | Zend Studio Team Lead
Rogue Wave Software, Inc.
Innovate with Confidence
M +359 887 648 663
www.roguewave.com / kaloyan.raev@xxxxxxxxxxxxx
On 06/28/2017 05:27 PM, Dawid PakuÅa wrote: