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

Migration to version 9.0 #56

Closed
3 of 7 tasks
pedrobaeza opened this issue Oct 14, 2015 · 5 comments
Closed
3 of 7 tasks

Migration to version 9.0 #56

pedrobaeza opened this issue Oct 14, 2015 · 5 comments
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Milestone

Comments

@pedrobaeza
Copy link
Member

pedrobaeza commented Oct 14, 2015

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

@yvaucher
Copy link
Member

I'm starting to work on migration of base_geoengine for 9.0
@lmignon

@lmignon
Copy link
Sponsor Contributor

lmignon commented Nov 17, 2015

Thank you in advance @yvaucher I've never found the time to finalize the migration to OpenLayer3 started on https://github.com/acsone/geospatial/tree/8.0-ol3-lmi

@lmignon
Copy link
Sponsor Contributor

lmignon commented Nov 18, 2015

@yvaucher I'm a little bit afraid but it seems that it will not be possible to use these addons on an 9.0 enterprise since we depend of 'web' and in enterprise 'web' is not lgpl. I'm even more worried to see that it will no more be possible to use 'AGPL' addons extending the module 'web' in enterprise. In the case of the module 'web', enterprise is not an extend of community but a relicenced fork.

@yvaucher
Copy link
Member

@lmignon For now I'm working on porting it to community version, I succeeded to display the maps in the widget but I'm having hard time trying to show the map on Geoengine view. You might already want to test with an enterprise if the widget are well displayed.

#60

@github-actions
Copy link

github-actions bot commented Feb 5, 2023

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Projects
None yet
Development

No branches or pull requests

3 participants