|Re: [cross-project-issues-dev] Does this behavior violate EPL or community prinicples|
I'm not part of PDT and don't use PDT at all. I'd like to comment on a few things that I believe are common misunderstandings about the release train.
There is the release train. And there is the Eclipse Packaging Project. You have to participate in the Release Train to have an EPP package, but not vice versa. There are a lot of projects on Juno that don't have a separate downloadable version.
PDT has a feature (3.0.0) in the Juno p2 repository. So to use it you have to download one of the packages and then install the PDT feature into it.
There was a discussion on epp-dev that PDT lost its package maintainer for the EPP projects and that no one would take the job (see http://dev.eclipse.org/mhonarc/lists/epp-dev/msg01632.html) (Hint: volunteers are always welcome).
You are right about the 3.1 release which got reviewed and seems well hidden. I couldn't find build artifacts or commits either. Maybe someone from the PDT team can clear this up.
Btw.: Raising a bug and getting no response in 2 work days doesn't mean no one will ever answer. Our team triages new bugzilla entries ones per week and shortly after the Juno release most committers will take a (IMO well deserved) break.
And I don't think the EPL is relevant here but the Eclipse Development Process and especially the Release Train requirements. As said above, I'd like some explanation from PDT on this.
On 04.07.2012, at 07:17, zhu kane wrote: