Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[bradh]

Just that Andrea suggested the next version of GeoServer be 22.0 (see Subject 
line) with some pseudo-math support argument. I'm not particularly worried 
about what we call it (GS 20.0 works for me), but consistency would be helpful.

-Original Message-
From: Ben Caradoc-Davies  
Sent: Friday, 13 July 2018 9:35 AM
To: br...@frogmouth.net; 'Andrea Aime' ; 
'Geoserver-devel' 
Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
be "GeoServer 22.0"?

I do not understand why 22.0. I could understand 2.14.0 -> 14.0 (like
Solaris) and then max(GT_VERSION, GS_VERSION). Is 22.0 a typo, or /r/wsh?

On 13/07/18 11:21, br...@frogmouth.net wrote:
> Or the next geotools is 22.0. Version numbers are pretty cheap, wasting a few 
> isn't a big deal.
> 
> -Original Message-
> From: Ben Caradoc-Davies 
> Sent: Friday, 13 July 2018 9:06 AM
> To: br...@frogmouth.net; 'Andrea Aime' ; 
> 'Geoserver-devel' 
> Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
> be "GeoServer 22.0"?
> 
> On 13/07/18 10:13, br...@frogmouth.net wrote:
>> Having geoserver and geotools use the same version numbers would probably be 
>> easier to remember.
> 
> This. Which would make the next GeoServer 20.0. GeoWebCache could get the 
> same treatment.
> 
> Unless we want to call them all 2018.10 (given that 18.x is already in 
> the past).  :-P
> 
> Kind regards,
> 
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited  New Zealand
> 
> 

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Ben Caradoc-Davies]

I do not understand why 22.0. I could understand 2.14.0 -> 14.0 (like 
Solaris) and then max(GT_VERSION, GS_VERSION). Is 22.0 a typo, or 
/r/wsh?


On 13/07/18 11:21, br...@frogmouth.net wrote:

Or the next geotools is 22.0. Version numbers are pretty cheap, wasting a few 
isn't a big deal.

-Original Message-
From: Ben Caradoc-Davies 
Sent: Friday, 13 July 2018 9:06 AM
To: br...@frogmouth.net; 'Andrea Aime' ; 
'Geoserver-devel' 
Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be 
"GeoServer 22.0"?

On 13/07/18 10:13, br...@frogmouth.net wrote:

Having geoserver and geotools use the same version numbers would probably be 
easier to remember.


This. Which would make the next GeoServer 20.0. GeoWebCache could get the same 
treatment.

Unless we want to call them all 2018.10 (given that 18.x is already in the 
past).  :-P

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand




--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[bradh]

Slightly tangential: The date-based thing might work well if we're going to do 
the Enterprise versioning packaging.

-Original Message-
From: Ben Caradoc-Davies  
Sent: Friday, 13 July 2018 9:06 AM
To: br...@frogmouth.net; 'Andrea Aime' ; 
'Geoserver-devel' 
Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
be "GeoServer 22.0"?

On 13/07/18 10:13, br...@frogmouth.net wrote:
> Having geoserver and geotools use the same version numbers would probably be 
> easier to remember.

This. Which would make the next GeoServer 20.0. GeoWebCache could get the same 
treatment.

Unless we want to call them all 2018.10 (given that 18.x is already in the 
past).  :-P

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[bradh]

Or the next geotools is 22.0. Version numbers are pretty cheap, wasting a few 
isn't a big deal.

-Original Message-
From: Ben Caradoc-Davies  
Sent: Friday, 13 July 2018 9:06 AM
To: br...@frogmouth.net; 'Andrea Aime' ; 
'Geoserver-devel' 
Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
be "GeoServer 22.0"?

On 13/07/18 10:13, br...@frogmouth.net wrote:
> Having geoserver and geotools use the same version numbers would probably be 
> easier to remember.

This. Which would make the next GeoServer 20.0. GeoWebCache could get the same 
treatment.

Unless we want to call them all 2018.10 (given that 18.x is already in the 
past).  :-P

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Ben Caradoc-Davies]

On 13/07/18 10:13, br...@frogmouth.net wrote:

Having geoserver and geotools use the same version numbers would probably be 
easier to remember.


This. Which would make the next GeoServer 20.0. GeoWebCache could get 
the same treatment.


Unless we want to call them all 2018.10 (given that 18.x is already in 
the past).  :-P


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Jonathan Moules]

Hi Andrea,

I believe it was Chrome that popularised the "every other release is a 
major release" thing, and so of course FireFox ended up following suit 
(number envy?). Fortunately FireFox has LTS\ESR releases, so sensible 
organisations use those.


Personally I'm a fan of the current Semantic Versioning - 
https://semver.org/ - At least I'm assuming that's what GS is using and 
it's not just a coincidence. Sure GS has major new features in 2.12.x 
that are not in 2.8.x, but it's basically API compatible between 
versions. The recent QGIS 2.x to 3.x is a prime example of a good use of 
a Major increase because it is largely API incompatible.


I suppose if GeoServer is going to continue always being backwards 
compatible then switching number scheme away won't lose anything, and in 
this era of version inflation it may become clearer to some users how 
far behind they are. But if it later starts having jumps where the API 
changes significantly (ala QGIS 2->3), that's going to get really 
confusing ("So lets see, 34 can go to... 43, then you need to manually 
go to 44, then you ").


This reminded me of the thread last year where I posted the versions for 
public GeoServer boxes - 
http://osgeo-org.1560.x6.nabble.com/Stats-on-GeoServer-versions-as-currently-deployed-td5314686.html 
- it really depends what the motivations are for the old versions. I 
haven't done similar with MapServer as yet which might offer some 
interesting insights into the end-user psychology of upgrading as 
they're at 7.1 I think, but over 20+ years.


Just my 2p,

Cheers,

Jonathan


On 2018-07-12 18:27, Andrea Aime wrote:
On Thu, Jul 12, 2018 at 7:21 PM, Chris Snider 
mailto:chris.sni...@polarisalpha.com>> 
wrote:


Just a thought;

Many businesses and governments will grant a project authority to
include a major level of a product, for example GeoServer 2.x.  If
GeoServer moves to a version numbering scheme that adjusts the
commonly viewed major version number, then these users may not be
able to upgrade as readily.  These types of institutions have a
longer lead time to approve major upgrades from 2.x to 3.x etc.


Wondering what do they do with popular browsers, updating their major 
number once every few months?


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 di Montramito 3/A 
55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: 
+39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- /Con 
riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si 
precisa che ogni circostanza inerente alla presente email (il suo 
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è 
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il 
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra 
operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which 
it is addressed and may contain information that is privileged, 
confidential or otherwise protected from disclosure. We remind that - 
as provided by European Regulation 2016/679 “GDPR” - copying, 
dissemination or use of this e-mail or the information herein by 
anyone other than the intended recipient is prohibited. If you have 
received this email by mistake, please notify us immediately by 
telephone or e-mail./




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


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


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Chris Snider]

I am going to forward this chain to another couple of people internal here and 
get back to you.

Chris Snider
Senior Software Engineer
[cid:image001.png@01D2E6A5.9104F820]

From: br...@frogmouth.net [mailto:br...@frogmouth.net]
Sent: Thursday, July 12, 2018 4:14 PM
To: 'Andrea Aime' ; 'Geoserver-devel' 

Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
be "GeoServer 22.0"?

I would suggest adopting semantic versioning, which means everything will be 
major versions (because of the geotools versioning). Having geoserver and 
geotools use the same version numbers would probably be easier to remember.

I do get Chris’ concern (its mainly a US DoD thing – version numbers define the 
amount of testing and the authorities / paper work required; makes no sense at 
all, just policy). One work around could be an “Enterprise GeoServer” product 
(which could have some / all of the extensions bundled into the war.zip / 
-bin.zip) and uses a 1.0.aMxb (where Mx is “maintenance release”). Then a is 
the major release and b is the minor release versions. Would that work for you 
Chris?

From: Andrea Aime 
mailto:andrea.a...@geo-solutions.it>>
Sent: Friday, 13 July 2018 2:33 AM
To: Geoserver-devel 
mailto:geoserver-devel@lists.sourceforge.net>>
Subject: [Geoserver-devel] Thinking out loud... should the next GeoServer be 
"GeoServer 22.0"?

Hi,
thinking out loud, so don't take me too seriously but... should we follow the 
GeoTools example and
switch GeoServer version numbering to a "x.y" approach, just like GeoTools did?

I keep on having people asking me things like "but is Geoserver 2.13.1 much 
different than 2.8.3?"
Heck yes, it's years of development in between... it's a major jump, even if 
the number may not make
it look like that.

GeoServer 1.x ended at 1.7, so GeoServer 2.14.0 should likely be renamed to 22 
(7 + 14 + 1, counting
also 2.0.0 in the mix).

We were keeping 3.x for a "epic storm" kind of change, but even when we 
switched to 2.x we maintained
seamless upgrades, so I guess it's not just in our style to do that kind of 
change, and we can probably
drop the "2."

Opinions?

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 di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: 
+39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- Con riferimento alla 
normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento 
generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza 
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è 
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, 
ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which it is 
addressed and may contain information that is privileged, confidential or 
otherwise protected from disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or 
the information herein by anyone other than the intended recipient is 
prohibited. If you have received this email by mistake, please notify us 
immediately by telephone or e-mail.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[bradh]

I would suggest adopting semantic versioning, which means everything will be 
major versions (because of the geotools versioning). Having geoserver and 
geotools use the same version numbers would probably be easier to remember.

 

I do get Chris’ concern (its mainly a US DoD thing – version numbers define the 
amount of testing and the authorities / paper work required; makes no sense at 
all, just policy). One work around could be an “Enterprise GeoServer” product 
(which could have some / all of the extensions bundled into the war.zip / 
-bin.zip) and uses a 1.0.aMxb (where Mx is “maintenance release”). Then a is 
the major release and b is the minor release versions. Would that work for you 
Chris?

 

From: Andrea Aime  
Sent: Friday, 13 July 2018 2:33 AM
To: Geoserver-devel 
Subject: [Geoserver-devel] Thinking out loud... should the next GeoServer be 
"GeoServer 22.0"?

 

Hi,

thinking out loud, so don't take me too seriously but... should we follow the 
GeoTools example and

switch GeoServer version numbering to a "x.y" approach, just like GeoTools did?

 

I keep on having people asking me things like "but is Geoserver 2.13.1 much 
different than 2.8.3?"

Heck yes, it's years of development in between... it's a major jump, even if 
the number may not make

it look like that.

 

GeoServer 1.x ended at 1.7, so GeoServer 2.14.0 should likely be renamed to 22 
(7 + 14 + 1, counting

also 2.0.0 in the mix).

 

We were keeping 3.x for a "epic storm" kind of change, but even when we 
switched to 2.x we maintained

seamless upgrades, so I guess it's not just in our style to do that kind of 
change, and we can probably

drop the "2."

 

Opinions?

 

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 di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: 
+39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- Con riferimento alla 
normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento 
generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza 
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è 
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, 
ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which it is 
addressed and may contain information that is privileged, confidential or 
otherwise protected from disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or 
the information herein by anyone other than the intended recipient is 
prohibited. If you have received this email by mistake, please notify us 
immediately by telephone or e-mail. 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Chris Snider]

My experience has been that some projects are stuck on old browsers for a long 
time.  For example, one project was stuck on Internet Explorer 11.0 for several 
years, and I believe has only recently been approved to move to Edge.

Same thing applied to Firefox, although I don’t recall what version it was 
stuck on for the longest before upgrades happened.

Chris Snider
Senior Software Engineer
[cid:image001.png@01D2E6A5.9104F820]

From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea 
Aime
Sent: Thursday, July 12, 2018 11:27 AM
To: Chris Snider 
Cc: Geoserver-devel 
Subject: Re: [Geoserver-devel] Thinking out loud... should the next GeoServer 
be "GeoServer 22.0"?

On Thu, Jul 12, 2018 at 7:21 PM, Chris Snider 
mailto:chris.sni...@polarisalpha.com>> wrote:
Just a thought;

Many businesses and governments will grant a project authority to include a 
major level of a product, for example GeoServer 2.x.  If GeoServer moves to a 
version numbering scheme that adjusts the commonly viewed major version number, 
then these users may not be able to upgrade as readily.  These types of 
institutions have a longer lead time to approve major upgrades from 2.x to 3.x 
etc.

Wondering what do they do with popular browsers, updating their major number 
once every few months?

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 di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: 
+39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- Con riferimento alla 
normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento 
generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza 
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è 
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, 
ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which it is 
addressed and may contain information that is privileged, confidential or 
otherwise protected from disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or 
the information herein by anyone other than the intended recipient is 
prohibited. If you have received this email by mistake, please notify us 
immediately by telephone or e-mail.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

[Chris Snider]

Just a thought;

Many businesses and governments will grant a project authority to include a 
major level of a product, for example GeoServer 2.x.  If GeoServer moves to a 
version numbering scheme that adjusts the commonly viewed major version number, 
then these users may not be able to upgrade as readily.  These types of 
institutions have a longer lead time to approve major upgrades from 2.x to 3.x 
etc.

Chris Snider
Senior Software Engineer
[cid:image001.png@01D2E6A5.9104F820]

From: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Sent: Thursday, July 12, 2018 10:33 AM
To: Geoserver-devel 
Subject: [Geoserver-devel] Thinking out loud... should the next GeoServer be 
"GeoServer 22.0"?

Hi,
thinking out loud, so don't take me too seriously but... should we follow the 
GeoTools example and
switch GeoServer version numbering to a "x.y" approach, just like GeoTools did?

I keep on having people asking me things like "but is Geoserver 2.13.1 much 
different than 2.8.3?"
Heck yes, it's years of development in between... it's a major jump, even if 
the number may not make
it look like that.

GeoServer 1.x ended at 1.7, so GeoServer 2.14.0 should likely be renamed to 22 
(7 + 14 + 1, counting
also 2.0.0 in the mix).

We were keeping 3.x for a "epic storm" kind of change, but even when we 
switched to 2.x we maintained
seamless upgrades, so I guess it's not just in our style to do that kind of 
change, and we can probably
drop the "2."

Opinions?

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 di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: 
+39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- Con riferimento alla 
normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento 
generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza 
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è 
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, 
ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which it is 
addressed and may contain information that is privileged, confidential or 
otherwise protected from disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or 
the information herein by anyone other than the intended recipient is 
prohibited. If you have received this email by mistake, please notify us 
immediately by telephone or e-mail.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer documentation builds failing: disk quota exceeded

[Andrea Aime]

Awesome, thank you!

Cheers
Andrea

On Thu, Jul 12, 2018 at 5:52 PM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:

> More space has been added, and the doc build appears to be running
> smoothly again.
>
> Torben
>
> On Wed, Jul 11, 2018 at 4:18 PM, Torben Barsballe <
> tbarsba...@boundlessgeo.com> wrote:
>
>> I'm looking into it, the server has indeed run out of space. Trying to
>> see if I can get the quota enlarged.
>>
>> I'll update when this is fixed.
>>
>> Cheers,
>>
>> Torben
>>
>> On Wed, Jul 11, 2018 at 1:55 AM, Andrea Aime <
>> andrea.a...@geo-solutions.it> wrote:
>>
>>> Hi,
>>> we have a build stuck for 17 hours, the last error message is on rsync,
>>> stating:
>>>
>>> rsync: write failed on 
>>> "/var/www/docs.geoserver.org/htdocs/master/en/api/index.html": Disk quota 
>>> exceeded (122)
>>> en/user/_images/MasterFailed.png
>>>
>>>
>>> Looks like the machine hosting the documentation is in need of a
>>> cleanup, or a larger quota?
>>>
>>> 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 di Montramito 3/A 55054 Massarosa
>>> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
>>> http://www.geo-solutions.it http://twitter.com/geosolutions_it
>>> --- *Con
>>> riferimento alla normativa sul trattamento dei dati personali (Reg. UE
>>> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail.*
>>>
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>>
>>
>


-- 

Regards, Andrea Aime == 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 di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer documentation builds failing: disk quota exceeded

[Torben Barsballe]

More space has been added, and the doc build appears to be running smoothly
again.

Torben

On Wed, Jul 11, 2018 at 4:18 PM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:

> I'm looking into it, the server has indeed run out of space. Trying to see
> if I can get the quota enlarged.
>
> I'll update when this is fixed.
>
> Cheers,
>
> Torben
>
> On Wed, Jul 11, 2018 at 1:55 AM, Andrea Aime  > wrote:
>
>> Hi,
>> we have a build stuck for 17 hours, the last error message is on rsync,
>> stating:
>>
>> rsync: write failed on 
>> "/var/www/docs.geoserver.org/htdocs/master/en/api/index.html": Disk quota 
>> exceeded (122)
>> en/user/_images/MasterFailed.png
>>
>>
>> Looks like the machine hosting the documentation is in need of a cleanup,
>> or a larger quota?
>>
>> 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 di Montramito 3/A 55054 Massarosa
>> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
>> http://www.geo-solutions.it http://twitter.com/geosolutions_it
>> --- *Con riferimento
>> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
>> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto, gli eventuali
>> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
>> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
>> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
>> sarei comunque grato se potesse darmene notizia. This email is intended
>> only for the person or entity to which it is addressed and may contain
>> information that is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European Regulation 2016/679
>> “GDPR” - copying, dissemination or use of this e-mail or the information
>> herein by anyone other than the intended recipient is prohibited. If you
>> have received this email by mistake, please notify us immediately by
>> telephone or e-mail.*
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Pre-Proposal: WPS Extension "GetExecutions" Operation

[Alessio Fabiani]

Dear lists,
I would like here to ask your opinion about a possible
extension/improvement of the GeoServer WPS Service.

*The main goal of this proposal is to allow a client to recognize the list
of WPS Executions through a simple request to a WPS Operation. What we
would like to achieve would be something similar to this:*

[image: image.png]



*The client makes a simple “GetExecutions” request to the WPS Server, in
order to get back an XML document containing the list of current Execution
Statuses.Ideally should be possible also to filter the “GetExecutions”
request along with simple parameters, in order to refine the output and get
back only the executions status we are looking for.Adding a bit more to
this, if AUTHORIZATION headers are sent along with the “GetExecutions”
request, the WPS Server should be able, if a security subsystem is
available and enable on the latter, of provide also the list of eventually
private/protected resources to the client itself.Part of this proposal is
also to review and improve the “lineage” option of the WPS service,
allowing a client to retrieve the Execute Inputs values provided to the
process Identifier.*
Thoughts?

-- 

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==
Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


GeoSolutions S.A.S.
Via di Montramito 3/A - 55054  Massarosa (LU) - Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39 331 6233686


http://www.geo-solutions.it
http://twitter.com/geosolutions_it
---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.


This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel