Brian K. Wallace wrote:
It's the "what's needed" from a user's point of view that interests me.
I don't need pretty. I just need fewer questions to be answered. :-)
(not that I don't want pretty, just that Tapestry already does so much
that either a) isn't quite there for "less than edge" cases or b) isn't
documented - or not as easy to find. [more an agreement on #4 than a
documentation push there :-)]
Janitorials are usually in the center of discussions because we
perfectionists would like all code to be as tidy and perfect as
possible, and everything refactored and thoroughly documented (but not
too much!). The other extreme, people who like to "jump in", like all
the new features, and a bit more, without concern for the code base and
whether it is getting bloated. Most people are somewhere in between.
In this case, for the record, I think that even with the 100+ bug fixes
(great work, by the way!), Tapestry does need a cleaning job.
Just my 2 cents.
(ahh, don't say I talk without offering help... I would gladly do it.
But that's a "cross-cutting concerns" job, so, no easy patches for it)
There are quite a few things that were talked about - first for 3.1/4.0,
now 4.1/5.0 that get left behind with evolution. I'd like to propose
(yeah, I did this before :-)) a roadmap with issues assigned to achieve
the goals set out in it. There will be bugs, but for X.0/X.1/X.2/etc
releases there should be some sort of "written in jello" features. If it
takes brain dumping all itemized features, then splitting them off into
releases, maybe we can continue to get those done while new things are
being dreamed up.
Yes. JIRA supports it in a great way.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
