+1 on having the spec. on github.
Does the document also relate to the TCK? If so it maybe makes sense
to have it within a third repo next to beanvalidation-api and
beanvalidation-tck. Otherwise putting it into beanvalidation-api seems
good. What format will the document have?
-- Gunnar
2011/6/7 Hardy Ferentschik <hardy(a)hibernate.org>:
On Tue, 07 Jun 2011 09:10:15 +0200, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> Guys I'm considering releasing the specification document as a Git
> repository.
> I am wondering if the document should share the same Git repo as
> beanvalidation-api or if these two should be kept separated. In other
> words, do these share the same release / tag cycle all the time?
+1 I think having them in the same repo makes sense. IMO they have the
same release/tag cycle.
If it is too hard though I am happy w/ a new repo under the
https://github.com/beanvalidation/
umbrella.
--Hardy
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev