[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Helios requirements
|
Well, here's my advice. Do the best you can on the items your community cares about the most. And forget about the rest. If they kick you off the train, so be it. The most important thing you should be focusing on is a EPP package for Parallel Tools. The train is secondary.
Doug.
On Fri, Apr 9, 2010 at 8:57 AM, Greg Watson
<g.watson@xxxxxxxxxxxx> wrote:
Hi Jeff,
The list is somewhat of a surprise to me also. It seems to have grown considerably since the Galileo.
I'd suggest we discuss this at the meeting next week before making any decisions. It's possible to request exceptions to certain requirements, so I suggest that we decide what we can achieve and what is impossible with our resources, then see if we can get the exceptions approved. Some of this stuff, like the ramp down and API policies, I'll be doing anyway for PTP.
Incidentally, adding message bundles is not difficult. There's an "Externalize strings..." option under the "Source" menu that will do just about everything for you. It shouldn't take more than a couple of hours for Photran.
Regards,
Greg
On Apr 9, 2010, at 1:41 AM, Jeffrey Overbey wrote:
There are many requirements that need to be met for the Helios release
Greg,
Did you mention this list of requirements when we first discussed joining Helios? If so, I missed it... I was not aware of this until Chris mentioned "the rules" a couple days ago and I began to wonder what I had gotten myself into.
I say this because Photran (perhaps not surprisingly) is going to be a problem, and I think the most responsible thing to do is for Photran to pull out of the release train.
All of the following are "required," and we do none of them.
> leverage only published APIs of dependencies.
> use Message Bundles.
> Support Translations.
> Excel in NL support.
> measurable performance criteria
> devote at least one milestone to performance and scalability improvements.
> Test Localization.
> design and test for ... bidi, unicode
> written ramp down policy by M6
> design and test for accessibility compliance
> document accessibility work and compliance
> API Policy Defined and Documented
> define and document their retention policy
> provide some summary metrics
> New & Noteworthy for each milestone
We absolutely don't have the resources to get all of this done in time. (And, frankly, some of it seems like over-engineering for Photran -- e.g., we have not, in seven years, had a single person request or offer to help with localization, so it's not clear to me why that's a good use of time when there are more pressing issues that users actually want addressed.)
We can still release Photran 6 aroud the same time as Helios (+/- a few weeks), even if we're not part of Helios proper. Users that want Fortran support in Eclipse have had no problem finding us in the past...
Jeff
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
