Developer Info: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary |
|||
| Line 5: | Line 5: | ||
== Developer Guidelines and Information == | == Developer Guidelines and Information == | ||
=== Development process information === | == General development information == | ||
These pages contain general information relevant to anyone working with our software: | |||
* [[LinuxBuildHostConfig| How to configure a Linux machine to build Hyrax from SVN]] | |||
* [[ConfigureCentos| How to configure a CentOS machine for production of RPM binaries]] | |||
* [[ConfigureSUSE| How to configure a SUSE machine for production of RPM binaries]] | |||
== Development process information (OPeNDAP Specific) == | |||
These pages contain information about how we'd like people working with us to use our various on-line tools. | |||
===== Using revision control: ===== | |||
* [[TrunkDevelBranchRel | Using the SVN trunk, branches and tags to manage releases]]. | * [[TrunkDevelBranchRel | Using the SVN trunk, branches and tags to manage releases]]. | ||
* [[ShrewBranchGuide | 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. | * [[ShrewBranchGuide | 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. | ||
* [[ReleaseGuide | 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. | * [[ReleaseGuide | 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. | ||
* [[ | * [[MergingBranches |How to merge code]] | ||
===== Making specific kinds of packages for release: ===== | |||
* [[RPM |Making RPM Distributions]]. Follow these steps to create an RPM distribution of the software. | * [[RPM |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. | * [[Hyrax Package for OS-X]]. This describes how to make a new OS/X 'metapackage' for Hyrax. | ||
| Line 16: | Line 28: | ||
* [[ReleaseToolbox |Making a Matlab Ocean Toolbox Release]]. Follow these steps when a new Matlab GUI version is ready to be released. | * [[ReleaseToolbox |Making a Matlab Ocean Toolbox Release]]. Follow these steps when a new Matlab GUI version is ready to be released. | ||
=== | ===== Software process issues: ===== | ||
* [[CopyRights| How to copyright software written for OPeNDAP]] | * [[CopyRights| How to copyright software written for OPeNDAP]] | ||
* [[GuideLines| Development Guidelines]] | * [[GuideLines| Development Guidelines]] | ||
Revision as of 20:46, 4 May 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
General development information
These pages contain general information relevant to anyone working with our software:
- How to configure a Linux machine to build Hyrax from SVN
- How to configure a CentOS machine for production of RPM binaries
- How to configure a SUSE machine for production of RPM binaries
Development process information (OPeNDAP Specific)
These pages contain information about how we'd like people working with us to use our various on-line tools.
Using revision control:
- 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 merge code
Making specific kinds of packages for release:
- 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.
Software process issues:
- 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.
