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