Re: [pdt-dev] PDT 2.2 Project Plan
Roy, As a partial/temporary technical solution for the visibility issue I would suggest to put into the page links for each milestone pointing to Bugzilla search result showing all the bugs having the selected milestone as the target (this is only relevant, of course, if the PDT team still maintains the bugs with targets). Regards, Seva On Tue, Mar 23, 2010 at 11:28 PM, Roy Ganor r...@zend.com wrote: Robert, this issue has nothing to do with the visibility of the project. The issue you mentioned depends on another issue that is handled by the Eclipse Foundation webmaster that prevents the action of promoting a new version of PDT to the milestones/interim update site. Once this issue is fixed we can start rolling out builds. With regards to the visibility of the project, I would like to know what you guys are expecting. In general the most important parts in successful open source communities is the *diversity and the communication*. Still since early days of this project we enjoy great user base *but small amount of feedback (good and bad)*, which causes us, the committers, to lead the project. I would be VERY happy to hear your feedback (in Bugzilla for example) and be more active before asking us the committers to be more visible. Last but not least, it doesn't say we can't do things better but at least you guys can be helpful with suggesting more accurate things rather than just vote. BTW, I fixed bug 294107 - 2.2 plan lists all milestone dates in the same year but am sure you guys want more information in this page. Usually I put a page after the project is release for What's new. Thanks for your feedback, Roy -Original Message- From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of Robert Gruendler Sent: Monday, March 22, 2010 9:05 PM To: PDT Developers Subject: Re: [pdt-dev] PDT 2.2 Project Plan same here. although i really support the project and appreciate the help one receives as a developer on this list, the end-user information could be enhanced. For example it's a bit confusing that the current development version is presented as the first option in the installation wiki, whereas the current 2.2 build is broken, which imho is not such a good experience for people trying out pdt: https://bugs.eclipse.org/bugs/show_bug.cgi?id=305877 regards -robert On Mar 22, 2010, at 7:59 PM, Nikolai Plath wrote: Sorry folks but... i second that Am 22.03.2010 08:26, schrieb Sjaak Eenhuis: This is not a project plan. Its a list consisting of alfanumeric codes with dates associated. M311/12/2010M3 milestone M412/18/2010M4 milestone etc The only thing this plan teaches us is that there are milestones, but they don't tell in what land they stand. Beside the fact that this table doesn't contain any usable data, the data that is inside is incorrect. We learn that milestone 3 will be delivered after the final product has been released. :-) As a pdt user I feel the urge to say something about this, because the last pdt release went online a long time ago, and the goals are still a secret. I would like to suggest that you seek out better ways to handle conflicting interests between Zend Studio and PDT, or if you feel this isn't the problem, we could try to find out the real cause. I understood that you have finished the rewrite with h2-indexing, maybe we could add this as an achievement on the plan page? This is a good message to all the people that suffers from autocompletion inertia. Btw I kind of love pdt. As an avid 'supporter' of this project I thank you all again for all the efforts made. Subject: RE: [pdt-dev] PDT 2.2 Project Plan Date: Sat, 20 Mar 2010 22:10:35 +0200 From: r...@zend.com To: pdt-dev@eclipse.org You can find the project plan for PDT here: http://www.eclipse.org/projects/project-plan.php?projectid=tools.pdt We are currently working on Eclipse PDT issues and fix issues marked as P1. Anything in particular that you are searching for? Roy -Original Message- From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of sNop Sent: Saturday, March 20, 2010 12:17 AM To: PDT Developers Subject: Re: [pdt-dev] PDT 2.2 Project Plan Hi, i'm lacking actualizations of the PDT's webpages too. They should be actualized more often. So the communication with PDT users is very bad. ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev _ Het laatste nieuws, shownieuws en voetbalnieuws op MSN.nl http://nl.msn.com/___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
RE: [pdt-dev] PDT 2.2 Project Plan
This is not a project plan. Its a list consisting of alfanumeric codes with dates associated. M3 11/12/2010 M3 milestone M4 12/18/2010 M4 milestone etc The only thing this plan teaches us is that there are milestones, but they don't tell in what land they stand. Beside the fact that this table doesn't contain any usable data, the data that is inside is incorrect. We learn that milestone 3 will be delivered after the final product has been released. :-) As a pdt user I feel the urge to say something about this, because the last pdt release went online a long time ago, and the goals are still a secret. I would like to suggest that you seek out better ways to handle conflicting interests between Zend Studio and PDT, or if you feel this isn't the problem, we could try to find out the real cause. I understood that you have finished the rewrite with h2-indexing, maybe we could add this as an achievement on the plan page? This is a good message to all the people that suffers from autocompletion inertia. Btw I kind of love pdt. As an avid 'supporter' of this project I thank you all again for all the efforts made. Subject: RE: [pdt-dev] PDT 2.2 Project Plan Date: Sat, 20 Mar 2010 22:10:35 +0200 From: r...@zend.com To: pdt-dev@eclipse.org You can find the project plan for PDT here: http://www.eclipse.org/projects/project-plan.php?projectid=tools.pdt We are currently working on Eclipse PDT issues and fix issues marked as P1. Anything in particular that you are searching for? Roy -Original Message- From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of sNop Sent: Saturday, March 20, 2010 12:17 AM To: PDT Developers Subject: Re: [pdt-dev] PDT 2.2 Project Plan Hi, i'm lacking actualizations of the PDT's webpages too. They should be actualized more often. So the communication with PDT users is very bad. ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev _ Het laatste nieuws, shownieuws en voetbalnieuws op MSN.nl http://nl.msn.com/___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] PDT 2.2 Project Plan
Sorry folks but... i second that Am 22.03.2010 08:26, schrieb Sjaak Eenhuis: This is not a project plan. Its a list consisting of alfanumeric codes with dates associated. M311/12/2010M3 milestone M412/18/2010M4 milestone etc The only thing this plan teaches us is that there are milestones, but they don't tell in what land they stand. Beside the fact that this table doesn't contain any usable data, the data that is inside is incorrect. We learn that milestone 3 will be delivered after the final product has been released. :-) As a pdt user I feel the urge to say something about this, because the last pdt release went online a long time ago, and the goals are still a secret. I would like to suggest that you seek out better ways to handle conflicting interests between Zend Studio and PDT, or if you feel this isn't the problem, we could try to find out the real cause. I understood that you have finished the rewrite with h2-indexing, maybe we could add this as an achievement on the plan page? This is a good message to all the people that suffers from autocompletion inertia. Btw I kind of love pdt. As an avid 'supporter' of this project I thank you all again for all the efforts made. Subject: RE: [pdt-dev] PDT 2.2 Project Plan Date: Sat, 20 Mar 2010 22:10:35 +0200 From: r...@zend.com To: pdt-dev@eclipse.org You can find the project plan for PDT here: http://www.eclipse.org/projects/project-plan.php?projectid=tools.pdt We are currently working on Eclipse PDT issues and fix issues marked as P1. Anything in particular that you are searching for? Roy -Original Message- From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of sNop Sent: Saturday, March 20, 2010 12:17 AM To: PDT Developers Subject: Re: [pdt-dev] PDT 2.2 Project Plan Hi, i'm lacking actualizations of the PDT's webpages too. They should be actualized more often. So the communication with PDT users is very bad. ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev _ Het laatste nieuws, shownieuws en voetbalnieuws op MSN.nl http://nl.msn.com/___ pdt-dev mailing list 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
Re: [pdt-dev] PDT 2.2 Project Plan
same here. although i really support the project and appreciate the help one receives as a developer on this list, the end-user information could be enhanced. For example it's a bit confusing that the current development version is presented as the first option in the installation wiki, whereas the current 2.2 build is broken, which imho is not such a good experience for people trying out pdt: https://bugs.eclipse.org/bugs/show_bug.cgi?id=305877 regards -robert On Mar 22, 2010, at 7:59 PM, Nikolai Plath wrote: Sorry folks but... i second that Am 22.03.2010 08:26, schrieb Sjaak Eenhuis: This is not a project plan. Its a list consisting of alfanumeric codes with dates associated. M311/12/2010M3 milestone M412/18/2010M4 milestone etc The only thing this plan teaches us is that there are milestones, but they don't tell in what land they stand. Beside the fact that this table doesn't contain any usable data, the data that is inside is incorrect. We learn that milestone 3 will be delivered after the final product has been released. :-) As a pdt user I feel the urge to say something about this, because the last pdt release went online a long time ago, and the goals are still a secret. I would like to suggest that you seek out better ways to handle conflicting interests between Zend Studio and PDT, or if you feel this isn't the problem, we could try to find out the real cause. I understood that you have finished the rewrite with h2-indexing, maybe we could add this as an achievement on the plan page? This is a good message to all the people that suffers from autocompletion inertia. Btw I kind of love pdt. As an avid 'supporter' of this project I thank you all again for all the efforts made. Subject: RE: [pdt-dev] PDT 2.2 Project Plan Date: Sat, 20 Mar 2010 22:10:35 +0200 From: r...@zend.com To: pdt-dev@eclipse.org You can find the project plan for PDT here: http://www.eclipse.org/projects/project-plan.php?projectid=tools.pdt We are currently working on Eclipse PDT issues and fix issues marked as P1. Anything in particular that you are searching for? Roy -Original Message- From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of sNop Sent: Saturday, March 20, 2010 12:17 AM To: PDT Developers Subject: Re: [pdt-dev] PDT 2.2 Project Plan Hi, i'm lacking actualizations of the PDT's webpages too. They should be actualized more often. So the communication with PDT users is very bad. ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev _ Het laatste nieuws, shownieuws en voetbalnieuws op MSN.nl http://nl.msn.com/___ pdt-dev mailing list 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 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
