support/1.13 was cut on May 4, 2020 as per Geode's published time-based
schedule [1] (Monday on or after Feb 1, May 1, Aug 1, Nov 1)
prior to the expected Aug 3 date to cut support/1.14, the Geode community
decided in July [2] that the usual quarterly schedule would not apply to 1.14,
and then
Build Update for apache/geode-native
-
Build: #2986
Status: Canceled
Duration: ?
Commit: a939452 (develop)
Author: M. Oleske
Message: update sqlite (#735)
View the changeset:
https://github.com/apache/geode-native/compare/5600a6b1fc26...a93945217aef
View
Having just spent some time yanking out some of the really really old version
support I think a naive version knocking approach would work. During the client
handshake the server will reject and close the connection of any client with a
newer version number than it supports. The client could
In my ideal world, the version represents the protocol version and not a
product release number. As Dan points out, we could add a negotiation option to
allow more flexibility between clients and servers.
To accomplish this we would need a simpler and well-specified protocol. The
current
On Jan 29, 2021, at 3:47 PM, Dan Smith
mailto:dasm...@vmware.com>> wrote:
I do think at least implementing some automated checking for whatever
compatibility we intend to provide is a good idea.
I have a branch with a test using Abigail [1]. This branch depends on merging
of a CI branch. It
