Hi,
I’m 100% agree with often releases.
But we still have to announce our participation before M4 with
version declared in PMI (number, type, project plan…) [1].
Each version update have to be also announced. I'm going to ask PMC
when (if) I'll be formally accepted as a project lead.
So, can we prepare our initial plan for Mars release?
From my side I want continue performance and memory consumption
improvements, especially #438091 [2], #438087 [3], #438100 [4] +
some tweaks for DLTK
Besides on my todo / investigate / wish list are also:
#369635 [5] - I’ll create another thread for this on our
(spam)list soon ;)
#443473 [6], #440965 [7], #438097 [8]
--
Dawid
Pakuła
+48 795
996 064
On 23 września 2014 at 17:22:29, Kaloyan
Raev (kaloyan.r@xxxxxxxx)
wrote:
Hi,
In general, I believe, we should have three releases per
year aligned with the Eclipse Simultaneous release: June - SR0,
September - SR1 and February - SR2. Whether each release is
"feature" or "maintenance" depends on the changes done in this
release.
So, if we apply the above, for Luna SR1 we are having
the 3.3.1 maintenance release.
As Michal started working on PHP 5.6 support and it will
be ready by Luna SR2, then we may ship a 3.4 feature release for
Luna SR2 and Mars M5.
For the official Mars release we can ship either 3.4.1
and 3.5 depending on what's done by then. But it is too early to
predict it at the moment.
This way we ship faster new features to users and avoid
having unnecessary spitting of code streams. This is actually the
approach of the EGit project, it's not anything I am inventing
right now :-)
Thoughts?
Kaloyan
_______________________________________________
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