[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jedit-cvs
Subject:    [ jEdit-commits ] SF.net SVN: jedit:[23569] jEdit/trunk/doc/releasing-jedit.txt
From:       vampire0 () users ! sourceforge ! net
Date:       2014-05-26 15:41:56
Message-ID: E1Wox2F-00089a-Cz () sfs-ml-1 ! v29 ! ch3 ! sourceforge ! com
[Download RAW message or body]

Revision: 23569
          http://sourceforge.net/p/jedit/svn/23569
Author:   vampire0
Date:     2014-05-26 15:41:55 +0000 (Mon, 26 May 2014)
Log Message:
-----------
exchange SVN root URL in releasing-jedit.txt

Modified Paths:
--------------
    jEdit/trunk/doc/releasing-jedit.txt

Modified: jEdit/trunk/doc/releasing-jedit.txt
===================================================================
--- jEdit/trunk/doc/releasing-jedit.txt	2014-05-26 15:35:48 UTC (rev 23568)
+++ jEdit/trunk/doc/releasing-jedit.txt	2014-05-26 15:41:55 UTC (rev 23569)
@@ -15,14 +15,14 @@
 
 1. Execute the BeanShell snippet at the end of this file ("Utilities -> BeanShell -> \
Evaluate Selection"). This will replace the version tags in this document by actual \
version numbers for easy copy & paste.  
-2. Review http://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/branches/[branch]/doc/CHANGES.txt \
for formatting errors (like missing newline characters, wrong indentation or empty \
blocks), fix them and check them in. +2. Review \
https://svn.code.sf.net/p/jedit/svn/jEdit/branches/[branch]/doc/CHANGES.txt for \
formatting errors (like missing newline characters, wrong indentation or empty \
blocks), fix them and check them in.  
 3. Tag the sourcecode for release in the SVN repository by doing
-        svn copy https://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/branches/[branch] \
https://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/tags/[tag] -m "Tagging \
[version] for release." +        svn copy \
https://svn.code.sf.net/p/jedit/svn/jEdit/branches/[branch] \
https://svn.code.sf.net/p/jedit/svn/jEdit/tags/[tag] -m "Tagging [version] for \
release."  with the correct version in the second URL and in the commit message
 
 4. To be sure to work with the exact tagged source, check out the newly tagged \
                source in a new directory by doing
-        svn checkout \
https://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/tags/[tag] +        svn \
checkout https://svn.code.sf.net/p/jedit/svn/jEdit/tags/[tag]  no matter where. You \
will find the source in a subfolder [tag] where you executed the command  
 5. Copy build.properties from your jEdit source directory to the newly created [tag] \
source directory if needed. If you don't have it, then create it if needed. You find \
a template called build.properties.sample in the root directory.

This was sent by the SourceForge.net collaborative development platform, the world's \
largest Open Source development site.


------------------------------------------------------------------------------
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
_______________________________________________
jEdit-CVS mailing list
jEdit-CVS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-cvs


[prev in list] [next in list] [prev in thread] [next in thread]