Hi again,
After reviewing the current state of PDT 4.2 with Michal, we thought
that we can make some quick wins for Neon.3:
- Declare the PHP 7.1 support as complete and make PHP 7.1 default
for new projects.
- Graduate the Composer plugin out of incubation and include it in
the EPP package. It is currently only in the SimRel update site.
The above deserves calling the next PDT release "4.3". I created a
4.3 version and target milestone in Bugzilla. I changed the target
milestone of all you fixes from 5.0 to 4.3. Thank you for making all
these fixes.
We can still fork the master branch once we have more aggressive
changes that should go for Oxygen only (PDT 5.0), but not for Neon.3
(PDT 4.3).
Kaloyan
On 01/03/2017 07:46 PM, thierry blind
wrote:
Hi Kaloyan,
that could be a solution ;)
I just wanted to merge some few pending patches, I think mid-january
could be a good deadline (probably more than enough for me
;),
I don't want to prevent other PDT developers from
committing 5.0 stuff.
The 14 january would be ok, after this date I'm anyway
on a business
travel ;)
Thierry.
Hi Thierry,
What is the exact date you need? :-)
Perhaps,
we can just do it when we have the first commit targeted to
PDT 5.0. Then we fork from the previous commit.
Kaloyan
On 01/03/2017 04:58 PM, thierry
blind wrote:
Hi Kaloyan,
ok we can call it 4.2.1 then. In all cases I see it
as a fork of master branch at some point in near
future ;)
Could we just set a date when we fork master branch
into a 4.2.1 branch?
Thierry.
Hi
If we want to have just bugfixes for Neon.3 then we
can have a 4.2.1 service release.
Kaloyan
On 01/03/2017 04:16 PM,
thierry blind wrote:
Hi team,
first of all: happy new year !!! 
I'm for option 2, even if option 3 would be
the easiest way to go.
I would like to see a 4.3 release that
includes my latest fixes (and further small
fixes that I will backport from 5.0).
I'm not planning to do big work on 4.3 in
near future (it will probably be a quiet
but-rock-solid release), so we could fork
master branch (in 1 or 2 weeks) as the 5.0
branch, and happily break things afterwards
with a lot of time to fix them ;)
Thierry.
I forgot to mention that I'm between
option 2 and 3 (the advantage for
3) regarding next release :)
Michal
Hi,
|
|
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.
|
For future, via
build.eclipse.org ssh you have
to prepare zip manually under
download/tools/pdt/downloads/ dir.
URL just contain full path inside
downloads dir.
|
|
build.eclipse.org
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.
|
Thanks!
With Kaloyan we did some
moves around version 4.2:
* version 4.2 is tagged in
git repo
* initial changes for PDT
website are done
To finish maintenance work
we need to decide what
will be next version.
Because we want to do
major API changes for
Oxygen then I think we
should consider 3 options:
1. Like always we are
releasing PDT with next
Eclipse release (Neon.3),
next PDT version will be
4.3, less time for
2. We are creating
separate branch for 4.3
were we will cherry pick
only fixes for issues
(release also with
Neon.3), in master we are
working with Oxygen
release (5.0), more time
for Oxygen but more work
with cherry picking :)
3. We are not releasing
4.3 at all and we are
focusing on version 5.0,
lot of time for Oxygen
WDYT?
Michał
Niewrzał | ZEND STUDIO
Rogue Wave
Software, Inc.
Accelerating
Great Code
www.roguewave.com / michal.niewrzal@roguewave.com
Hi,
I hope so 4.3
will be ok. My
personal
situation will
be clear since
new year
(3.01.2017),
I’ll be again
free and I will
do my 4.2 plan
;)
Hi
Team,
Eclipse
Neon.2 is
released but I
think we neglected
this release a
little bit What needs to
be done from
maintenance
point of view?
For Neon.3 we
will have
version 4.3 I
guess?
Greetings,
_______________________________________________
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
_______________________________________________
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
|
