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
1.2 Release #2483
Comments
Any chance pending PR's will get merged for the release? I've got two-
|
Could we also get some longtime PRs merged in?
|
Thanks @sdjacobs and @seime for the reminders. We're producing this release for immediate use so I'm a little wary of including too many recently merged features. On the other hand we have evidence that all of these have been working well in your deployments, which is better than we've had for many merges in the past. I may not merge everything but I'm going to merge at least those that pass all checks and appear incapable of causing any problems for other people's existing deployments. The others we can merge just after the release, for inclusion in the next release (which should be fairly soon because we've got some fixes of our own to include). |
I've just merged all of them except #2449. That one has the potential to change routes drastically, so I'm still reviewing it more closely but I don't think it can possibly have any unexpected impact unless someone sets options.compactLegsByReversedSearch=true. |
The release has been pushed and is now being built and deployed to Maven Central. |
We would like to cut a 1.2 release of OTP. We've gotten requests for several items currently in the master branch including GBFS support and the fix for issue #2404.
Here is the proposed 1.2 changelog:
The text was updated successfully, but these errors were encountered: