Re: [bv-dev] Priority list
My problems with votes is that they are not weighted. I am not running the EG as a direct
democracy. In general, I value someone's opinion proportional to his knowledge and
involvement.
For example, method level validation might not make sense to the commoner and thus be
voted low but we see it as extremely important esp since it's used by other JSRs.
Votes cannot really expose that.
That being said, we can categorize issues in 4 circles:
- must have
- should have
- nice to have
- post 1.1
and we can use the comment system to mark issues with these circles.
On 25 sept. 2011, at 13:37, Gunnar Morling wrote:
I'm wondering what's the best way to achieve some initial
prioritization. Should we add comments to the JIRA issues? Another
idea would be to use JIRA's voting feature and start with working on
features with most votes. WDYT?
--Gunnar
2011/9/7 beanvalidation-dev List <beanvalidation-dev(a)lists.jboss.org>:
> Hi all,
>
> I have not seen your comment on the priority list.
>
> http://beanvalidation.org/roadmap/ (main)
>
https://hibernate.onjira.com/secure/IssueNavigator.jspa?reset=true&jq...
(complete list of candidates)
>
> Can you put some thoughts to what has top priority for you and give your feedback?
>
> Emmanuel
>
> PS: I will be away from connected computers of most sort for 7 days ( for good
reasons :o) ), but get the flow going without me.
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev