-
Notifications
You must be signed in to change notification settings - Fork 797
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
RFC3: relax to allow updating programming language standard in minor …
…versions. (#4369) * RFC3: relax to allow updating programming language standard in minor versions. * Further updates to RFC3 --------- Co-authored-by: Kristian Evers <[email protected]>
- Loading branch information
Showing
1 changed file
with
10 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ PROJ RFC 3: Dependency management | |
:Author: Kristian Evers | ||
:Contact: [email protected] | ||
:Status: Adopted | ||
:Last Updated: 2019-01-16 | ||
:Last Updated: 2025-01-07 | ||
|
||
Summary | ||
------------------------------------------------------------------------------- | ||
|
@@ -31,10 +31,12 @@ With adoption of this RFC, versions used for | |
2. software packages will always be at least two years old | ||
(patch releases are exempt) | ||
|
||
A change in programming language standard can only be introduced with a new | ||
major version release of PROJ. Changes for software package dependencies can be | ||
Changes for programming languages or software package dependencies can be | ||
introduced with minor version releases of PROJ. Changing the version | ||
requirements for a dependency needs to be approved by the PSC. | ||
requirements for a dependency needs to be approved by the PSC. Following | ||
a change in dependency version the build requirements needs to be updated | ||
and the changes be clearly stated in the release notes for the affected PROJ | ||
version. | ||
|
||
Following the above rule set will ensure that all but the most conservative | ||
users of PROJ will be able to build and use the most recent version of the | ||
|
@@ -99,8 +101,7 @@ change to C99 is possible, as long as the PROJ PSC acknowledges such a change. | |
When a new standard for either C or C++ is released PROJ should consider | ||
changing its requirement to the next standard in the line. For C++ that means a | ||
change in standard roughly every three years, for C the periods between | ||
standard updates is expected to be longer. Adaptation of new programming | ||
language standards should be coordinated with a major version release of PROJ. | ||
standard updates is expected to be longer. | ||
|
||
|
||
Software dependencies | ||
|
@@ -149,3 +150,6 @@ The RFC was adopted on 2018-01-19 with +1's from the following PSC members | |
* Even Rouault | ||
* Thomas Knudsen | ||
* Howard Butler | ||
|
||
Amendment on January 2025 to allow updating programming language standard in | ||
minor versions. |