Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "HowToContribute" page has been changed by HansHenrikRavn: http://wiki.apache.org/solr/HowToContribute?action=diff&rev1=73&rev2=74 Note that committers have to use [[http://apache.org/dev/committers.html#commit-403|https]] instead of http here, but http is fine for read-only access to the trunk code. If you prefer you could use the [[https://github.com/apache/lucene-solr|GitHub]] mirror instead. + + == Exporting to a local repository == + When making larger scale (please, try to keep your patches as small as humanly possible) changes, or when working in a team, you might want to be able to keep track of what you are doing locally. One way of doing so, is exporting to a local SVN repository. + + A proposed strategy for switching/exporting to a local SVN repository; + * get the source from the repository (baseline) + * export to local svn (local baseline) + * loop + * do work on local baseline (now work) + * commit + * draw a line + * do a (unix*) diff of local baseline <-> work (ignore anything that shouldn't go in the patch) + * patch apache baseline + * (unix) diff apache baseline <-> work (confirm is empty, or at least looking fine) + * svn diff apache baseline, resulting in final patch + + * by doing a unix diff, you keep any local version out of the patch file. == Making Changes == Before you start, you should send a message to the [[http://lucene.apache.org/solr/mailing_lists.html|Solr developer mailing list]] (Note: you have to subscribe before you can post), or file a bug in [[http://issues.apache.org/jira/browse/SOLR|Jira]]. Describe your proposed changes and check that they fit in with what others are doing and have planned for the project. Be patient, it may take folks a while to understand your requirements.
