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
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.
ÂÂÂ ÂÂÂ Ed Willink
On 04/07/2012 06:17, zhu kane wrote:
I hesitated about raising such question in here. But I can't get
any response from PDT project even if filing critical bug for
PDT team announced PDT 3.1 was released with Juno simultaneous
release. PDT 3.1 also is listed in highlighted Juno project
list. But none of Eclipse users knows how to install it.
I would like to believe it's just a bug, however nobody of PDT
project takes action for it. In my understanding all projects of
Eclipse.org are open source, everybody can browse the latest
source code even under developing. I'm astonished that I can't
find any commit related to PDT 3.1 from its source repository.
Looks like PDT 3.1 doesn't have any public nightly build and
integration build. I only find a build for 3.0 in Hudson.
I'm wondering whether Eclipse.org/EPL allows a project under it
that is not really open source and just declared its new release.
Hope experienced people help resolve my doubts.
cross-project-issues-dev mailing list
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2193 / Virus Database: 2437/5108 - Release Date: