Hi,
I had the first time a closer look at distributed VCS systems. In
particular I had a look at bazaar, bundle buggy and launchpad. I have
to say, on first sight I'm very impressed. It tears down the strong
divide between committers and non-commiters. It offers a much more
convenient and powerful way to contribute for non committers. Another
killer feature is how launchpad (optionally) enforces code reviews.
And obviously it is so much easier to informally exchange code (for
example when you are doing bug fixing together with a user, as I have
been doing frequently the last month). And there are even additional
important advantages. I'm excited. But we have to keep the Gradle svn-
only users happy.
These questions go to Russel. Provided bazaar is master and the svn
codehaus is slave. What about:
1.) using svn to get the latest from branch/trunk to build a
distribution from.
2.) checking the history of the code via svn.
3.) submitting a svn-patch via Jira.
If we were to move to Bazzar, the developers would have to use it.
They could not choose to use svn instead. For contributions it would
be also the preferred way.
There is an IntelliJ plugin out there for bazaar. Russel, what would
I have to do, if I would like to use bazaar locally but then get the
changes into codehaus svn as well as merge from codehaus svn?
Adam, what is your opinion on all this?
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
