you're right there's been a bit of mess with PDT lately.
Although we continuously work on the project, there was nobody since Indigo SR2 to update project version (3.0.1->3.1) and promote it regularly, hence Juno release train ended up with same PDT package as Indigo SR2, dated 2012-01-11.
We want to fix this for Juno SR1, which will have PDT version 3.1.1. Our friendly Zend QA team is currently verifying about 200 fixed bugs from last months in PDT bugzilla. We just started publishing nightly builds update site at http://download.eclipse.org/tools/pdt/updates/3.1.1/nightly
you can give it a try as well. It's also available as zip at pdt downloads.
Jacek Pospychala, PDT lead
+Tools PMC (note bolded comment below)
+PDT dev list (please see
I also appreciate the effort of PDT team made, it's great to release maintenance version in Indigo SR2 time frame. And it still works well in Juno.
I don't think development team is possible to mess up the release version. Anyway
I would like to see comments from PDT and PMC.
On Wed, Jul 4, 2012 at 3:04 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
The situation doesn't seem nearly as bad as you make out.
The public promoted builds on
http://www.eclipse.org/pdt/downloads/ show a 2-Jan-2012 3.0.0 Maintenance build as the most recent and examining the ZIP content reveals 3.0.1 content.
Installing the Juno release train installs a 2-Jan-2012 3.0.1, which correlates with the Eclipse CVS.
The Hudson build job
https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes shows active public development of 3.1 in the Eclipse CVS.
So it seems there are some releng difficulties that cause 3.0.1 to be listed as 3.0.0 on the download page, and some over-enthusiasm that causes a 3.0.1 contribution to be called 3.1.
A rename can fix the download page. A resubmission of the review slides can fix the misleading version claim. Perhaps Kepler should be 3.2 to avoid more confusion.
On 04/07/2012 06:17, zhu kane wrote: