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

No longer need patch for geofield schema #3

Closed
finnlewis opened this issue Sep 4, 2020 · 11 comments · Fixed by #8
Closed

No longer need patch for geofield schema #3

finnlewis opened this issue Sep 4, 2020 · 11 comments · Fixed by #8

Comments

@finnlewis
Copy link
Member

It looks like the patch was committed :
https://git.drupalcode.org/project/geofield_map/-/commit/6642265c136329ce04ebda7bccd1b208919f5e4e

@Adnan-cds
Copy link
Contributor

Thanks Finn. Now that this issue is resolved, would you mind doing the honour of adding a release tag for localgov_geo such as 1.0.1-alpha1? :)

@finnlewis
Copy link
Member Author

I think it should bt 1.0.0-alpha2 up until we have the 1.0.0 release.

From experience I think that is more the Drupal way.

Thoughts? @ekes @stephen-cox @andybroomfield

@finnlewis
Copy link
Member Author

Sorry, cross posting from localgovdrupal/localgov#139

But here's an example of how I expect the increments to flow :

1.0.1 - 23 July 2020
1.0.0 - 6 July 2020
1.0.0-alpha6 - 25 June 2020
1.0.0-alpha5 - 23 June 2020
1.0.0-alpha4 - 23 June 2020
1.0.0-alpha3 - 23 June 2020
1.0.0-alpha2 - 22 June 2020
1.0.0-alpha1 - 21 June 2020
1.0.x-dev - 21 June 2020

@stephen-cox
Copy link
Member

The Drupal way would be to release 1.0.0-alpha2 next. I have to admit that I find this a little strange, but I think we decided to do things this way.

As mentioned here localgovdrupal/localgov#139 (comment), we need a list of conditions that might cause a new release. In my view, a minor fix isn't enough to trigger a new release on it's own, but we do need to decide on what conditions need to be met to trigger a new release.

@finnlewis
Copy link
Member Author

I think a bug fix perhaps should trigger a release, as people might need that fix downstream. But is a bug fix anything that causes tests to fail?

In our immediate case, Lambeth is launching next Tuesday, so we need to be able to pull in as many of the bug fixes that occur this week as possible.

@finnlewis
Copy link
Member Author

OK - tagged this with 1.0.0-alpha2

https://github.com/localgovdrupal/localgov_geo/releases/tag/1.0.0-alpha2

@stephen-cox
Copy link
Member

I assume this is only causing an warning with Composer so it's not breaking the site or causing builds to fail? In which case it's very minor and in my view not worth creating a new release for.

@Adnan-cds
Copy link
Contributor

I assume this is only causing an warning with Composer so it's not breaking the site or causing builds to fail?

I really don't know Steve. Gosia's tests are failing with Schema errors from the localgov_geo module. This is very odd. Now that Finn has made a new release, I will trigger the failing test again and see if this makes any difference.

@Adnan-cds
Copy link
Contributor

Gosia's test has failed again. But looks like this time the missing Schemas are from the geofield module and I can't find a patch. It may be a coincidence that these tests failed on the same day the change for this issue was merged.

FAO @finnlewis @stephen-cox @gosia-mlynarczyk

@ekes
Copy link
Member

ekes commented Aug 18, 2021

Is this still an issue?

@Adnan-cds
Copy link
Contributor

I think this one can be closed.

@ekes ekes closed this as completed Sep 8, 2021
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

Successfully merging a pull request may close this issue.

4 participants