-
Notifications
You must be signed in to change notification settings - Fork 234
Versioning Conventions
Version tagging is based on a major.minor.patch
numbering scheme.
-
The major number is incremented after extensive rewrites or substantial overhauls that may significantly affect workflow integration or user experience. Major updates undergo extensive testing, but subsequent patch updates may still be needed.
-
The minor number is incremented whenever modifications to the source code are significant enough to require updates to parameter files or other input files.
-
The patch number is used to denote bug fixes or other minor revisions. Updates to parameter files or other input files are not required.
In the past, tagged releases have been fairly infrequent because the associated testing is very time consuming. Now that a buildbot system and testing framework are being put in place, the frequency of such releases is expected to increase.
Development wiki for SPECFEM3D
Development wiki
- Home
- Development plan
- Best Practices
- Using Git for SPECFEM
- Advanced Git Topics
- Versioning Conventions
- Merging Development Branches into Master
User manual
- 01_introduction
- 02_getting_started
- 03_mesh_generation
- 04_creating_databases
- 05_running_the_solver
- 06_fault_sources
- 07_adjoint_simulations
- 08_doing_tomography
- 08b_performing_full_waveform_inversion_FWI_or_source_inversions
- 09_noise_simulations
- 10_gravity_calculations
- 11_graphics
- 12_running_scheduler
- 13_changing_the_model
- 14_post_processing
- 15_informations_for_developers
- A_reference_frame
- B_channel_codes
- C_troubleshooting
- D_license
- authors
- bug_reports
- copyright_and_version
- features
- manual_SPECFEM3D_Cartesian
- notes_and_acknowledgement
- sponsors