Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC3: relax to allow updating programming language standard in minor versions. #4369

Merged
merged 2 commits into from
Jan 9, 2025
Merged

RFC3: relax to allow updating programming language standard in minor versions. #4369

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49cdde3
RFC3: relax to allow updating programming language standard in minor …
rouault Jan 6, 2025
8f045ba
Further updates to RFC3
kbevers Jan 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions docs/source/community/rfc/rfc-3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
-------------------------------------------------------------------------------
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.
Loading