Artifacts are available here. Please give them a quick smoke test if you have a chance.
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
···
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
Hi Kevin,
it looks like a pull request fixing a bug recently introduced in GetFeatureInfo
did not get merged, so we have a non fully working GetFeatureInfo functionality:
https://github.com/geoserver/geoserver/pull/1075
I’ve now merged that pull request.
Also, Jukka observation about the Oracle plugin makes me think the release
is cut off an outdated revision, the Oracle plugin in nightly builds does not
ship with the Oracle driver anymore, but the release one does.
The change to remove that driver was merged by Jody on Monday, so
the release has been build off something older than that.
Indeed, the MANIFEST from one random jar shows:
Build-Timestamp: 19-May-2015 23:30
Implementation-Version: 2.7.1
Git-Revision: 03a0bc499a7c74527d480d30643dd5fd249edcce
This revision is from May 16th:
https://github.com/geoserver/geoserver/commits/2.7.x
I can see you have followed procedure, the commit id from the cite tests run May 19th
is indeed that one:
version = 2.7-SNAPSHOT
git revision = 03a0bc499a7c74527d480d30643dd5fd249edcce
git branch = 03a0bc499a7c74527d480d30643dd5fd249edcce
build date = 18-May-2015 10:40
geotools version = 13-SNAPSHOT
geotools revision = 5fd9fd323eb2b091e07f3c2385326be4889dc913
The GeoTools revision also wants me to pull hair, as it misses the fixes we
made for mosaic harvesting issues that several people complained about on the
user mailing list, also merged the 18th:
https://github.com/geotools/geotools/commits/13.x
Now… how can a cite test from the 19th miss commits made the 18th, I’m not
really sure… the nightly build actually never failed recently:
http://ares.boundlessgeo.com/jenkins/view/geoserver/job/geoserver-2.7.x-nightly/
Also looking at the 20th cite test run, it has newer revision, so it’s not like we’re
stuck with an old jar
Long story short, it seems the release is busted at the GeoTools and GeoServer level…
I’m kicking the build server manually to get a new round of CITE test that include also the GetFeatureInfo
fixes.
About the release notes, I believe there is something wrong with the release notes,
because there are 19 tickets marked as resolved or closed for 2.7.1,
see here:
https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.7.1
And here is the list of GeoTools ones, for 13.1, 20 tickets:
https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOT%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%2013.1%20ORDER%20BY%20summary%20ASC
Cheers
Andrea
···
On Wed, May 20, 2015 at 2:00 AM, Kevin Smith <ksmith@anonymised.com> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
==
Meet us at the INSPIRE Conference in Lisbon 25-29 May 2015! Visit http://goo.gl/WHKDXT for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
I did not notice anything strange when I ran the script, and the GeoTools one (which is pretty much the same script) generated release notes just fine.
Have you fixed this since? I can see the 2.7.1 Release notes just fine here: https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10414
Torben
···
On Tue, May 19, 2015 at 5:29 PM, Kevin Smith <ksmith@anonymised.com> wrote:
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
Strange, yesterday I couldn’t find any reference to version 2.7.1 in JIRA whatsoever, just 2.7.0 and 2.7.2. Do we need to do a GeoTools 13.1.1 first or should I restart the GeoServer release.
···
On 20 May 2015 at 08:48, Torben Barsballe <tbarsballe@anonymised.com> wrote:
I did not notice anything strange when I ran the script, and the GeoTools one (which is pretty much the same script) generated release notes just fine.
Have you fixed this since? I can see the 2.7.1 Release notes just fine here: https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10414
Torben
–
On Tue, May 19, 2015 at 5:29 PM, Kevin Smith <ksmith@anonymised.com839…> wrote:
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
On Wed, May 20, 2015 at 8:13 PM, Kevin Smith <ksmith@anonymised.com>
wrote:
Strange, yesterday I couldn't find any reference to version 2.7.1 in JIRA
whatsoever, just 2.7.0 and 2.7.2. Do we need to do a GeoTools 13.1.1 first
or should I restart the GeoServer release.
We'd need gt 13.1 redone too if possible, in order to get the mosaic
harvesting fixes.
What cannot be avoided is only the GeoServer one, as we cannot release with
a broken GetFeatureInfo
Cheers
Andrea
--
Meet us at the INSPIRE Conference in Lisbon 25-29 May 2015! Visit
http://goo.gl/WHKDXT for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
Kevin - By default, the OSGeo JIRA dashboard only shows unreleased versions, and it looks like all the old versions are showing as unreleased due to the migration. Just check “released” for the status up above: https://osgeo-org.atlassian.net/projects/GEOS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released
I’ll kick of a new 13.1 release - from the latest Cite tests that Andrea started, the new build info is:
version = 2.7-SNAPSHOT
git revision = 38d7d11f9064b1d861365bbaed2474dabe410677
git branch = 38d7d11f9064b1d861365bbaed2474dabe410677
build date = 19-May-2015 11:44
geotools version = 13-SNAPSHOT
geotools revision = 0a6a182f4e86797f4430fc2a901a407b0ade82b6
geowebcache version = 1.7-SNAPSHOT
geowebcache revision = bee486b3ba683f8752b4ad578cd61cbb62422832/bee48
Does anyone know if we will have any problems with overwriting the existing 13.1 release files?
Torben
···
On Wed, May 20, 2015 at 11:13 AM, Kevin Smith <ksmith@anonymised.com> wrote:
Strange, yesterday I couldn’t find any reference to version 2.7.1 in JIRA whatsoever, just 2.7.0 and 2.7.2. Do we need to do a GeoTools 13.1.1 first or should I restart the GeoServer release.
On 20 May 2015 at 08:48, Torben Barsballe <tbarsballe@anonymised.com> wrote:
I did not notice anything strange when I ran the script, and the GeoTools one (which is pretty much the same script) generated release notes just fine.
Have you fixed this since? I can see the 2.7.1 Release notes just fine here: https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10414
Torben
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
On Tue, May 19, 2015 at 5:29 PM, Kevin Smith <ksmith@anonymised.com> wrote:
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
I’ve started a new batch of CITE test builds that actually include Mauro’s GetFeatureInfo fix. The GeoTools revision is the same for the new build, so at least the GeoTools update should still be fine. It looks like both GeoWebCache and GeoServer will need rebuilding though:
···
On Wed, May 20, 2015 at 1:35 PM, Andrea Aime <andrea.aime@…1268…> wrote:
Eeek oh no, I was interrupted and failed to finish the builds, if you look at that revision you will see it does not include Mauro’s GetFeatureInfo fix… sorry guys…
Bye
AndreaIl 20/mag/2015 20:31, “Torben Barsballe” <tbarsballe@anonymised.com> ha scritto:
Kevin - By default, the OSGeo JIRA dashboard only shows unreleased versions, and it looks like all the old versions are showing as unreleased due to the migration. Just check “released” for the status up above: https://osgeo-org.atlassian.net/projects/GEOS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released
I’ll kick of a new 13.1 release - from the latest Cite tests that Andrea started, the new build info is:
version = 2.7-SNAPSHOT git revision = 38d7d11f9064b1d861365bbaed2474dabe410677 git branch = 38d7d11f9064b1d861365bbaed2474dabe410677 build date = 19-May-2015 11:44 geotools version = 13-SNAPSHOT geotools revision = 0a6a182f4e86797f4430fc2a901a407b0ade82b6 geowebcache version = 1.7-SNAPSHOT geowebcache revision = bee486b3ba683f8752b4ad578cd61cbb62422832/bee48Does anyone know if we will have any problems with overwriting the existing 13.1 release files?
Torben
On Wed, May 20, 2015 at 11:13 AM, Kevin Smith <ksmith@anonymised.com> wrote:
Strange, yesterday I couldn’t find any reference to version 2.7.1 in JIRA whatsoever, just 2.7.0 and 2.7.2. Do we need to do a GeoTools 13.1.1 first or should I restart the GeoServer release.
On 20 May 2015 at 08:48, Torben Barsballe <tbarsballe@anonymised.com> wrote:
I did not notice anything strange when I ran the script, and the GeoTools one (which is pretty much the same script) generated release notes just fine.
Have you fixed this since? I can see the 2.7.1 Release notes just fine here: https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10414
Torben
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
On Tue, May 19, 2015 at 5:29 PM, Kevin Smith <ksmith@anonymised.com> wrote:
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com3839…> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
The latest CITE tests builds (see above) passed, and GeoTools 13.1 has been re-released to the newest passing revision. You can go ahead with GeoWebCache/GeoServer Kevin.
Torben
···
On Wed, May 20, 2015 at 1:52 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:
I’ve started a new batch of CITE test builds that actually include Mauro’s GetFeatureInfo fix. The GeoTools revision is the same for the new build, so at least the GeoTools update should still be fine. It looks like both GeoWebCache and GeoServer will need rebuilding though:
``` git revision = 381d86c5a8678a07eeee34f4c509e75dd03a4421 git branch = 381d86c5a8678a07eeee34f4c509e75dd03a4421 build date = 20-May-2015 10:40 geotools version = 13-SNAPSHOT geotools revision = 0a6a182f4e86797f4430fc2a901a407b0ade82b6 geowebcache version = 1.7-SNAPSHOT geowebcache revision = a52ef84de9ad0ed09b22575afb95c2adfaf7b06f/a52ef ```Kevin - once the CITE tests are confirmed to pass, I will finish off the GeoTools release, and then you can go ahead with GeoServer I guess?
Torben
On Wed, May 20, 2015 at 1:35 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Eeek oh no, I was interrupted and failed to finish the builds, if you look at that revision you will see it does not include Mauro’s GetFeatureInfo fix… sorry guys…
Bye
AndreaIl 20/mag/2015 20:31, “Torben Barsballe” <tbarsballe@anonymised.com> ha scritto:
Kevin - By default, the OSGeo JIRA dashboard only shows unreleased versions, and it looks like all the old versions are showing as unreleased due to the migration. Just check “released” for the status up above: https://osgeo-org.atlassian.net/projects/GEOS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released
I’ll kick of a new 13.1 release - from the latest Cite tests that Andrea started, the new build info is:
version = 2.7-SNAPSHOT git revision = 38d7d11f9064b1d861365bbaed2474dabe410677 git branch = 38d7d11f9064b1d861365bbaed2474dabe410677 build date = 19-May-2015 11:44 geotools version = 13-SNAPSHOT geotools revision = 0a6a182f4e86797f4430fc2a901a407b0ade82b6 geowebcache version = 1.7-SNAPSHOT geowebcache revision = bee486b3ba683f8752b4ad578cd61cbb62422832/bee48Does anyone know if we will have any problems with overwriting the existing 13.1 release files?
Torben
On Wed, May 20, 2015 at 11:13 AM, Kevin Smith <ksmith@anonymised.com> wrote:
Strange, yesterday I couldn’t find any reference to version 2.7.1 in JIRA whatsoever, just 2.7.0 and 2.7.2. Do we need to do a GeoTools 13.1.1 first or should I restart the GeoServer release.
On 20 May 2015 at 08:48, Torben Barsballe <tbarsballe@anonymised.com> wrote:
I did not notice anything strange when I ran the script, and the GeoTools one (which is pretty much the same script) generated release notes just fine.
Have you fixed this since? I can see the 2.7.1 Release notes just fine here: https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10414
Torben
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
On Tue, May 19, 2015 at 5:29 PM, Kevin Smith <ksmith@anonymised.com> wrote:
One issue, it appears no tickets were associated with the 2.7.1 release in the new JIRA so it appears no release notes were generated.
Torben, you ran the JIRA release note script manually, did you notice anything odd?
At the moment I can’t even fix the tickets I can see in the git log since my account with the new JIRA (ksmith) seems to only be able to create new tickets and comments.
I’ll finish the release tomorrow.
On 19 May 2015 at 17:00, Kevin Smith <ksmith@anonymised.com3839…> wrote:
Artifacts are available here. Please give them a quick smoke test if you have a chance.
http://ares.boundlessgeo.com/geoserver/release/2.7.1/
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459
–
Kevin Smith
Software Engineer | Boundless
+1-778-785-7459