Request for rights to write comments on Apache Geode Confluence

[Jakov Varenina]

Hi devs,

Could you please give me rights to write comments on Apache Geode 
Confluence page?


username: jakov.varenina

BRs,

Jakov

Re: Request for rights to write comments on Apache Geode Confluence

[Dan Smith]

Done. You should have access now.

Thanks!
-Dan

From: Jakov Varenina 
Sent: Monday, January 11, 2021 2:09 AM
To: dev@geode.apache.org 
Subject: Request for rights to write comments on Apache Geode Confluence

Hi devs,

Could you please give me rights to write comments on Apache Geode
Confluence page?

username: jakov.varenina

BRs,

Jakov

[DISCUSSION] Should We Backport Publishing of Geode Tomcat Module

[Sarah Abbey]

Hey, Geode Devs!

Ben Ross and I are currently working on session state in Geode.  In order to 
include the Geode Tomcat session module in the Geode artifacts published to 
Maven, we had to update the module so it publishes to Maven (as seen in this 
PR and this 
PR).  This change is only on the 
current develop branch.  We are now wondering if these changes should be 
backported to older versions of Geode.

What does everyone think?  If it should be backported, to which versions should 
it be backported?

Thank you,
Sarah

Re: [DISCUSSION] Should We Backport Publishing of Geode Tomcat Module

[Owen Nichols]

If this is just adding an additional published artifact, sounds like there 
would be no backward-compatibility issue or breaking change...feel free to 
backport to support/1.13 and support/1.12 if desired.  

Currently there has been no proposal for a Geode 1.13.2 or 1.12.1 release, but 
you're welcome to make such proposal(s) and volunteer as release manager if you 
need a release of Geode with this sooner than 1.14

On 1/11/21, 10:10 AM, "Sarah Abbey"  wrote:

Hey, Geode Devs!

Ben Ross and I are currently working on session state in Geode.  In order 
to include the Geode Tomcat session module in the Geode artifacts published to 
Maven, we had to update the module so it publishes to Maven (as seen in this 
PR
 and this 
PR).
  This change is only on the current develop branch.  We are now wondering if 
these changes should be backported to older versions of Geode.

What does everyone think?  If it should be backported, to which versions 
should it be backported?

Thank you,
Sarah

Re: [DISCUSSION] Should We Backport Publishing of Geode Tomcat Module

[Anilkumar Gingade]

Is there a user request to use this in an older version?
How easy is it to backport?
From the comments, it looks like it is needed for Geode artifacts published to 
Maven? Is this true?

If there is no user request, and there is other way to include Tomcat session, 
my view is to not backport, but I am not expert in this area, if there is 
recommendation to backport, I am fine to. And if it has to be backported, it 
should be on the version widely used and above(say 1.10 and above, again 
depending on how easy to backport)...

-Anil.


On 1/11/21, 10:10 AM, "Sarah Abbey"  wrote:

Hey, Geode Devs!

Ben Ross and I are currently working on session state in Geode.  In order 
to include the Geode Tomcat session module in the Geode artifacts published to 
Maven, we had to update the module so it publishes to Maven (as seen in this 
PR
 and this 
PR).
  This change is only on the current develop branch.  We are now wondering if 
these changes should be backported to older versions of Geode.

What does everyone think?  If it should be backported, to which versions 
should it be backported?

Thank you,
Sarah

Re: [DISCUSSION] Should We Backport Publishing of Geode Tomcat Module

[Sarah Abbey]

Hey, Anil,

It would be really easy to backport.  It is needed for the Geode Tomcat Module 
to be published to Maven along with the other Geode artifacts.  These changes 
could be made locally and the artifacts could be published to local Maven or 
some other artifactory, but it is easier for the user if they are available 
alongside other Geode artifacts in Maven.

There is no user request for this specifically, and we don't need a minor 
release of Geode.  We just thought it might be nice to include if a minor 
version of a past Geode release is created in the future.

From: Anilkumar Gingade 
Sent: Monday, January 11, 2021 2:51 PM
To: dev@geode.apache.org 
Subject: Re: [DISCUSSION] Should We Backport Publishing of Geode Tomcat Module

Is there a user request to use this in an older version?
How easy is it to backport?
From the comments, it looks like it is needed for Geode artifacts published to 
Maven? Is this true?

If there is no user request, and there is other way to include Tomcat session, 
my view is to not backport, but I am not expert in this area, if there is 
recommendation to backport, I am fine to. And if it has to be backported, it 
should be on the version widely used and above(say 1.10 and above, again 
depending on how easy to backport)...

-Anil.


On 1/11/21, 10:10 AM, "Sarah Abbey"  wrote:

Hey, Geode Devs!

Ben Ross and I are currently working on session state in Geode.  In order 
to include the Geode Tomcat session module in the Geode artifacts published to 
Maven, we had to update the module so it publishes to Maven (as seen in this 
PR
 and this 
PR).
  This change is only on the current develop branch.  We are now wondering if 
these changes should be backported to older versions of Geode.

What does everyone think?  If it should be backported, to which versions 
should it be backported?

Thank you,
Sarah

Re: Request for rights to write comments on Apache Geode Confluence

[Jakov Varenina]

Thank you, Dan!

BRs,

Jakov

On 11. 01. 2021. 18:40, Dan Smith wrote:

Done. You should have access now.

Thanks!
-Dan

From: Jakov Varenina 
Sent: Monday, January 11, 2021 2:09 AM
To: dev@geode.apache.org 
Subject: Request for rights to write comments on Apache Geode Confluence

Hi devs,

Could you please give me rights to write comments on Apache Geode
Confluence page?

username: jakov.varenina

BRs,

Jakov