Comments (6)
The downside with dates is that it's hard to memorize which versions exist. Using consecutive natural numbers makes them a bit too opaque imho, and it's also harder to remember them IMHO.
So I'd actually propose we go with 2-part version numbers; and we declare the current version to be labeled as "1.0".
We can then have "http://pvp.haskell.org/v1.0" be the permalink to version 1.0, and have http://pvp.haskell.org/ redirect to the latest current version, i.e. pvp.haskell.org/v1.0
;
once there is say v1.1, we'd make sure that all non-latest versions have a warning at the top denoting this isn't the latest pvp-spec version.
from pvp.
I don't have a strong opinion about the versioning scheme PVP itself uses. Something based on dates or increasing natural numbers seems fine. Obviously I'm in favor of SemVer, but that might end up being more confusing than it's worth. I doubt anybody will be writing constraints against the PVP's version; "I comply with PVP >=1.2.3 && <3.4
", said no one ever. Just being able to point to pvp-123
is all that I'm after.
from pvp.
That's a sensible thing to do, and it's in fact one of the items I intended to address at some point....
But the reason I stalled so far is that it's not obvious to me which versioning scheme to apply to the PVP itself, and my brain hurts a little bit trying to think about what a formally sound scheme would be here, given the self-referential aspect... :-)
An informal scheme would maybe be to use a simplistic 2-number-component scheme (which makes it obvious that this is neither SemVer nor PVP). That version would only track semantically relevant changes (i.e. typos/layout etc which doesn't change the meaning would not be reflected in the version). IOW, we'd use a "major.minor" version; where "major" denotes breaking changes, and "minor" bumps denote "less breaking" changes. The big question is how to define what is a major breaking change to the versioning scheme, and what can be considered a "benign" minor change.
A trivial unstructured scheme would be to simply version by consecutive natural numbers, or alternatively by date (e.g. 20170922), but that's ugly imho.
One thing we can do once we have meta versioning is that we can annotate the pvp-version applying to a specific release inside the respective .cabal
file by e.g. a "x-pvp-spec: 1.0
" field; this would be rather essential for upcoming pvp validation tooling.
from pvp.
Hey, any update on this? I have a libraries proposal that would like to DEPRECATE a function but is blocked by #18 since we don't want to cause a major version bump. Thanks!
from pvp.
Bump!
from pvp.
Friendly ping on this, this is still blocking #18 which has caused the libraries proposal linked above to be in limbo for almost a year. Let me know what I can do to help move this along :)
from pvp.
Related Issues (20)
- Translations? HOT 1
- FAQ should mention x-uncurated
- Mention changing definitons of functions or values as Breaking change HOT 7
- new version number suggestions seem wrong? HOT 6
- Does removing a Cabal flag constitute a breaking change? HOT 3
- Block all HOT 2
- ## Overview HOT 1
- Remove the "2.0.1.0 > 2.0.1" example, or clarify that this is bad HOT 4
- Hav k HOT 2
- Missing logo
- Clarify rule two HOT 2
- condition 2 (Non-breaking changes) examples are too limited HOT 11
- (non-enforced) section on prerelease versions? HOT 3
- Do you need help with pvp.haskell.org? HOT 2
- The PVP should include advice about SafeHaskell HOT 2
- Tools section points to outdated tools, so remove or update it
- Clarify bumping policy for bug fixes HOT 4
- [RFC] Make PVP ecosystem/language agnostic HOT 24
- What is the goal of the PVP? HOT 21
- Remove point 7 about deprecation HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pvp.