-
Notifications
You must be signed in to change notification settings - Fork 130
Carto v0.16 release #440
Comments
I tried locating all relevant issues and PRs and have added them to the milestone. Not sure if I missed something. |
Sounds good in Kosmtik :) |
Generated XML for osm-carto between 0.15.3 and master is identical except for some rounding errors in colors due to the new transition via HSL. But I might have found a potential bug in the |
TileMill tests pass with latest carto master. Will try Mapbox Studio Classic next. |
I have pushed a commit (206a595) that fixes the problem with color mixing. |
Added changelog in af92b76. |
Excellent work @nebulon42 - I'll test Mapbox Studio Classic this weekend and then ping @tmcw early next week. Assuming all looks good let's plan to release next Wednesday or so. Sound good? |
@springmeyer Any success for Mapbox Studio Classic? |
Mapbox studio classic has failing tests:
|
Sorry, I cannot help investigating because it fails to install for me (sqlite3 makes problems). |
@nebulon42 what is the error you are seeing? |
The error below:
|
@nebulon42 - looks like you might be running as root. This breaks |
@springmeyer I'm only running npm as root if I'm prompted to do so. It might be related to that specific sqlite3 version, because the latest version installs fine. Unfortunately, I don't have much time to investigate this in detail. |
Installation succeeded when I upgraded from |
After some problems with
|
@springmeyer How should we proceed from here? |
@nebulon42 thanks for pinging. I think those earlier mapbox studio classic errors are unrelated. I'm not seeing them and travis is green for studio classic. I've spent some time this morning getting to the bottom of the problem: Mapbox Studio Classic uses Carto without the styling for generating MML suitable for rendering vector tiles. So what Studio Classic needed was Carto to only validate the |
Assuming that change looks good to you and travis passes green, I think we are ready to tag. |
|
Great! |
Ticket to track overall coordination on releasing v0.16.0.
(Below I've added tasks and handles. Please feel free to edit in place, adding yourself on a task or removing if you don't have bandwidth.)
Before cutting a release I'm seeing we need to:
npm publish
The text was updated successfully, but these errors were encountered: