+1

For minor changes a commit without a ticket is good for me but we still need to open a pull request.

For other changes a BVAL issue has to be opened and each commit should reference its ticket. I think commits should have the same format as described here but with BVAL as issue key.

--Kevin

Le vendredi 16 septembre 2011 à 19:49, Gunnar Morling a écrit :

+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@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@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev