Developer Info: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary |
|||
| Line 28: | Line 28: | ||
** [http://www.opendap.org/faq|Developer's FAQ] -- Information about using OPeNDAP's [http://scm.opendap.org:8090/trac/browser/ subversion repository]. | ** [http://www.opendap.org/faq|Developer's FAQ] -- Information about using OPeNDAP's [http://scm.opendap.org:8090/trac/browser/ subversion repository]. | ||
** [http://svnbook.red-bean.com/ Subversion documentation] -- The official Subversion documentation; [http://svnbook.red-bean.com/en/1.1/svn-book.pdf PDF] and [http://svnbook.red-bean.com/en/1.1/index.html HTML]. | ** [http://svnbook.red-bean.com/ Subversion documentation] -- The official Subversion documentation; [http://svnbook.red-bean.com/en/1.1/svn-book.pdf PDF] and [http://svnbook.red-bean.com/en/1.1/index.html HTML]. | ||
** [[OPeNDAP's Use of Trac]] -- | ** [[OPeNDAP's Use of Trac]] -- How to use Trac's various features in the software development process. | ||
Revision as of 17:35, 8 March 2012
- Nightly Builds: Software we build every night on several platforms. The link provides the most recent report for each build we do. Use show=current to get the most recent; show=<date> to get a particular date, show=<platform> to see a particular platform. The sort=yes option runs the results through Unix sort before building the table. The nightly build software is part of the nbuilds project and is available from our trac/svn repository.
- test.opendap.org: Test servers with data files.
Developer Guidelines and Information
- Development process information
- Using the SVN trunk, branches and tags to manage releases.
- Making a Branch of Shrew for a Server Release. Releases should be made from a branch so that development can continue on the trunk and so that we can easily go back to the software that mad up a release, fix bugs, and release those fixes.
- Making a Source Release. Once software is ready for distribution, use this checklist to make sure you do all of the steps needed to make a source release.
- How to configure a Linux machine to build Hyrax from SVN
- Making RPM Distributions. Follow these steps to create an RPM distribution of the software.
- Hyrax Package for OS-X. This describes how to make a new OS/X 'metapackage' for Hyrax.
- Making Windows XP distributions. Follow these directions to make Windows XP binaries.
- Making a Release of OLFS. Follow these steps to create the three .jar files needed for the OLFS release. Includes information on how to build the OLFS and how to run the tests.
- Making a Matlab Ocean Toolbox Release. Follow these steps when a new Matlab GUI version is ready to be released.
- General development information
- How to configure a CentOS machine for production of RPM binaries
- How to merge code
- How to copyright software written for OPeNDAP
- Development Guidelines
- How to Setup Secure Email and Sign Software Distributions
- How to Handle Email-list Support Questions
- Security Policy and Related Procedures
- Software version numbers
About Subversion
- FAQ -- Information about using OPeNDAP's subversion repository.
- Subversion documentation -- The official Subversion documentation; PDF and HTML.
- OPeNDAP's Use of Trac -- How to use Trac's various features in the software development process.
