On 21 Nov 2009, at 14:15, Steven Boscarine wrote:
Works for me, personally.
As an outsider, it's obviously more friendly for non-JBoss employees
like me to contribute. I am still waiting on someone to tag those Weld
Maven archetypes I submitted so I can commit to trunk for review without
worrying about breaking anything. With git, that wouldn't be an issue.
You are welcome to tag whenever you want :-)
But I agree, GIT supports distributed development much better.
I have only used it for personal projects, though. I don't know if
it'll make life easier or harder for whoever has to manage these releases.
Pete Muir wrote:
> A quick item we discussed at the f2f meeting was whether to switch to
> GIT for our SCM, rather than SVN.
>
> This would give us a IMO a system well suited to our distribued dev
> model, it would also make it much easier for others to sandbox PEs and
> then contribute them back to us.
>
> The proposal is to use Github to host.
>
> The team members at devoxx were in favour, but what do others think?
>
> Pete
>
> --
> Pete Muir
>
http://in.relation.to/Bloggers/Pete
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/weld-dev
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev