Hi, one other organizational question I had was how to handle changes/clarifications/typos in the existing spec (https://github.com/beanvalidation/beanvalidation-spec). Should we open BVAL issues for each change or just create pull request or ... ? --Hardy _______________________________________________ beanvalidation-dev mailing list beanvalidation-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/beanvalidation-dev

+1 Only really minor changes should go without a BVAL ticket IMO. Each commit should of course reference a ticket, too. --Gunnar -sent from my mobile phone- Am 16.09.2011 17:44 schrieb "Emmanuel Bernard" <emmanuel(a)hibernate.org (mailto:emmanuel@hibernate.org)>: > I'd say > - typo: simply commit > - clarification and change deserve their BVAL + pull request > > On 16 sept. 2011, at 17:10, Hardy Ferentschik wrote: > >> Hi, >> >> one other organizational question I had was how to handle >> changes/clarifications/typos in the existing spec >> (https://github.com/beanvalidation/beanvalidation-spec). >> Should we open BVAL issues for each change or just create pull request or >> ... ? >> >> --Hardy >> _______________________________________________ >> beanvalidation-dev mailing list >> beanvalidation-dev(a)lists.jboss.org (mailto:beanvalidation-dev@lists.jboss.org) >> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev > > _______________________________________________ > beanvalidation-dev mailing list > beanvalidation-dev(a)lists.jboss.org (mailto:beanvalidation-dev@lists.jboss.org) > https://lists.jboss.org/mailman/listinfo/beanvalidation-dev _______________________________________________ beanvalidation-dev mailing list beanvalidation-dev(a)lists.jboss.org (mailto:beanvalidation-dev@lists.jboss.org) https://lists.jboss.org/mailman/listinfo/beanvalidation-dev