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

docs - information on releases #2923

Merged
merged 2 commits into from
Feb 5, 2020
Merged

docs - information on releases #2923

merged 2 commits into from
Feb 5, 2020

Conversation

fvanderbiest
Copy link
Member

Documents the new release scheme

@fvanderbiest
Copy link
Member Author

@fvanderbiest
Copy link
Member Author

@landryb
Copy link
Member

landryb commented Feb 4, 2020

just realized that the buildbot will need work to adapt to the new branch naming... since it no longer matches the release being built but its a prefix..

@fvanderbiest fvanderbiest added this to the 20.0 milestone Feb 5, 2020
@landryb
Copy link
Member

landryb commented Feb 5, 2020

buildbot has a new job (https://packages.georchestra.org/bot/builders/buildjob-20.0.x/builds/0, access limited) for this branch (and deploys debian pkg in the 20.0.x branch of the repo), but strangely it still produces pkgs for master..

20.0.x|main|amd64: georchestra-analytics 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-atlas 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-cas 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-console 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-extractorapp 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-geonetwork3 3.8.2.202002050918~134bfd5
20.0.x|main|amd64: georchestra-geoserver 99.master.202002050916~6ede375
20.0.x|main|amd64: georchestra-geowebcache 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-header 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-mapfishapp 99.master.202002050918~6ede375
20.0.x|main|amd64: georchestra-security-proxy 99.master.202002050918~6ede375

i guess that's because we're still on 20.0-SNAPSHOT per 32636ea and not a real version like in fe31be7 ? as long as the -SNAPSHOT prefix is removed when the release is final...

@fvanderbiest
Copy link
Member Author

i guess that's because we're still on 20.0-SNAPSHOT per 32636ea and not a real version like in fe31be7 ? as long as the -SNAPSHOT prefix is removed when the release is final...

Yes, the release has not been published yet. It will be a tag, and the version will be set to 20.0.0.

@landryb
Copy link
Member

landryb commented Feb 5, 2020

https://packages.georchestra.org/bot/wars/20.0.x/ has wars :)

@fvanderbiest fvanderbiest merged commit 77de019 into master Feb 5, 2020
@fvanderbiest fvanderbiest deleted the releases branch February 5, 2020 14:14
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 this pull request may close these issues.

None yet

2 participants