Skip to content

Commit 0dae573

Browse files
committed
Prepare release version 1.0.0 (!)
1 parent c228ac3 commit 0dae573

File tree

4 files changed

+9
-6
lines changed

4 files changed

+9
-6
lines changed

README.md

+2
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ The OpenTripPlanner project was launched by Portland, Oregon's transport agency
1717

1818
In summer of 2013, the OpenTripPlanner project was accepted for membership in the Software Freedom Conservancy (SFC). SFC handles the legal and financial details common to many open source projects, providing a formal framework for OTP and allowing contributors to concentrate on the code. For more information, see the SFC website at http://sfconservancy.org/.
1919

20+
After seven years of hard work and almost 10,000 commits from over 100 contributors around the world, version 1.0 was released on 9 September 2016.
21+
2022

2123
## Mailing Lists
2224

docs/History.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ In November of 2014, Arlington, Virginia launched a new [commute planning site](
1414

1515
As of 2015, OTP now powers the New York State department of transportation's [transit trip planner](http://511ny.org/tripplanner/default.aspx). It provides itineraries for public transit systems throughout the state in a single unified OTP instance.
1616

17+
The Helsinki Regional Transport Authority (HSL) [trip planner](https://digitransit.fi/en/) based on OpenTripPlanner is in public beta as of spring 2016.
1718

18-
19-
19+
After seven years and almost 10,000 commits from over 100 contributors around the world, version 1.0 was released on 9 September 2016.
20+

docs/index.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ If you want to get started right away running your own OTP instance, the best pl
99

1010
**Latest Project Updates**
1111

12-
* After seven years of hard work, a **1.0 release is planned for August of 2016**! OTP is in feature freeze, with all work concentrating on bug fixes and API cleanup.
12+
* After seven years of hard work and almost 10,000 commits from over 100 contributors around the world, **version 1.0 was released on 9 September 2016**!
1313

1414
* The Helsinki Regional Transport Authority (HSL) [trip planner](https://digitransit.fi/en/) based on OpenTripPlanner is in public beta as of spring 2016. Source code for their new UI is [available on Github](https://github.com/HSLdevcom/digitransit-ui).
1515

@@ -31,7 +31,7 @@ If you want to get started right away running your own OTP instance, the best pl
3131

3232
[![Build Status](https://travis-ci.org/opentripplanner/OpenTripPlanner.svg?branch=master)](https://travis-ci.org/opentripplanner/OpenTripPlanner)
3333

34-
After seven years of hard work, a **1.0 release of OTP is planned for August of 2016**! OTP is in feature freeze, with all work concentrating on bug fixes and API cleanup. See the [changelog](Changelog) and the [version notes](Version-Notes) to decide which branch or tag you want to work with. The software currently:
34+
**Version 1.0 was released on 9 September 2016**. OTP now:
3535

3636
* Plans multi-modal walking, wheelchair, bicycle and transit trips
3737
* Takes travel time, road type, safety, and elevation into account, and allows users to customize the weighting of these three factors
@@ -52,7 +52,7 @@ At the core of OpenTripPlanner is a library of Java code that finds efficient pa
5252

5353
The **OTP Routing API** is a [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) web service that responds to journey planning requests with itineraries in a JSON or XML representation. You can combine this API with OTP's standard Javascript front end to provide users with trip planning functionality in a familiar map interface, or write your own applications that talk directly to the API.
5454

55-
The **OTP Transit Index API** is another [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) web service that provides information derived from the input GTFS feed(s). Examples include routes serving a particular stop, upcoming vehicles at a particular stop, upcoming stops on a given trip, etc.
55+
The **OTP Transit Index API** is another [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) web service that provides information derived from the input GTFS feed(s). Examples include routes serving a particular stop, upcoming vehicles at a particular stop, upcoming stops on a given trip, etc. More complex transit data requests can be formulated using a GraphQL API.
5656

5757
The term "OTP Analyst" refers to parts of OTP that apply the routing engine to transportation network analysis rather than end-to-end trip planning. OTP Analyst includes:
5858

pom.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
<url>http://opentripplanner.org/</url>
77
<groupId>org.opentripplanner</groupId>
88
<artifactId>otp</artifactId>
9-
<version>1.0.0-SNAPSHOT</version>
9+
<version>1.0.0</version>
1010
<packaging>jar</packaging>
1111

1212
<scm>

0 commit comments

Comments
 (0)