www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <j...@apache.org>
Subject [jira] Updated: (INFRA-2823) git mirror for maven-surefire
Date Thu, 24 Jun 2010 19:40:51 GMT

     [ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Rosenvold updated INFRA-2823:
--------------------------------------

    Environment:     (was: The Apache Software Foundation uses Subversion as the main version
control infrastructure, but we also provide some level of support to users of the Git version
control system. This page describes how you can use Git with Apache codebases.

Git access to Apache codebases
Git mirrors
Proposed workflow
Ongoing improvements
Git mirrors

We maintain read-only Git mirrors of many Apache codebases at http://git.apache.org/. These
mirrors contain the full version histories (including all branches and tags) of the mirrored
codebases and are updated in near real time based on the latest svn commits.

The mirrors can be cloned or pulled from using got the Git and HTTP protocols. See the mirror
page for the available clone URLs.

Please file an INFRA issue (component: Git) to request a new codebase to be mirrored or to
change the settings of an existing mirror. When requesting a new mirror, please include the
following information:

Name of the codebase, for example "Apache Tika"
Name of the requested Git mirror, for example "tika.git"
Subversion path of the codebase, for example "/lucene/tika/"
Subversion layout, in case it is different from the standard "trunk, branches, tags" structure.
Proposed workflow

This is a proposed workflow for using Git with an Apache codebase. This workflow is mainly
targeted to contributors who don't already have commit access to a project.

Once you have cloned or pulled the latest changes to your local Git repository of an Apache
codebase, you can start working on it. Whenever you make some changes to the codebase, it's
good to have a related issue filed in the issue tracker of the project and to use a similarly
named branch in your Git repository. For example, to create a branch for an issue with the
key TIKA-123.

git branch TIKA-123 origin/trunk
With per-issue branches you can easily switch back and forth between different issues without
worrying about unwanted side-effects from unfinished changes to other issues. Whenever you
want to work on the TIKA-123 example issue, simply checkout that branch and start making your
changes.

git checkout TIKA-123
It's a good idea to commit your changes whenever you have finished one logical part of the
issue. For example when refactoring, make a new commit for each refactoring step you take.

git commit
Once you're ready to share your changes with the rest of the project team, you can use the
git format-patch command to produce a nice set of patches to attach to the relevant issue.

git format-patch origin/trunk
The sooner you share your work the better. You can repeat the steps of this workflow as often
as you like, producing more patches to be attached to the issue tracker. Once some of your
patches are accepted and committed to svn, you can rebase your work against the latest trunk.
Alternatively, if you're asked to make some changes, you can go back to the original Git commit
and modify it until the project team accepts your changes.

Ongoing improvements

Improvements to Git support at Apache are being discussed on the infrastructure-dev@ mailing
list. This list is open to everyone and is publicly archived. You can subscribe this mailing
list by sending a message to infrastructure-dev-subscribe@apache.org.

Apache Projects
HTTP Server
Abdera
ActiveMQ
Ant
APR
Archiva
Avro
Buildr
Camel
Cassandra
Cayenne
Click
Cocoon
Commons
Continuum
CouchDB
CXF
DB
Directory
Excalibur
Felix
Forrest
Geronimo
Gump
Hadoop
Harmony
HBase
HttpComponents
Jackrabbit
Jakarta
James
Lenya
Logging
Lucene
Mahout
Maven
Mina
MyFaces
Nutch
ODE
OFBiz
OpenEJB
OpenJPA
OpenWebBeans
PDFBox
Perl
Pivot
POI
Portals
Qpid
Roller
Santuario
ServiceMix
Shindig
Sling
SpamAssassin
STDCXX
Struts
Subversion
Synapse
Tapestry
Tika
TCL
Tiles
Tomcat
TrafficServer
Turbine
Tuscany
UIMA
Velocity
Wicket
Web Services
Xalan
Xerces
XML
XMLBeans
XML Graphics
Foundation
FAQ
Licenses
News
Blog
Public Records
Press Inquiries
Contact
Support Apache
Sponsorship
Donations
Buy Stuff
Thanks
Foundatio)

> git mirror for maven-surefire
> -----------------------------
>
>                 Key: INFRA-2823
>                 URL: https://issues.apache.org/jira/browse/INFRA-2823
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Kristian Rosenvold
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message