Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#3657 closed defect (fixed)

Fix winnie badge on the wiki table for 2.3 branch

Reported by: strk Owned by: robe
Priority: medium Milestone: PostGIS 2.3.1
Component: QA/buildbots Version: 2.3.x
Keywords: Cc:

Description

See the "unknown" cell in winnie/2.3 branch https://trac.osgeo.org/postgis/

Change History (8)

comment:1 by strk, 8 years ago

Should also be fixed in the README.md of the 2.3 branch, as the current one points to trunk

comment:2 by strk, 8 years ago

In 15194:

Fix buildbot badges to point to 2.3 branch

See #3657

comment:3 by robe, 8 years ago

We should probably add in the HOW_TO_RELEASE to bump up the badges or did I miss that in my gloss over?

comment:4 by strk, 8 years ago

it's not in HOWTO_RELEASE. This is specific to minor release, reviewing the file there's no special instructions for that kind of release (and there's also an hard-coded assumption of releases coming out of the "trunk" branch which is nowadays hardly the case.

comment:5 by robe, 8 years ago

Yah the HOWTO_RELEASE needs some work. It kinda assumes branch micro releases in some places and not others. I was tempted to put in instructions for doing a minor but didn't want to muddle it too much.

Perhaps we need to break it into two

doing

Minor vs. Micro.

The 2.3 I had to improvise a bit from what the HOW to said. Like you need to spin off a new branch as well as tag, where as micro you just tag.

and all these debbie things on jenkins have to be flipped, not covered in HOW_TO_RELEASE. Like the doxygen thing for example you noticed.

comment:6 by strk, 8 years ago

Having done the most recent releases you're in the best position to rewrite that file. Go Regina Go !

comment:7 by robe, 8 years ago

Resolution: fixed
Status: newclosed

the badge has been long fixed. This should be closed. We should have a separate ticket for cleaning up the HOW_TO_RELEASE.

comment:9 by robe, 8 years ago

In 15280:

Relationship functions not using an index in some cases
Set cost back to 1 for functions that return a geometry
A higher cost has the side-effect of making the planner
think when used in conjunction with relate constructs like ST_Intersects
it's cheaper to compute the geometry once rather
than compute twice and break into an index and non-index call.
References #3657 for PostGIS 2.3

Note: See TracTickets for help on using tickets.