[Geoserver-devel] About backport for fixes in GT and GS

Dear All,
first of all sorry for crossposting but I believe it is needed in this case.

I was discussing this with Andrea these days and we decided to bring
this up to the developers.
I am noticing that people tend to fix issues only on trunk for GT and
GS ( I would also add GWC) without backporting on stable and
maintenance.
I know there is not policy at this stage for backporting fixes
(correct me if I ma wrong) but I would suggest that we come up with
something.

If it was up to me I would say that whenever an issue is discovered we
should strive to fix on all active branches. I believe
that should be the mandatory behaviour and deviations should be
justified on the ML. Otherwise I don't see the value in having
branches aside master.

Opinions?

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.

In general people have been good about waiting a month and asking about back porting functionality changes. I am not sure why fixes are getting left by the wayside.

Do you have any specific fixes we can talk about Simone? I would like to know if there is a pattern …

···

On 24 June 2015 at 10:33, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Dear All,
first of all sorry for crossposting but I believe it is needed in this case.

I was discussing this with Andrea these days and we decided to bring
this up to the developers.
I am noticing that people tend to fix issues only on trunk for GT and
GS ( I would also add GWC) without backporting on stable and
maintenance.
I know there is not policy at this stage for backporting fixes
(correct me if I ma wrong) but I would suggest that we come up with
something.

If it was up to me I would say that whenever an issue is discovered we
should strive to fix on all active branches. I believe
that should be the mandatory behaviour and deviations should be
justified on the ML. Otherwise I don’t see the value in having
branches aside master.

Opinions?

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.


Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.coms.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel


Jody Garnett

Ciao Jody,
thanks for taking the time to answer this, but I am afraid you are
missing the point.
I am not try to fingerpoint at someone or to understand why someone
might not have backported something.

The point is that having three live branches, we should have rules
that regulates how and when a fix must be backported.
Then we can volunteer to vigilate and even to help with backports, but
if at the moment there is no rule for this case I am bringing this up
as a potential loophole in our release model, which btw has also been
pointed out by a few clients already.

Long story short, IMHO no regular backports might lead to less
meaningful mantenaince releases.

So, what could we do? :slight_smile:

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, Jun 24, 2015 at 10:23 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

In general people have been good about waiting a month and asking about back
porting functionality changes. I am not sure why fixes are getting left by
the wayside.

Do you have any specific fixes we can talk about Simone? I would like to
know if there is a pattern ...

--
Jody Garnett

On 24 June 2015 at 10:33, Simone Giannecchini
<simone.giannecchini@anonymised.com> wrote:

Dear All,
first of all sorry for crossposting but I believe it is needed in this
case.

I was discussing this with Andrea these days and we decided to bring
this up to the developers.
I am noticing that people tend to fix issues only on trunk for GT and
GS ( I would also add GWC) without backporting on stable and
maintenance.
I know there is not policy at this stage for backporting fixes
(correct me if I ma wrong) but I would suggest that we come up with
something.

If it was up to me I would say that whenever an issue is discovered we
should strive to fix on all active branches. I believe
that should be the mandatory behaviour and deviations should be
justified on the ML. Otherwise I don't see the value in having
branches aside master.

Opinions?

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.

------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Thu, Jun 25, 2015 at 9:41 AM, Simone Giannecchini <
simone.giannecchini@anonymised.com> wrote:

Long story short, IMHO no regular backports might lead to less
meaningful mantenaince releases.

I believe he means, no regular backports of bug fixes :slight_smile:

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.

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

No I understand, and I agree we should ask for bug fixes to be back ported. I can even add this to my list of dev guide changes fit Geoserver.

Beyond that I am trying to see what kind of fixes we are missing. I know Boundlesd staff would often focus on 2.7. I often focus just on GeoTools master.

Is there any way we can improve our game and make this easier. Like discuss backports when the fix is a pull request?

···

On Thu, Jun 25, 2015 at 9:41 AM, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Long story short, IMHO no regular backports might lead to less
meaningful mantenaince releases.

I believe he means, no regular backports of bug fixes :slight_smile:

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,
please, read below...

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 Thu, Jun 25, 2015 at 4:39 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I understand, and I agree we should ask for bug fixes to be back ported.
I can even add this to my list of dev guide changes fit Geoserver.

Beyond that I am trying to see what kind of fixes we are missing. I know
Boundlesd staff would often focus on 2.7. I often focus just on GeoTools
master.

And 2.6? :slight_smile:

This attitude makes 2.6 useles since fixes are not ported over.

Is there any way we can improve our game and make this easier. Like discuss
backports when the fix is a pull request?

I believe my position is clear, fixes _must_ be backported otherwise 3
branches are useless.
I know it is a strong statement, but we need to find a (cooperative)
way to make this happen.
Just stating that if someone provides a fix he must also provide
backports might be too strong (although I would prefer it over
free will) hence I am open to see alternatives. On the other side,
discussing on the ML each single fix seems an overkill to me.

At the very least I believe that we shall ask people to investigate
and report on whether a fix can be backported and then encourage to do
the backport.
I would like to make the backport mandatory but it might be better to
make it recommended.

At the very least we need to make everyone responsible for:

-1- investigating if the issue impact all the active branches
-2- investigating whether a fix is possible
-3- capturing this in jira

Actual backporting can stay a volunteer based action for the time
being, I am keen in spending some of our time on doing that.

On Thu, Jun 25, 2015 at 12:50 AM Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Thu, Jun 25, 2015 at 9:41 AM, Simone Giannecchini
<simone.giannecchini@anonymised.com> wrote:

Long story short, IMHO no regular backports might lead to less
meaningful mantenaince releases.

I believe he means, no regular backports of bug fixes :slight_smile:

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.

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

--
--
Jody Garnett

> Is there any way we can improve our game and make this easier. Like
discuss

backports when the fix is a pull request?

I believe my position is clear, fixes _must_ be backported otherwise 3
branches are useless.
I know it is a strong statement, but we need to find a (cooperative)
way to make this happen.
Just stating that if someone provides a fix he must also provide
backports might be too strong (although I would prefer it over
free will) hence I am open to see alternatives. On the other side,
discussing on the ML each single fix seems an overkill to me.

At the very least I believe that we shall ask people to investigate
and report on whether a fix can be backported and then encourage to do
the backport.
I would like to make the backport mandatory but it might be better to
make it recommended.

At the very least we need to make everyone responsible for:

-1- investigating if the issue impact all the active branches
-2- investigating whether a fix is possible
-3- capturing this in jira

Actual backporting can stay a volunteer based action for the time
being, I am keen in spending some of our time on doing that.

Simone I have updated https://github.com/geoserver/geoserver/wiki/GSIP-129
based on this discussion (since the dev guide is already under review).
Can you review, I think we could call that proposal to vote and get started
on making the required edits.

Aside: We can look at a similar proposal for GeoTools developers guide. I
did not mean to give offence earlier, Kevin and myself will look out for
fixes Boundless has provided, and the little geotools volunteer work I do
is not generally suitable for back porting.

Dear Jody,
please, read below....

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 Thu, Jun 25, 2015 at 9:26 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

> Is there any way we can improve our game and make this easier. Like
> discuss

> backports when the fix is a pull request?

I believe my position is clear, fixes _must_ be backported otherwise 3
branches are useless.
I know it is a strong statement, but we need to find a (cooperative)
way to make this happen.
Just stating that if someone provides a fix he must also provide
backports might be too strong (although I would prefer it over
free will) hence I am open to see alternatives. On the other side,
discussing on the ML each single fix seems an overkill to me.

At the very least I believe that we shall ask people to investigate
and report on whether a fix can be backported and then encourage to do
the backport.
I would like to make the backport mandatory but it might be better to
make it recommended.

At the very least we need to make everyone responsible for:

-1- investigating if the issue impact all the active branches
-2- investigating whether a fix is possible
-3- capturing this in jira

Actual backporting can stay a volunteer based action for the time
being, I am keen in spending some of our time on doing that.

Simone I have updated https://github.com/geoserver/geoserver/wiki/GSIP-129
based on this discussion (since the dev guide is already under review).
Can you review, I think we could call that proposal to vote and get started
on making the required edits.

I am about to review and edit a little.

Aside: We can look at a similar proposal for GeoTools developers guide.

Let me know if you want me to do that.

I
did not mean to give offence earlier, Kevin and myself will look out for
fixes Boundless has provided, and the little geotools volunteer work I do is
not generally suitable for back porting.

I never get offended by emails unless they are explicitly offensive :slight_smile:
This is something I learnt a long time ago.