Hi guys,
my 2 c ... I mainly develop under windows and using git successfully ...
most of our projects are git based and for sure we enjoy the power and
flexibility of this instument.
Said that I personally agree with Justin and Ben, I guess speaking about
community modules we should mainly take i
I disagree.
One key advantage of keeping community modules in subversion is
continuous integration coverage. The -PallExtensions profile raises
quality by forcing community modules to build or be kicked. This makes
it a true incubator. Furthermore, it alerts core developers to community
module
In my opinion community modules still have their place. For a few reasons.
1. While core developers are comfortable using git the learning curve is big
if you have never used it. I feel it might hinder contribution if we make
that the only option.
2. We build and publish some of the more mature c
Here is a list of community modules that I think I'm either the author,
co-author, or current maintainer of (I am pretty terrible about putting my
name in the appropriate fields in the pom, sorry about that.)
- css: definitely still maintained (although most of the real work of
this module i
On Fri, May 13, 2011 at 7:58 PM, Gabriel Roldán wrote:
> Hey, so this is my concern wrt community modules: IMHO the whole concept
> of having community modules in the mainstream svn repo is obsolete.
>
> I don't quite remember if we already discussed it, but for how long are
> we going to keep tie
Hey, so this is my concern wrt community modules: IMHO the whole concept
of having community modules in the mainstream svn repo is obsolete.
I don't quite remember if we already discussed it, but for how long are
we going to keep tied to svn?
Moving to git is a natural step forward IMHO and it'd
