Skip to content
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

Release 2.40.0 #2174

Closed
gravitystorm opened this issue Jun 17, 2016 · 8 comments
Closed

Release 2.40.0 #2174

gravitystorm opened this issue Jun 17, 2016 · 8 comments
Assignees

Comments

@gravitystorm
Copy link
Owner

A month ago I ran out of time to make a release before I left on a holiday. I've realised that I'm a single point of failure with releases, and despite telling all the other maintainers that the are welcome to take over, I think everyone is still waiting on me to do them!

So I'm going to make a new policy, which is that I want to see every maintainer making a release at least once a year, just to make sure that everyone is comfortable doing so if I'm not around. I'm happy to continue as the main release manager, and I'm also happy to hand over to others. But I think it's worth making sure all the maintainers are happy with the release process.

I've assigned this issue to @math1985 to make the next release, which can be done any time from now.

@matthijsmelissen
Copy link
Collaborator

Two reasons I haven't done any release yet:

  • @pnorman suggested not to do a release until we know better what causes the landuse polygons problems
  • We hardly merged any PRs since last release (until @matkoniecz started his gsoc project), and the changes that were merged don't affect rendering output

I will pick up the next release soon.

@kocio-pl
Copy link
Collaborator

At least bookshop and library will look different now, so new release would make the difference.

@pnorman
Copy link
Collaborator

pnorman commented Jun 17, 2016

I had written half an email about doing a release about 6 weeks ago, but realized there was nothing yet release-worthy, and I hadn't tested for #2101 on a production renderd setup.

#2101 still concerns me

@matkoniecz
Copy link
Contributor

I also considered pushing release, but I decided to wait until #2101 is resolved.

@matthijsmelissen
Copy link
Collaborator

I have reverted #2101 for now as it is blocking the release.

@pnorman
Copy link
Collaborator

pnorman commented Jun 21, 2016

With that reverted, are you ready to tag a release?

@matthijsmelissen
Copy link
Collaborator

Done, see also openstreetmap/chef#70.

@gravitystorm
Copy link
Owner Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants