Apache OpenOffice Wiki - User contributions [en]

https://wiki.openoffice.org/w/api.php?action=feedcontributions&feedformat=atom&user=Mayongl Apache OpenOffice Wiki - User contributions [en] 2026-06-18T05:59:37Z User contributions MediaWiki 1.35.14 https://wiki.openoffice.org/w/index.php?title=Symphony&diff=202283 Symphony 2012-06-18T01:30:59Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The the code is formally ready on 18 Jun 2012. <br /> <br /> This page is an introduction of the code contribution and how it can be used. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> The code is now ready at<br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel described here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> '''Q: What is the difference between this build and Symphony?'''<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> '''Q: I can find two kinds of help content in the source code, why?'''<br /> <br /> A: The help system of Symphony 3.1 is eclipse based. The Symphony help content can't be consumed by AOO directly. AOO or OO.o help mechanism is used in the code contribution.<br /> <br /> OO.o 3.x help content is there to be packaged in the the binary build of the "Symphony code contribution". Symphony 3.1 help content is there for reference of Symphony features.<br /> <br /> '''Q: Does this contain everything we get in AOO 3.4? Or what is the difference?'''<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=202185 Symphony 2012-06-14T01:49:22Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready is a test trunk. But it has been verified as buildable and workable.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel described here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> '''Q: What is the difference between this build and Symphony?'''<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> '''Q: I can find two kinds of help content in the source code, why?'''<br /> <br /> A: The help system of Symphony 3.1 is eclipse based. The Symphony help content can't be consumed by AOO directly. AOO or OO.o help mechanism is used in the code contribution.<br /> <br /> OO.o 3.x help content is there to be packaged in the the binary build of the "Symphony code contribution". Symphony 3.1 help content is there for reference of Symphony features.<br /> <br /> '''Q: Does this contain everything we get in AOO 3.4? Or what is the difference?'''<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201817 Svn practices 2012-06-06T12:48:16Z

<p>Mayongl: </p> <hr /> <div>'''This page is under review. This line will be removed after it is done.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> SVN Client 1.7 is recommanded to use for AOO development.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw</nowiki><br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended if you are commit a patch. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for cross reference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <nowiki>svn copy https://svn.apache.org/repos/asf/incubator/ooo/trunk \<br /> https://svn.apache.org/repos/asf/incubator/ooo/branches/tocloading \<br /> -m "Creating a private branch for toc loading of word document."</nowiki><br /> <br /> *Keep a branche in sync<br /> Subversion is aware of the history of your branch and knows when it split away from the mainline. To perform a sync merge, first make sure your working copy of the branch is “clean”—that it has no local modifications reported by 'svn status'. Then simply run:<br /> <br /> $ pwd<br /> /home/user/tocloading <br /> <br /> $ svn merge ^/ooo/trunk<br /> <br /> *Reintegrate a branche<br /> When your new feature is done. It needs to be merged back to mainline. Before do that, sync the brache with mainline and commit your changes. Then<br /> <br /> $ svn merge --reintegrate ^/ooo/branches/tocloading<br /> <br /> and commit again<br /> <br /> *Remove a branche<br /> Once a branche is integrated back. It is useless and can be removed.<br /> <br /> $ svn delete ^/ooo/branches/tocloading -m "Remove branche of toc loading" <br /> <br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> SVN Best Practices<br /> http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html<br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201815 Svn practices 2012-06-06T12:23:36Z

<p>Mayongl: </p> <hr /> <div>'''This page is under review. This line will be removed after it is done.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> SVN Client 1.7 is recommanded to use for AOO development.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw</nowiki><br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended if you are commit a patch. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for cross reference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <nowiki>svn copy https://svn.apache.org/repos/asf/incubator/ooo/trunk \<br /> https://svn.apache.org/repos/asf/incubator/ooo/branches/tocloading \<br /> -m "Creating a private branch for toc loading of word document."</nowiki><br /> <br /> *How to merge change in branche back to mainline<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> SVN Best Practices<br /> http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html<br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201814 Svn practices 2012-06-06T12:10:52Z

<p>Mayongl: </p> <hr /> <div>'''This page is under review. This line will be removed after it is done.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> SVN Client 1.7 is recommanded to use for AOO development.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for cross reference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <br /> *How to merge change in branche back to mainline<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> SVN Best Practices<br /> http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html<br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201811 Svn practices 2012-06-06T09:09:55Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for cross reference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <br /> *How to merge change in branche back to mainline<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201810 Svn practices 2012-06-06T09:07:08Z

<p>Mayongl: /* Working with branch */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <br /> *How to merge change in branche back to mainline<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201809 Svn practices 2012-06-06T09:06:01Z

<p>Mayongl: /* Working with branch */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> Change you will made is complicated or you want to share it with others during development.<br /> <br /> You may also need work with brache created by others. For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> Instead of doing 'svn commit' twice, 'svn merge' should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> There are also other cases in which you don't want to commit in development mainline directly. <br /> <br /> *How to create a branche <br /> <br /> <br /> *How to merge change in brache back to mainline<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201808 Svn practices 2012-06-06T09:01:58Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /><br /> svn log -v<br /><br /> svn log -r m<br /><br /> svn log filename<br /><br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> <br /> Know how to work with branch is also helpful even you don't get your own branch.<br /> For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> svn merge should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201807 Svn practices 2012-06-06T09:00:59Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> <nowiki>svn log<br /> svn log -v<br /> svn log -r m<br /> svn log filename</nowiki><br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> <br /> Know how to work with branch is also helpful even you don't get your own branch.<br /> For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> svn merge should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201806 Svn practices 2012-06-06T09:00:25Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes history<br /> <br /> svn log<br /> svn log -v<br /> svn log -r m<br /> svn log filename<br /> <br /> *Check changes & Create patch for specific revision<br /> <br /> svn diff -r m:n > n.patch<br /> <br /> ==Write access==<br /> *Commit your changes<br /> Change can be comitted in by <br /> svn commit -m "comment" <br /> However, this is not recommended. Since it is lack of information for contributors and may also cause unwanted changes.<br /> <br /> *Check changes before commit<br /> <br /> svn status<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> svn commit change1 change2<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit -F ../mychangelog.txt change1 change2<br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> <br /> Know how to work with branch is also helpful even you don't get your own branch.<br /> For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> svn merge should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201800 Svn practices 2012-06-06T08:12:09Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> svn co https://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34/main/sw sw<br /> <br /> This get the source code for writer module from AOO34 branche<br /> <br /> *Get the latest changes into your working copy.<br /> <br /> execute 'svn update' in working directory. It is ooo or sw for above cases.<br /> <br /> This command will attempt to merge the public changes with the local changes if any.<br /> <br /> *Update to a specific revision<br /> <br /> svn update -r xxxx<br /> <br /> *Check changes in specific revision<br /> svn diff<br /> <br /> ==Write access==<br /> *Commit your changes<br /> <br /> *Check changes before commit<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> <br /> Know how to work with branch is also helpful even you don't get your own branch.<br /> For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> svn merge should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201781 Svn practices 2012-06-05T09:30:10Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> *Update your tree<br /> svn update<br /> <br /> *Update to a specific revision<br /> <br /> *Check changes in specific revision<br /> svn diff<br /> <br /> ==Write access==<br /> *Commit your changes<br /> <br /> *Check changes before commit<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> <br /> == Working with branch ==<br /> There at least two situations that you need work with branche.<br /> <br /> Know how to work with branch is also helpful even you don't get your own branch.<br /> For example, after AOO 3.4 is released, a branch for AOO 3.4.1 was created. <br /> <br /> svn merge should be used if you get a fix need be submitted to both the 3.4.1 branch and main line.<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book:<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201778 Svn practices 2012-06-05T07:38:53Z

<p>Mayongl: /* Write access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> *Update your tree<br /> svn update<br /> <br /> *Update to a specific revision<br /> <br /> *Check changes in specific revision<br /> svn diff<br /> <br /> ==Write access==<br /> *Commit your changes<br /> <br /> *Check changes before commit<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> *Template for the log files should be used<br /> <br /> Patch by:<br /> Suggested by:<br /> Found by:<br /> Review by:<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201777 Svn practices 2012-06-05T07:23:20Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> *Grab a branche<br /> <br /> *Update your tree<br /> svn update<br /> <br /> *Update to a specific revision<br /> <br /> *Check changes in specific revision<br /> svn diff<br /> <br /> ==Write access==<br /> *Commit your changes<br /> <br /> *Check changes before commit<br /> <br /> *Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> *Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> *How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> *How to merge your changes<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201776 Svn practices 2012-06-05T07:21:02Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> *Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> *Grab a branche<br /> *Update your tree<br /> *Update to a specific revision<br /> *Check changes in specific revision<br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201775 Svn practices 2012-06-05T07:19:26Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> #Grab the whole source code from main trunk<br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> #Grab a branche<br /> <br /> #Update your tree<br /> #Update to a specific revision<br /> Check changes in specific revision<br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201774 Svn practices 2012-06-05T07:18:52Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> Grab the whole source code from main trunk<br /> <br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> <br /> #Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision<br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201773 Svn practices 2012-06-05T07:17:55Z

<p>Mayongl: /* Read-only access */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> Grab the whole source code from main trunk<br /> <br /> <nowiki>svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk ooo</nowiki><br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision<br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201772 Svn practices 2012-06-05T07:16:13Z

<p>Mayongl: /* Reference */</p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> SVN book<br /> http://svnbook.red-bean.com/en/1.7/svn-book.html<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201771 Svn practices 2012-06-05T06:38:26Z

<p>Mayongl: </p> <hr /> <div>'''This page is still in draft. This line will be removed after the page been reviewed.'''<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.<br /> <br /> __TOC__<br /> <br /> ==Read-only access==<br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> ==Write access==<br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> A guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201770 Symphony 2012-06-05T06:35:10Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel described here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> Q: Does this contain everything we get in AOO 3.4? Or what is the difference.<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201769 Symphony 2012-06-05T06:34:49Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel described here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> Q: Does this contain everything we get in AOO 3.4? Or what is the difference.<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201768 Svn practices 2012-06-05T06:34:11Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> __TOC__<br /> ==Read-only access==<br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> ==Write access==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201767 Svn practices 2012-06-05T06:33:31Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> <br /> ==Read-only access==<br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> <br /> ==Write access==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201766 Svn practices 2012-06-05T06:32:34Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> <br /> <br /> ==Read-only access==<br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> <br /> ==Write access==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201765 Svn practices 2012-06-05T06:28:54Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> <br /> <br /> ==Read-only access==<br /> <br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> <br /> ==Write access==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201764 Svn practices 2012-06-05T06:28:38Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> <br /> <br /> ==Read-only access==<br /> <br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> <br /> ==Write access==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> ==Reference==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201763 Svn practices 2012-06-05T06:27:20Z

<p>Mayongl: </p> <hr /> <div>This page is still under review.<br /> <br /> This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.<br /> <br /> <br /> == Read-only access ==<br /> <br /> Grab the whole source code<br /> <br /> Grab a branche<br /> <br /> Update your tree<br /> <br /> Update to a specific revision<br /> <br /> Check changes in specific revision <br /> <br /> <br /> == Write access ==<br /> There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> Commit your changes<br /> <br /> Check changes before commit<br /> <br /> Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.<br /> <br /> Template for the log files should be used<br /> <br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> Do not use 'svn commit -m "Your comment". <br /> <br /> Update bugzilla with revision information for crossreference when you are done with the commit<br /> <br /> How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly. <br /> <br /> How to merge your changes<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> <br /> == Reference ==<br /> <br /> Merge Instruction from FreeBSD:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201761 Svn practices 2012-06-05T06:05:35Z

<p>Mayongl: </p> <hr /> <div><br /> This page is still under review.<br /> <br /> 1) Read-only access. This is meant for people that<br /> don't know that well what version control is but<br /> want to grab the code and play with it.<br /> <br /> It should contain how to do a checkout, update<br /> your tree, what the branches are and how to<br /> apply, revert or generate patches, It's<br /> actually a good practice to use svn diff to<br /> generate patches as it contains the information<br /> of the specific revision used to generate it.<br /> <br /> 2) Write access. There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> But I actually think that a quick guide that explains<br /> how to set the default properties and how to do the<br /> simple tasks would be great. My tips here are<br /> <br /> I highly recommend:<br /> <br /> 1) specifying in the command line a list of the<br /> files/dirs that are changed to avoid accidentally<br /> committing unwanted changes.<br /> <br /> 2) Use of a template for the log file with the<br /> author and other information.<br /> This is wrong:<br /> svn commit -m "My changes"<br /> This is right:<br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> 3) Remind people to add the revision information<br /> in Bugzilla for crossreference, if it applies.<br /> <br /> This chapter should also explain how to create<br /> branches for bigger tasks and how to merge<br /> changes to a branch.<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> instructions:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> Of course FreeBSD is more complex in structure<br /> and has many more committers so some additional<br /> rules are in place:<br /> <br /> In general we don't commit things directly<br /> to the branches unless we have to and in that<br /> case the Release Engineer has to approve the<br /> change. There's no such thing as lazy consensus<br /> there ;). We also set as minimum three days (I<br /> usually take a couple of weeks) before merging<br /> any change to the stable branch.</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Svn_practices&diff=201760 Svn practices 2012-06-05T06:04:28Z

<p>Mayongl: Created page with "This page is still under review. 1) Read-only access. This is meant for people that don't know that well what version control is but want to grab the code and play with it. It …"</p> <hr /> <div>This page is still under review.<br /> <br /> 1) Read-only access. This is meant for people that<br /> don't know that well what version control is but<br /> want to grab the code and play with it.<br /> <br /> It should contain how to do a checkout, update<br /> your tree, what the branches are and how to<br /> apply, revert or generate patches, It's<br /> actually a good practice to use svn diff to<br /> generate patches as it contains the information<br /> of the specific revision used to generate it.<br /> <br /> 2) Write access. There is a guide for new committers:<br /> http://www.apache.org/dev/new-committers-guide.html<br /> <br /> But I actually think that a quick guide that explains<br /> how to set the default properties and how to do the<br /> simple tasks would be great. My tips here are<br /> <br /> I highly recommend:<br /> <br /> 1) specifying in the command line a list of the<br /> files/dirs that are changed to avoid accidentally<br /> committing unwanted changes.<br /> <br /> 2) Use of a template for the log file with the<br /> author and other information.<br /> This is wrong:<br /> svn commit -m "My changes"<br /> This is right:<br /> svn commit ci -F ../mychangelog.txt change1 change2<br /> <br /> 3) Remind people to add the revision information<br /> in Bugzilla for crossreference, if it applies.<br /> <br /> This chapter should also explain how to create<br /> branches for bigger tasks and how to merge<br /> changes to a branch.<br /> <br /> For reference, FreeBSD has a SVN Primer,<br /> and the Merging section has some complete<br /> instructions:<br /> http://wiki.freebsd.org/SubversionPrimer/Merging<br /> <br /> Of course FreeBSD is more complex in structure<br /> and has many more committers so some additional<br /> rules are in place:<br /> <br /> In general we don't commit things directly<br /> to the branches unless we have to and in that<br /> case the Release Engineer has to approve the<br /> change. There's no such thing as lazy consensus<br /> there ;). We also set as minimum three days (I<br /> usually take a couple of weeks) before merging<br /> any change to the stable branch.</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201571 Symphony 2012-05-29T02:55:42Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel described here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> Q: Does this contain everything we get in AOO 3.4? Or what is the difference.<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201570 Symphony 2012-05-29T02:53:49Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> Q: Does this contain everything we get in AOO 3.4? Or what is the difference.<br /> <br /> A: This is not based on AOO 3.4. Symphony 3.0 was developed based on OO.o3.1. And while it goes some improvments from AOO 3.2, 3.3 and 3.4beta were also integrated. Before it was contributed to ASF, most of changes from AOO 3.4 were also integrated. <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201365 Symphony 2012-05-23T02:14:51Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code temporarily from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> '''IMPORTANT:'''<br /><br /> You still need get some extra source modules from AOO3.4 to make the code base buildable, which includes main/ext_libraries, main/ext_sources. And icu 4.8.1 source can be download from http://download.icu-project.org/files/icu4c/4.8.1/icu4c-4_8_1-src.tgz, then change it's name to af36f635271a239d76d038d6cf8da8df-icu4c-4_8_1-src.tgz and put it in main/ext_sources directory.<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> Q: Does this contain everything we get in AOO 3.4? Or what is the difference.<br /> <br /> A: <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201284 Symphony 2012-05-21T01:49:06Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code is ready for verify.<br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> You can get the code from <br /> <br /> https://svn-master.apache.org/repos/test/danielsh/symphony-import/<br /> <br /> Finally the code will be available at: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201211 Symphony 2012-05-18T07:44:38Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==Build guide==<br /> <br /> Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it paralell to Apache OpenOffice 3.4 by following guide<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> <br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201201 Symphony 2012-05-18T07:23:44Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort. <br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==Build guide==<br /> <br /> Will be available soon<br /> <br /> ==The binary build==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> Optionally, you can install development version, paralell to Apache OpenOffice 3.4<br /> *[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> Q: What is the difference between this build and Symphony?<br /> A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.<br /> And menu, toolbar, statusbar also have different look&feel from that in Symphony. <br /> <br /> The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.<br /> <br /> Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package. <br /> <br /> <br /> <br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201132 Symphony 2012-05-17T03:39:44Z

<p>Mayongl: /* The binary build of it */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==Build guide==<br /> <br /> Will be available soon<br /> <br /> ==The binary build of it==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> <br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201131 Symphony 2012-05-17T03:39:19Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get the source code==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==Build guide==<br /> <br /> Will be available soon<br /> <br /> ==The binary build of it==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201130 Symphony 2012-05-17T03:38:12Z

<p>Mayongl: /* How to get the binary build of it */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get it==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==The binary build of it==<br /> <br /> You can build this out yourself by following the build guide. You can also get it from link below.<br /> Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first.<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201129 Symphony 2012-05-17T03:33:02Z

<p>Mayongl: /* Introduction of the code base */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.<br /> <br /> ==Where to get it==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==How to get the binary build of it==<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201128 Symphony 2012-05-17T03:07:58Z

<p>Mayongl: /* How this can be reused */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> ==Where to get it==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==How to get the binary build of it==<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==FAQ==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201127 Symphony 2012-05-17T03:06:15Z

<p>Mayongl: /* How to get it */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> ==Where to get it==<br /> <br /> the code will be checked into: (Not ready yet) <br /> <br /> https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk<br /> <br /> ==How to get the binary build of it==<br /> <br /> *[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==How this can be reused==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201123 Symphony 2012-05-17T02:04:38Z

<p>Mayongl: /* How to get the binary build of it */</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> ==Introduction of the code base==<br /> <br /> ==How to get it==<br /> <br /> ==How to get the binary build of it==<br /> <br /> http://<br /> <br /> ==Feature Description==<br /> *[[Symphony contribution]]<br /> <br /> ==How this can be reused==<br /> <br /> [[Category:Documentation]]</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201099 Symphony 2012-05-16T08:58:53Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> '''Introduction of the code base:<br /> <br /> '''How to get it:<br /> <br /> '''How to get the binary build of it:'''<br /> <br /> '''Feature Description:'''<br /> <br /> http://wiki.services.openoffice.org/wiki/Symphony_contribution<br /> <br /> '''How this can be reused:</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201098 Symphony 2012-05-16T08:55:02Z

<p>Mayongl: </p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> '''Introduction of the code base:<br /> '''<br /> '''How to get it:<br /> '''<br /> '''How to get the binary build of it:'''<br /> <br /> '''Feature Description:'''<br /> <br /> http://wiki.services.openoffice.org/wiki/Symphony_contribution<br /> <br /> '''How this can be reused:<br /> '''</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201097 Symphony 2012-05-16T08:53:23Z

<p>Mayongl: </p> <hr /> <div><br /> IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> The code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> Introduction of the code base:<br /> <br /> How to get it:<br /> <br /> How to get the binary build of it:<br /> <br /> Feature Description:<br /> <br /> How this can be reused:</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=User:Mayongl&diff=201095 User:Mayongl 2012-05-16T08:44:08Z

<p>Mayongl: Created page with "I am from IBM. Erik Ma"</p> <hr /> <div>I am from IBM.<br /> <br /> Erik Ma</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=Symphony&diff=201094 Symphony 2012-05-16T08:31:01Z

<p>Mayongl: Created page with "IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. Now the code will be available soon. This page is special for the code contribut…"</p> <hr /> <div>IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011. <br /> Now the code will be available soon. <br /> <br /> This page is special for the code contribution effort.<br /> <br /> Introduction of the code base:<br /> <br /> How to get it:<br /> <br /> How to get the binary build of it:<br /> <br /> Feature Description:<br /> <br /> How this can be reused:</div>

Mayongl https://wiki.openoffice.org/w/index.php?title=User:Mayongl/Books/AOO_Cookbook&diff=199343 User:Mayongl/Books/AOO Cookbook 2012-02-15T02:23:22Z

<p>Mayongl: Created page with "{{saved_book}} == AOO Cookbook == === Startup Guide for Developers === :Build Environment Effort/Status And Next Steps :Passive Component Registration [[Category:Books|…"</p> <hr /> <div>{{saved_book}}<br /> <br /> == AOO Cookbook ==<br /> === Startup Guide for Developers ===<br /> :[[Build Environment Effort/Status And Next Steps]]<br /> :[[Passive Component Registration]]<br /> <br /> [[Category:Books|AOO Cookbook]]</div>

Mayongl