-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
[feature] Add 'trip_short_name' into 'trips.txt' (NTFS v0.10.0) #455
Conversation
French](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_changelog_fr.md)). | ||
From the standard, some of the functionalities are not fully supported: | ||
- Management of pathways introduced in version `v0.8` is not supported | ||
- No support for all periodic description (files `grid_calendars.txt`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
148897a
to
2b13195
Compare
French](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_changelog_fr.md)). | ||
From the standard, some of the functionalities are not fully supported: | ||
- Management of pathways introduced in version `v0.8` is not supported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be removed since it has been done in #398.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it a PR needed for netex?
Cargo.toml
Outdated
@@ -1,7 +1,7 @@ | |||
[package] | |||
authors = ["Kisio Digital <[email protected]>", "Guillaume Pinot <[email protected]>"] | |||
name = "transit_model" | |||
version = "0.10.0" | |||
version = "0.11.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's a good idea. If this PR is merged, in the next PR I can also put 0.12.0 and deploys whereas 0.10.0 has never been deployed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, you wouldn't put 0.12.0
because you would check first what is the last released version. The idea is not to increment it everytime you do change something, the idea is just to verify that is coherent with 2 information:
- what is the last released version
- what kind of change my PR is doing, and keep or change the next version accordingly
Yes, we need to populate the |
2b13195
to
9dff77d
Compare
Pull request has been modified.
9dff77d
to
b87dbb0
Compare
Note: I'm bumping version of
transit_model
to0.11.0
since this is a breaking change.