baliuka juozas wrote:
All feature requests are very low priority after
roadmap for the new release is approved, it is better
to discuss new features before to start development on
the new branch, it helps to plan releases. It is
possible to vote it on jira too, it must be a good
usefulness and priority indicator. But it must be
better to delay issue than to close it too ( this
information can be useful the next release, jira must
help to maintain it ).
My main concern is because people close feature requests instead of
delaying them, we lose all track of the requested change. Then JIRA
voting and other features are disabled too, so we can't really know if a
issue is popular or not. And last but not least, the rejections are
based on personal motivations (or just lack of interest) instead of
valid technical reasons (which should be commented in JIRA for other
people to see and to avoid dupes).
So important features get ignored very easily. The mailing list is
usually a worse option, since people tend to ignore "naggers" just
because they ask for a reason of a rejection. I'll probably patch myself
the source, but I'd rather see it in the main codebase for other people
to benefit from it (and to get some feedback).
--
Ing. Leonardo Quijano Vincenzi
Director Técnico
DTQ Software
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
