thanks for links, Robert It seems that I can only have one link to update site on that page, so I won't add nightly there. Instead I'll try to update the current update site. I posted a link to this discusion on the forum.
Jacek ________________________________ From: pdt-dev-boun...@eclipse.org [pdt-dev-boun...@eclipse.org] on behalf of Robert Gründler [r.gruend...@gmail.com] Sent: 06 July 2012 14:00 To: PDT Developers Subject: Re: [pdt-dev] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples Hi Jacek, thanks for the info. Could this nightly updatesite be mentioned here? http://www.eclipse.org/projects/project.php?id=tools.pdt Looks like there's quite some confusion going an among users: http://www.eclipse.org/forums/index.php/t/366539/ regards -robert On Fri, Jul 6, 2012 at 9:33 AM, Jacek Pospychała <jace...@zend.com<mailto:jace...@zend.com>> wrote: hi, 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 so you can give it a try as well. It's also available as zip at pdt downloads. In June we also provided a fresh all-in-one package at www.zend.com/pdt/downloads<http://www.zend.com/pdt/downloads> if you prefer a complete bundle. Jacek Pospychala, PDT lead ________________________________ From: pdt-dev-boun...@eclipse.org<mailto:pdt-dev-boun...@eclipse.org> [pdt-dev-boun...@eclipse.org<mailto:pdt-dev-boun...@eclipse.org>] on behalf of Mike Milinkovich [mike.milinkov...@eclipse.org<mailto:mike.milinkov...@eclipse.org>] Sent: 05 July 2012 15:23 To: 'Cross project issues' Cc: 'Tools PMC mailing list'; pdt-dev@eclipse.org<mailto:pdt-dev@eclipse.org> Subject: Re: [pdt-dev] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples +Tools PMC (note bolded comment below) +PDT dev list (please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977) From: cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org> [mailto:cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>] On Behalf Of zhu kane Sent: July-05-12 1:53 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Does this behavior violate EPL or community prinicples 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. Mengxin On Wed, Jul 4, 2012 at 3:04 PM, Ed Willink <e...@willink.me.uk<mailto:e...@willink.me.uk>> wrote: Hi 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. Regards Ed Willink On 04/07/2012 06:17, zhu kane wrote: Hello community, I hesitated about raising such question in here. But I can't get any response from PDT project even if filing critical bug for it[1]. PDT team announced PDT 3.1 was released[2] with Juno simultaneous release. PDT 3.1 also is listed in highlighted Juno project list[3]. 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[4]. Looks like PDT 3.1 doesn't have any public nightly build and integration build. I only find a build[5] 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. Thank you. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977 [2] https://bugs.eclipse.org/bugs/attachment.cgi?id=216929 [3] http://eclipse.org/juno/projects.php [4] http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.pdt/features/org.eclipse.php-feature/?root=Tools_Project [5] https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes Mengxin Zhu _______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org<mailto:pdt-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
