With a lot of help from Torben GSIP-111 is ready:
- https://github.com/geoserver/geoserver/wiki/GSIP-111
- https://github.com/geoserver/geoserver/pull/551
Sadly it is late to the party, is there any way to sneak this in?
···
–
Jody Garnett
+0 for sneaking it in. It would be a shame to leave this out of 2.8, despite the freeze.
*looks the other way*
On 02/09/15 12:01, Jody Garnett wrote:
With a lot of help from Torben GSIP-111 is ready:
- https://github.com/geoserver/geoserver/wiki/GSIP-111
- https://github.com/geoserver/geoserver/pull/551Sadly it is late to the party, is there any way to sneak this in?
--
Jody Garnett
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On Wed, Sep 2, 2015 at 2:01 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
With a lot of help from Torben GSIP-111 is ready:
- https://github.com/geoserver/geoserver/wiki/GSIP-111
- https://github.com/geoserver/geoserver/pull/551Sadly it is late to the party, is there any way to sneak this in?
It is sad, or do you have a strict contractual requirement?
If it's just sad, I'd say commit to master, wait a month, and then backport.
If it's serious instead, let's find a way to make it work, like having two
core
devs make a line by line code review of it.
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
-------------------------------------------------------
It is just sad, mostly for the API cleanup. I can wait a month.
···
On Wed, Sep 2, 2015 at 2:01 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
With a lot of help from Torben GSIP-111 is ready:
- https://github.com/geoserver/geoserver/wiki/GSIP-111
- https://github.com/geoserver/geoserver/pull/551
Sadly it is late to the party, is there any way to sneak this in?
It is sad, or do you have a strict contractual requirement?
If it’s just sad, I’d say commit to master, wait a month, and then backport.
If it’s serious instead, let’s find a way to make it work, like having two core
devs make a line by line code review of it.
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
Aha! There will be no need to backport as we do not branch until the first RC. 
The 2.8.x branch has not yet been created.
On 02/09/15 18:15, Andrea Aime wrote:
If it's just sad, I'd say commit to master, wait a month, and then backport.
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On Wed, Sep 2, 2015 at 9:59 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
Aha! There will be no need to backport as we do not branch until the
first RC.The 2.8.x branch has not yet been created.
Right, I wanted to point that out, by now, we should have been created the
branch instead,
the plan was to delay the beta and have zero blocked branches all the time,
no?
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
-------------------------------------------------------
Ciao Jody,
I am +0 about the proposal but I am -0 about pushing this in now
I agree with Andrea, If we are holding up payed work I would move on right away.
That said, does this work include the possibility to use a pre-cooked
legend for layers?
Regards,
Simone Giannecchini
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
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.
On Wed, Sep 2, 2015 at 2:01 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
With a lot of help from Torben GSIP-111 is ready:
- https://github.com/geoserver/geoserver/wiki/GSIP-111
- https://github.com/geoserver/geoserver/pull/551Sadly it is late to the party, is there any way to sneak this in?
--
Jody Garnett------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
I thought we were in a code freeze (see earlier email announcing the 2.8-beta release) from now until the RC1.
···
On 2 September 2015 at 01:20, Andrea Aime <andrea.aime@anonymised.com> wrote:
–
Jody Garnett
On Wed, Sep 2, 2015 at 9:59 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
Aha! There will be no need to backport as we do not branch until the
first RC.The 2.8.x branch has not yet been created.
Right, I wanted to point that out, by now, we should have been created the branch instead,
the plan was to delay the beta and have zero blocked branches all the time, no?
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
Ciao Jody,
···
I am +0 about the proposal but I am -0 about pushing this in now
I agree with Andrea, If we are holding up payed work I would move on right away.
It is not holding up paid work, my motivation for asking is due to ease of maintenacne fixing LegendGraphicRequest in the future. Given the refactor it would be much easier to fix and back port changes over the life of 2.8.x if the API change is made now.
That said, does this work include the possibility to use a pre-cooked legend for layers?
Yes, that is what the pull request provides. So from a product story it would be a nice user visible feature for GeoServer 2.8.
Jody
It was also my understanding that we are in a feature freeze and that the new branch is not created until RC1:
http://docs.geoserver.org/latest/en/developer/release-guide/index.html#if-you-are-cutting-the-first-rc-of-a-series-create-the-stable-branch
On 03/09/15 06:54, Jody Garnett wrote:
I thought we were in a code freeze (see earlier email announcing the
2.8-beta release) from now until the RC1.
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On 02/09/15 20:20, Andrea Aime wrote:
Right, I wanted to point that out, by now, we should have been created the
branch instead,
the plan was to delay the beta and have zero blocked branches all the time,
no?
I was not aware that this was the plan. My understanding of a beta is that we should expect many bugs. An RC should be releasable unchanged and so gets a new stable branch.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On Wed, Sep 2, 2015 at 9:02 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
On 02/09/15 20:20, Andrea Aime wrote:
Right, I wanted to point that out, by now, we should have been created the
branch instead,
the plan was to delay the beta and have zero blocked branches all the
time,
no?I was not aware that this was the plan. My understanding of a beta is that
we should expect many bugs.
Ha ha ha ha ha... sorry, could not resist... I actually took the time to do
bug fixing in the last
few betas... I can assure you, the important bug reports came with 2.x.0,
2.x.1 and 2.x.2, our user base did not
even bother to touch the beta (besides some bright exceptions).
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
-------------------------------------------------------
Duly noted, the best thing we can do is get the RC1 and release out as soon as possible.
···
On 2 September 2015 at 13:01, Andrea Aime <andrea.aime@anonymised.com> wrote:
–
Jody Garnett
On Wed, Sep 2, 2015 at 9:02 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
On 02/09/15 20:20, Andrea Aime wrote:
Right, I wanted to point that out, by now, we should have been created the
branch instead,
the plan was to delay the beta and have zero blocked branches all the time,
no?I was not aware that this was the plan. My understanding of a beta is that we should expect many bugs.
Ha ha ha ha ha… sorry, could not resist… I actually took the time to do bug fixing in the last
few betas… I can assure you, the important bug reports came with 2.x.0, 2.x.1 and 2.x.2, our user base did not
even bother to touch the beta (besides some bright exceptions).
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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.
On 03/09/15 08:01, Andrea Aime wrote:
Ha ha ha ha ha... sorry, could not resist... I actually took the time to do
bug fixing in the last
few betas... I can assure you, the important bug reports came with 2.x.0,
2.x.1 and 2.x.2, our user base did not
even bother to touch the beta (besides some bright exceptions).
Indeed. I have seen previous betas with no reports, except from the most diligent users, who we then nominate for the steering committee. It is a trap!
Users may prefer to test releases that they are considering for production.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
>Indeed. I have seen previous betas with no reports, except from the most diligent users, who we then nominate for the steering committee. >It is a trap! Users may prefer to test releases that they are considering for production. Kind regards,
I'm a little curious here. If I was taking more beta's, or for that matter more production releases! onto my test environment, it would make IT more confident about updating our production environment (which they are extremely conservative about). The hassle is synchronising with the production version. Do you just periodically copy the geoserver data area or do people have more sophisticated ways of synchronizing between test and production environments?
--
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
Depends on the installation …
On some installation I make sure the “data” is out of the data directory (external references only - since data is often under different backup policy than configuration). Create a copy of the data directory, run the new geoserver against the copy.
If the machine is scripted, configured via rest api so machines can be provisioned consistently, I update the script with the new war and let it try setting up a new VM. Not sure if that counts as sophisticated or not.
···
On 2 September 2015 at 14:08, Phil Scadden <p.scadden@anonymised.com> wrote:
Indeed. I have seen previous betas with no reports, except from the
most diligent users, who we then nominate for the steering committee.
It is a trap!
considering for production. Kind regards,
I’m a little curious here. If I was taking more beta’s, or for that
matter more production releases! onto my test environment, it would make
IT more confident about updating our production environment (which they
are extremely conservative about). The hassle is synchronising with the
production version. Do you just periodically copy the geoserver data
area or do people have more sophisticated ways of synchronizing between
test and production environments?–
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St,
Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Jody Garnett
Jody,
how do you handle data directories with datastores configured for read-write access to, for example, databases? These must require special treatment to avoid the test environment writing into the production database.
Kind regards,
Ben.
On 03/09/15 11:14, Jody Garnett wrote:
Depends on the installation ...
On some installation I make sure the "data" is out of the data directory
(external references only - since data is often under different backup
policy than configuration). Create a copy of the data directory, run the
new geoserver against the copy.If the machine is scripted, configured via rest api so machines can be
provisioned consistently, I update the script with the new war and let it
try setting up a new VM. Not sure if that counts as sophisticated or not.
--
Jody--
Jody GarnettOn 2 September 2015 at 14:08, Phil Scadden <p.scadden@anonymised.com> wrote:
>Indeed. I have seen previous betas with no reports, except from the
most diligent users, who we then nominate for the steering committee.
>It is a trap!
considering for production. Kind regards,
I'm a little curious here. If I was taking more beta's, or for that
matter more production releases! onto my test environment, it would make
IT more confident about updating our production environment (which they
are extremely conservative about). The hassle is synchronising with the
production version. Do you just periodically copy the geoserver data
area or do people have more sophisticated ways of synchronizing between
test and production environments?--
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St,
Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477
5232Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Guess the point is I am a developer and do not get the privilege of running a GeoServer myself
But two answers to your question:
a) That is what JNDI is for (allowing configuration migration from dev to test to production)
b) 90% of the time I turn off WFS-T, so I am not as concerned about performing a test against a live data base
It would be different if my evaluation was going to focus on performance, or WFS-T functionality.
All we are asking for out of a beta is any confidence that the release will work … so anything feedback for the developers would be great.
I also note the cycle, if users put off upgrading while they wait for others to go first, we will need to put off having betas and release candidates.
···
On 2 September 2015 at 16:22, Ben Caradoc-Davies <ben@anonymised.com> wrote:
Jody,
how do you handle data directories with datastores configured for read-write access to, for example, databases? These must require special treatment to avoid the test environment writing into the production database.
Kind regards,
Ben.On 03/09/15 11:14, Jody Garnett wrote:
Depends on the installation …
On some installation I make sure the “data” is out of the data directory
(external references only - since data is often under different backup
policy than configuration). Create a copy of the data directory, run the
new geoserver against the copy.If the machine is scripted, configured via rest api so machines can be
provisioned consistently, I update the script with the new war and let it
try setting up a new VM. Not sure if that counts as sophisticated or not.Jody
–
Jody GarnettOn 2 September 2015 at 14:08, Phil Scadden <p.scadden@anonymised.com> wrote:
Indeed. I have seen previous betas with no reports, except from the
most diligent users, who we then nominate for the steering committee.
It is a trap!
considering for production. Kind regards,
I’m a little curious here. If I was taking more beta’s, or for that
matter more production releases! onto my test environment, it would make
IT more confident about updating our production environment (which they
are extremely conservative about). The hassle is synchronising with the
production version. Do you just periodically copy the geoserver data
area or do people have more sophisticated ways of synchronizing between
test and production environments?–
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St,
Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477
5232Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
–
Jody Garnett
Thanks, Jody. I think "use JNDI" is good advice to easy dev/test/production migration.
On 03/09/15 11:29, Jody Garnett wrote:
a) That is what JNDI is for (allowing configuration migration from dev to
test to production)
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Yes, we use JNDI for dev/test/prod migration on apps and for geoserver. However is the /data area that is a pain to sync. Dev team has no login on the production servers. This makes just copying from production area a pain. (but we do have data outside the deployment)
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.