Skip to content

Commit

Permalink
REL: set version to 1.5.0rc1
Browse files Browse the repository at this point in the history
  • Loading branch information
@tylerjereddy
tylerjereddy committed May 30, 2020
1 parent fc166b5 commit ff72ef8
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion pavement.py
View file
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@

# Start/end of the log (from git)
LOG_START = 'v1.4.0'
LOG_END = 'master'
LOG_END = 'maintenance/1.5.x'


#-------------------------------------------------------
Expand Down
4 changes: 2 additions & 2 deletions setup.py
View file
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,8 @@
MAJOR = 1
MINOR = 5
MICRO = 0
ISRELEASED = False
VERSION = '%d.%d.%d' % (MAJOR, MINOR, MICRO)
ISRELEASED = True
VERSION = '%d.%d.%drc1' % (MAJOR, MINOR, MICRO)


# Return the git revision as a string
Expand Down

2 comments on commit ff72ef8

@h-vetinari
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that something went wrong with the encoding while copying the release notes to the tag under releases - there's some mojibake, particularly under the contributor names. Also, as a tiny nit that doesn't really merit a PR, I'd add the following before the final 1.5.0:

 This release requires Python 3.6+ and NumPy 1.14.5 or greater.

-For running on PyPy, PyPy3 6.0+ and NumPy 1.15.0 are required.
+For running on PyPy, PyPy3 6.0+ and NumPy 1.15.0 or greater are required.

 Highlights of this release
 --------------------------

@tylerjereddy
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

particularly under the contributor names

I brought this up on the mailing list. I copy-pasted the notes through gvim on a Windows machine into a browser, so some part of that process probably has some issues.

That said, the original release notes file should be formatted "ok"

Please sign in to comment.