[Geoserver-devel] GeoServer 2.6.3 release changelog

GeoServer GeoServer Developer
1

Hi,
during the weekend me and Jody are going to cut GeoServer 2.6.3.

One trouble is that we are going to need to go out of our normal way
for it because the Jira migration is still in progress and we have a
notion of which tickets have been closed split among the two
Jira instances. (Harrison, cc’ed, will hopefully explain what’s the holdup
and provide an idea of when the migration is going to get completed?)

Here is a link to the tickets closed for 2.6.3 before we made the old
Jira read only:
http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20fixVersion%20%3D%20%222.6.3%22%20AND%20status%20in%20(Resolved%2C%20Closed)

Apparently in the new one we have none… that seems strange:
https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.6.3

And then there’s the matter of whatever got fixed in the meantine, but could not be closed because the tickets
in the old system are marked read-only, and are not in the new Jira in a suitable state for closing.
Can I ask devs to report about them?

Cheers
Andrea

···

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

2

Harrison Grundy do you have update / ETA for the team?

Time to kick it old school I guess - I have started a CHANGELOG as a temporary measure:

This will let us mark down what issues have been resolved so we can fix the issue tracker.

···

On 17 April 2015 at 01:29, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
during the weekend me and Jody are going to cut GeoServer 2.6.3.

One trouble is that we are going to need to go out of our normal way
for it because the Jira migration is still in progress and we have a
notion of which tickets have been closed split among the two
Jira instances. (Harrison, cc’ed, will hopefully explain what’s the holdup
and provide an idea of when the migration is going to get completed?)

Here is a link to the tickets closed for 2.6.3 before we made the old
Jira read only:
http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20fixVersion%20%3D%20%222.6.3%22%20AND%20status%20in%20(Resolved%2C%20Closed)

Apparently in the new one we have none… that seems strange:
https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.6.3

And then there’s the matter of whatever got fixed in the meantine, but could not be closed because the tickets
in the old system are marked read-only, and are not in the new Jira in a suitable state for closing.
Can I ask devs to report about them?

Cheers
Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

3

I have set up a CHANGELOG.md for each branch populated from CodeHaus.

In addition I have updated the 2.6.x CHANGLEOG.md based on the commits to the 2.6.x branch since March 28th.

···

On 17 April 2015 at 01:29, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
during the weekend me and Jody are going to cut GeoServer 2.6.3.

One trouble is that we are going to need to go out of our normal way
for it because the Jira migration is still in progress and we have a
notion of which tickets have been closed split among the two
Jira instances. (Harrison, cc’ed, will hopefully explain what’s the holdup
and provide an idea of when the migration is going to get completed?)

Here is a link to the tickets closed for 2.6.3 before we made the old
Jira read only:
http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20fixVersion%20%3D%20%222.6.3%22%20AND%20status%20in%20(Resolved%2C%20Closed)

Apparently in the new one we have none… that seems strange:
https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.6.3

And then there’s the matter of whatever got fixed in the meantine, but could not be closed because the tickets
in the old system are marked read-only, and are not in the new Jira in a suitable state for closing.
Can I ask devs to report about them?

Cheers
Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

4

On Fri, Apr 17, 2015 at 9:39 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

I have set up a CHANGELOG.md for each branch populated from CodeHaus.

* https://github.com/geoserver/geoserver/blob/master/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.6.x/src/CHANGELOG.md

I saw it, and disagree with the move. It was not discussed publicly, and I
believe nobody is
going to maintain the contents of those files (I certainly won't, unless
otherwise ordered by the PSC)

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

-------------------------------------------------------

5

On Sat, Apr 18, 2015 at 10:10 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

I have set up a CHANGELOG.md for each branch populated from CodeHaus.

* https://github.com/geoserver/geoserver/blob/master/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.6.x/src/CHANGELOG.md

I saw it, and disagree with the move. It was not discussed publicly, and I
believe nobody is
going to maintain the contents of those files (I certainly won't, unless
otherwise ordered by the PSC)

Should have added rationale, here we go:
* Once we have Jira back, having a changelog file just introduces more
work, Jira generates the changelog for us
* We need to close Jira tickets anyways, that's our communication line with
the reporter (and a chance to get some feedback on whether the fix actually
worked)
* Once we have Jira back (hopefully soon, most certainly before next
release, next month, or we'll need to look for some other migration avenue,
and quickly) those three files will just need to be removed, and two would
have been setup for nothing

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

-------------------------------------------------------

6

When we have Jira back we can remove those files. I was just trying to be helpful.

···

On Sat, Apr 18, 2015 at 10:10 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

I have set up a CHANGELOG.md for each branch populated from CodeHaus.

I saw it, and disagree with the move. It was not discussed publicly, and I believe nobody is
going to maintain the contents of those files (I certainly won’t, unless otherwise ordered by the PSC)

Should have added rationale, here we go:

  • Once we have Jira back, having a changelog file just introduces more work, Jira generates the changelog for us
  • We need to close Jira tickets anyways, that’s our communication line with the reporter (and a chance to get some feedback on whether the fix actually worked)
  • Once we have Jira back (hopefully soon, most certainly before next release, next month, or we’ll need to look for some other migration avenue, and quickly) those three files will just need to be removed, and two would have been setup for nothing

Cheers
Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.