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' <andrea.a...@geo-solutions.it>; 'Geoserver-devel'
<geoserver-devel@lists.sourceforge.net>
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
<andrea.a...@geo-solutions.it<mailto:andrea.a...@geo-solutions.it>>
Sent: Friday, 13 July 2018 2:33 AM
To: Geoserver-devel
<geoserver-devel@lists.sourceforge.net<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
