Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] About target platform

These milestones was also available previously (form M1 - M7 if have good memory).

Because we also have now only stream, we can always deliver latest-nightly. More important is M3 and RC1 phase.
In oposite to for example DLTK we have simple situation because we are at the end of the given chain so none in eclipse (except final EPP package) have org.eclipse.php.* bundles in dependencies.

From: thierry blind <thierryblind@xxxxxxx>
Reply: PDT Developers <pdt-dev@xxxxxxxxxxx>
Date: 20 March 2018 at 11:07:53
To: PDT Developers <pdt-dev@xxxxxxxxxxx>
Subject:  Re: [pdt-dev] About target platform

Hi,
I find milestone 1 and 2 very early in the dev cycle :/ Except that, no big changes.

Thierry.

De : pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> de la part de Dawid Pakuła <zulus@xxxxxxxxx>
Envoyé : mardi 20 mars 2018 08:25
À : PDT Developers
Objet : Re: [pdt-dev] About target platform
 
Hi,

for those who not track cross-project-issues-dev, Photon.0 is last yearly release. After this entire release train switch to 13-week cycle. There will be only one stream without maintenance releases.



From: Michal Niewrzal <m.niewrzal@xxxxxxxxx>
Reply: PDT Developers <pdt-dev@xxxxxxxxxxx>
Date: 24 February 2018 at 19:04:15
To: PDT Developers <pdt-dev@xxxxxxxxxxx>
Subject:  Re: [pdt-dev] About target platform

Hi,

I'm ok with droping compatibility with previous versions. 

Michal


23.02.2018 3:10 PM "thierry blind" <thierryblind@xxxxxxx> napisał(a):
I don't think we need to keep compatibility accross major eclipse release (Neon, Oxygen, ...), anyway, today's "compatibility" is already not 100% true between eclipse releases. And we also don't provide support for older versions, since we don't really work on multiple stable branches.
But the biggest breaking changes should (in my opinion) still be done after any *.3 stable release (and before next major eclipse release).
Simply because we are a very small team and every big change will bring new bugs (or missing features) that take (sometimes) very long time to be solved.
But on the other side, in a small team, it would still be possible to add big changes *anytime*, if we scrupulously respect this condition: the person who adds a major change should also maintain it 😉

I prefer adding stability and missing features than reworking code but it's still nice and exciting to be up-to-date with newest eclipse developments 😊
Also because some PDT dependencies seem deprecated (and no more supported) so some bugs will then never be solved 😉

Thierry.

De : pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> de la part de Dawid Pakuła <zulus@xxxxxxxxx>
Envoyé : vendredi 23 février 2018 12:27
À : PDT Developers
Objet : [pdt-dev] About target platform
 
Hi,

since we are without commercial support, do we still need keep compatibility with previous platform version?

Platform API grow a lot between releases , for example new apis for generic editor, tip of the day. With correct *.target file, you can easy develop on Oxygen for Photon. 

-- 
Dawid Pakuła

_______________________________________________
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

Back to the top