These pages are generated from files in
https://github.com/apache/synapse/tree/master/modules/documentation/src/site/xdoc/dev.
Shouldn't those files have been updated first?

Andreas

On Fri, May 12, 2023 at 5:48 PM <isud...@apache.org> wrote:

> Author: isudana
> Date: Fri May 12 16:48:49 2023
> New Revision: 1909778
>
> URL: http://svn.apache.org/viewvc?rev=1909778&view=rev
> Log:
> replace svn with git
>
> Modified:
>     synapse/site/dev/developer-guide.html
>     synapse/site/dev/release-process.html
>
> Modified: synapse/site/dev/developer-guide.html
> URL:
> http://svn.apache.org/viewvc/synapse/site/dev/developer-guide.html?rev=1909778&r1=1909777&r2=1909778&view=diff
>
> ==============================================================================
> --- synapse/site/dev/developer-guide.html (original)
> +++ synapse/site/dev/developer-guide.html Fri May 12 16:48:49 2023
> @@ -113,7 +113,7 @@
>  <ul>
>
>  <li>
> -                    <a href="#subversion">Interacting with the Code Base
> Using Subversion</a>
> +                    <a href="#git">Interacting with the Code Base Using
> Git</a>
>
>  <ul>
>
> @@ -149,19 +149,14 @@
>                  </li>
>              </ul>
>          </div>
> -        <a name="subversion"></a>
> -<div class="section" id="subversion">
> -<h2><a
> name="Interacting_with_the_Code_Base_Using_Subversion"></a>Interacting with
> the Code Base Using Subversion</h2>
> +        <a name="git"></a>
> +<div class="section" id="git">
> +<h2><a name="Interacting_with_the_Code_Base_Using_Git"></a>Interacting
> with the Code Base Using Git</h2>
>
>  <p>
> -                Synapse code base is maintained in a Subversion
> repository. Therefore, anyone willing
> +                Synapse code base is maintained in a Github repository.
> Therefore, anyone willing
>                  to go through the Synapse source code in the development
> trunk and make contributions
> -                should use a Subversion client to interact with the
> Synapse code base. To learn more
> -                about using Subversion or to download the latest client
> distributions, please visit
> -                the <a class="externalLink" href="
> http://subversion.apache.org";>Apache Subversion project website</a>.
> -                Developers on Unix/Linux based systems may use the
> command line based SVN client,
> -                while the developers on Windows platform can use an
> appropriate client application
> -                like <a class="externalLink" href="
> http://tortoisesvn.net/";>TortoiseSVN</a>.
> +                should use a Git client to interact with the Synapse code
> base.
>              </p>
>
>  <p>
> @@ -176,26 +171,19 @@
>  <p>
>                      Synapse development trunk is where all the latest
> development work takes place.
>                      This is located at
> -                    <a class="externalLink" href="
> http://svn.apache.org/repos/asf/synapse/trunk/java/";>
> http://svn.apache.org/repos/asf/synapse/trunk/java/</a>.
> -                    Any developer with a Subversion client should be able
> to checkout the latest
> -                    source from this SVN location but only Synapse
> committers are allowed to actually
> -                    commit source code. Synapse committers should access
> the above SVN location over
> -                    HTTPS and provide the ASF committer credentials to
> checkout and commit source
> -                    code. Please refer the <a
> href="../source-repository.html">source repository guide</a>
> -                    for more details on checking out the source code from
> the above repository.
> +                    <a class="externalLink" href="
> https://github.com/apache/synapse.git";>
> https://github.com/apache/synapse.git</a>.
> +                    Any developer with a Git client should be able to
> checkout the latest
> +                    source from this Github location but only Synapse
> committers are allowed to actually
> +                    commit source code.
>                  </p>
>
>  <p>
> -                    Once you have checked out the source code, you can
> update your working copy by
> -                    running the 'svn update' command. This will checkout
> the modifications since the
> -                    last checkout/update and bring your local working
> copy to the latest revision.
> -                </p>
> -
> +
>  <p>
>                      If you want to browse the source code of an older
> release of Synapse or want
>                      to implement a patch for a past release, you may
> checkout the relevant source
> -                    tree from one of the available SVN
> -                    <a class="externalLink" href="
> http://svn.apache.org/repos/asf/synapse/tags/";>tags</a>.
> +                    tree from one of the available Github
> +                    <a class="externalLink" href="
> https://github.com/apache/synapse/tags";>tags</a>.
>                  </p>
>              </div>
>          </div>
> @@ -388,28 +376,10 @@ For Eclipse: mvn eclipse:eclipse</div>
>                  If you have implemented a new feature, fixed some bug in
> the code or written a new
>                  sample, we'll be more than happy to review it and include
> it in the Synapse code
>                  base for everyone's benefit. If you are interested in
> contributing your work to Synapse,
> -                please create an issue in the JIRA system first. Then you
> can attach your workings to
> -                the JIRA issue as a patch.
> -            </p>
> -
> -<p>
> -                To create a patch file out of your work simply run the
> 'svn diff' command.
> +                please create an issue in the JIRA system first. Then you
> can send a pull request with your workings
> +                to Github repository and mention the pull request url in
> the JIRA issue.
>              </p>
>
> -<div class="command">svn diff &gt; FixForIssue123.patch</div>
> -
> -<p>
> -                If you added any new files as a part of your work you
> should first run the 'svn add'
> -                command on them before creating the patch file. Otherwise
> they won't be included
> -                in the generated patch.
> -            </p>
> -
> -<p>
> -                Once the patch file has been created, attach it to the
> relevant JIRA issue and make
> -                sure to grant the ASF permission to use your patch in ASF
> development activities.
> -                One of the committers will review your work and provide
> feedback through the JIRA. If
> -                all is well, the patch will eventually go into the
> Synapse development trunk.
> -            </p>
>          </div>
>
>
>
> Modified: synapse/site/dev/release-process.html
> URL:
> http://svn.apache.org/viewvc/synapse/site/dev/release-process.html?rev=1909778&r1=1909777&r2=1909778&view=diff
>
> ==============================================================================
> --- synapse/site/dev/release-process.html (original)
> +++ synapse/site/dev/release-process.html Fri May 12 16:48:49 2023
> @@ -94,9 +94,7 @@
>                  One of the committers would volunteer to play the release
> manager role for a given
>                  release. A few days will be spent on stabilizing the
> Synapse development trunk,
>                  improving its documentation and test coverage. When the
> code base is in a satisfactory
> -                state a release branch would be created under
> -                <a class="externalLink" href="
> https://svn.apache.org/repos/asf/synapse/branches";>
> https://svn.apache.org/repos/asf/synapse/branches</a>.
> -                .
> +                state a release branch would be created.
>              </p>
>
>  <p>
>
>
>

Reply via email to