Menu
▾
▴
[ jEdit-commits ] SF.net SVN: jedit:[19342] pjo/trunk/doc/releasing-jedit.txt
|
From: <Vam...@us...> - 2011-02-04 02:03:13
|
Revision: 19342
http://jedit.svn.sourceforge.net/jedit/?rev=19342&view=rev
Author: Vampire0
Date: 2011-02-04 02:03:05 +0000 (Fri, 04 Feb 2011)
Log Message:
-----------
Update step numbers
Modified Paths:
--------------
pjo/trunk/doc/releasing-jedit.txt
Modified: pjo/trunk/doc/releasing-jedit.txt
===================================================================
--- pjo/trunk/doc/releasing-jedit.txt 2011-02-04 00:24:23 UTC (rev 19341)
+++ pjo/trunk/doc/releasing-jedit.txt 2011-02-04 02:03:05 UTC (rev 19342)
@@ -17,11 +17,11 @@
svn copy https://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/branches/4.4.x https://jedit.svn.sourceforge.net/svnroot/jedit/jEdit/tags/jedit-4-4-pre2 -m "Tagging 4.4pre2 for release."
with the correct version in the second URL and in the commit message
-5. To be sure to work with the exact tagged source, check out the newly tagged source in a new directory by doing
+2. 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/jedit-4-4-pre2
no matter where. You will find the source in a subfolder jedit-4-4-pre2 where you executed the command
-6. Copy build.properties and jars/build.properties from your jEdit source directory to the newly created jedit-4-4-pre2 source directory. If you don't have the two, then create them. For the root directory you find a template called build.properties.sample there and for the jars/build.properties you find a template in build-support/build.properties. These are independent and have to be set up correctly. The one in the root directory is for jEdit itself, the one in jars is for the standard plugins.
+3. Copy build.properties and jars/build.properties from your jEdit source directory to the newly created jedit-4-4-pre2 source directory. If you don't have the two, then create them. For the root directory you find a template called build.properties.sample there and for the jars/build.properties you find a template in build-support/build.properties. These are independent and have to be set up correctly. The one in the root directory is for jEdit itself, the one in jars is for the standard plugins.
To give an example, in build.properties I customized the following properties:
- wine.executable=wine
- winepath.executable=winepath
@@ -38,7 +38,7 @@
You may not need to customize the same properties than me, e. g. if xsltproc is in your PATH environment variable, you may not need to customize xsltproc.executable.
For further information about what you need to build the source, please read README.SRC.txt in the sources root directory.
-7.1. Build the distribution files by doing
+4.1. Build the distribution files by doing
ant dist
in the jedit-4-4-pre2 directory
In the newly created directory jedit-4-4-pre2/dist you find 8 files:
@@ -51,21 +51,21 @@
- jedit4.4pre2install.exe or jedit4.4pre2-dist-win-finish.tar.bz2
- jedit4.4pre2install.dmg or jedit4.4pre2-dist-mac-finish.tar.bz2
-7.2. If you have jedit4.4pre2-dist-win-finish.tar.bz2 in your jedit-4-4-pre2/dist folder you probably don't run a Windows box and don't have wine installed and set up, so please hand over this file to someone (e. g. <Bj\xF6rn "Vampire" Kautler> Vampire@jEdit.org) who does and ask him to unpack the file and run
+4.2. If you have jedit4.4pre2-dist-win-finish.tar.bz2 in your jedit-4-4-pre2/dist folder you probably don't run a Windows box and don't have wine installed and set up, so please hand over this file to someone (e. g. <Bj\xF6rn "Vampire" Kautler> Vampire@jEdit.org) who does and ask him to unpack the file and run
ant dist-win-finish
and to hand over the resulting file jedit4.4pre2install.exe to you. The requirements for this are described in README.SRC.txt
-7.3. If you have jedit4.4pre2-dist-mac-finish.tar.bz2 in your jedit-4-4-pre2/dist folder you probably don't run a Mac OS X box, so please hand over this file to someone (e. g. Bj\xF6rn "Vampire" Kautler <Vampire@jEdit.org>) who does and ask him to unpack the file and run
+4.3. If you have jedit4.4pre2-dist-mac-finish.tar.bz2 in your jedit-4-4-pre2/dist folder you probably don't run a Mac OS X box, so please hand over this file to someone (e. g. Bj\xF6rn "Vampire" Kautler <Vampire@jEdit.org>) who does and ask him to unpack the file and run
ant dist-mac-finish
and to hand over the resulting file jedit4.4pre2install.dmg to you. The requirements for this are described in README.SRC.txt
-7.4. After you received the final distribution files jedit4.4pre2install.exe and jedit4.4pre2install.dmg you can delete jedit4.4pre2-dist-win-finish.tar.bz2 and jedit4.4pre2-dist-mac-finish.tar.bz2
+4.4. After you received the final distribution files jedit4.4pre2install.exe and jedit4.4pre2install.dmg you can delete jedit4.4pre2-dist-win-finish.tar.bz2 and jedit4.4pre2-dist-mac-finish.tar.bz2
-8. - Connect to the SourceForge servers via one of the methods described in https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download
+5. - Connect to the SourceForge servers via one of the methods described in https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download
- Add the sub-folder "4.4pre2" under "/home/frs/project/j/je/jedit/jedit-devel"
- Upload the 8 final distribution files to the newly created folder on the SourceForge servers
-9. - Go to https://sourceforge.net/projects/jedit/files/jedit-devel/4.4pre2/
+6. - Go to https://sourceforge.net/projects/jedit/files/jedit-devel/4.4pre2/
- Make the following settings for each file after clicking on the respective "i" icon
- jedit_4.4pre2_all.deb
- Download Button: Debian Installer
@@ -92,14 +92,14 @@
- Download Button: Slackware Installer
- Default Download For: <none>
-10. Update the website in the following places and also update this state in SVN:
+7. Update the website in the following places and also update this state in SVN:
- Open sftp://<your sf username>,je...@we.../home/groups/j/je/jedit/htdocs/download.html e. g. in jEdit with installed FTP plugin and update the website for the new release, means the filenames, filesizes and amount of pages in the User's Guides
- Open sftp://<your sf username>,je...@we.../home/groups/j/je/jedit/htdocs/jEdit-version.txt e. g. in jEdit with installed FTP plugin and update the versions in the file, which is needed by the LatestVersion Plugin
- Open sftp://<your sf username>,je...@we.../home/groups/j/je/jedit/htdocs/CHANGES44.txt e. g. in jEdit with installed FTP plugin and copy the contents of jedit-4-4-pre2/doc/CHANGES.txt to this file
- Open sftp://<your sf username>,je...@we.../home/groups/j/je/jedit/htdocs/index.php e. g. in jEdit with installed FTP plugin and update the version number and the Last Site Update date
- Open sftp://<your sf username>,je...@we.../home/groups/j/je/jedit/htdocs/devel.html e. g. in jEdit with installed FTP plugin and add a line for 4.4pre2 in the Release Schedule
-11. Update the plugin wizard
+8. Update the plugin wizard
- Go to http://plugins.jedit.org/wiz/release_add.php?package_id=24
- Enter the Version "4.4pre2"
- Switch "Head of Branch" to "devel"
@@ -108,15 +108,15 @@
- Click "Update Dependencies"
- Click "Create Release"
-12. Send an announcement eMail to the jEdit-announce list. The announcement should contain some announcing text and in the end the contents of jedit-4-4-pre2/doc/CHANGES.txt for this release.
+9. Send an announcement eMail to the jEdit-announce list. The announcement should contain some announcing text and in the end the contents of jedit-4-4-pre2/doc/CHANGES.txt for this release.
You have to be set up to be able to post to jEdit-announce list.
The mail should automatically get forwarded to the jedit-users list, but for that you have to be subscribed to that list too.
-13. Ask Vampire <Vampire@jEdit.org> (Vampire0@#jE...@ch...) to update the topic of the IRC Channel
+10. Ask Vampire <Vampire@jEdit.org> (Vampire0@#jE...@ch...) to update the topic of the IRC Channel
-14. Delete the jedit-4-4-pre2 folder
+11. Delete the jedit-4-4-pre2 folder
-15. Update the version number on the release branch
+12. Update the version number on the release branch
- Add the following section to doc/CHANGES.txt
{{{ Version 4.4pre3
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|