I believe support for Mongo was added by Gary so I am expecting he might have
more input into this.
Ralph
> On Jun 2, 2019, at 3:17 PM, Matt Sicker wrote:
>
> I haven't kept up with MongoDB in quite some time (I'm more interested
> in tech like Cassandra or Postgres), so I wouldn't be able to
I haven't kept up with MongoDB in quite some time (I'm more interested
in tech like Cassandra or Postgres), so I wouldn't be able to say
there. If it's anything like other databases, it might work to simply
use the oldest compatible driver that supports the necessary features.
On Sun, 2 Jun 2019 a
Looking at the MongoDB web site I see release 4 and release 3. We have support
for release 2 and 3. Do we really need support for version 2 in the 3.0 branch?
Is anything special required to support MongoDB 4?
Ralph
Oh, it's only a toolchain issue? Not a big problem I suppose. I'm
already using Java 11 as my default JDK for Log4j right now, and it
mostly works (other than a removed class from sun.reflect that's
tested in a unit test; that's to be expected due to the StackWalker
API).
On Sun, 2 Jun 2019 at 13:
Gary,
In looking at the changes.xml in 3.0 it looks like you are adding notations to
both the 2.x and 3.x releases. That doesn’t make any sense. A change should be
noted ONLY in the release in which it was first published. Can you please go
through all the actions you added to the 3.0 release
I don’t understand. Future 2.x releases will still be compatible with Java 7.
Maven just has to be run using Java 8. Due to toolchains all the compiles will
still be done using the Java 7 compiler.
> On Jun 2, 2019, at 10:55 AM, Matt Sicker wrote:
>
> Is there a last working version compatible
I can help finish the release with any PMC-specific aspects. We can
certainly help explain any release steps. Making a new release guide
for the audit component would be great, too.
On Sun, 2 Jun 2019 at 12:56, Ralph Goers wrote:
>
> I should also add that there are a couple of steps that have to
On Thu, 30 May 2019 at 01:17, Ralph Goers wrote:
>
> I have been working on a large commit for 3.0 to change how plugins are bound
> and to move the plugin code to its own module. Following that I plan on going
> through more Jira issues that are critical. I know of a few that I feel need
> to
I should also add that there are a couple of steps that have to be performed by
a PMC member but those are after the release vote. If feel up to giving it a
try that would be great!
Ralph
> On Jun 2, 2019, at 10:54 AM, Ralph Goers wrote:
>
> Yes, I more or less follow the same process. Since
Is there a last working version compatible with java 7 that we can use for
our 2.x releases?
On Sat, Jun 1, 2019 at 21:59, Ralph Goers
wrote:
> In testing on Windows I suddenly discovered that the support I added for
> Spring Cloud Config now requires that the build run using Java 8. This is
> b
Yes, I more or less follow the same process. Since it uses Java 8 it doesn’t
need to add the TLS property though.
Ralph
> On Jun 2, 2019, at 9:46 AM, Matt Sicker wrote:
>
> This looks to be one of the few components that doesn't have a dedicated
> release guide on the wiki yet. This likely fol
This looks to be one of the few components that doesn't have a dedicated
release guide on the wiki yet. This likely follows the same steps as the
Log4j 2 release guide, though:
https://cwiki.apache.org/confluence/display/LOGGING/Log4j+2+Release+Process
On Sun, Jun 2, 2019 at 06:04, Andrei Ivanov
Hi,
I would really like to see 1.0.2 released.
Do you think there's anything else that should go in?
Is there a release procedure documented somewhere so I can do that myself?
Thank you,
Andrei
13 matches
Mail list logo
