From 94ba2e09dfff8a3d1c74e9ba36208298a97aece3 Mon Sep 17 00:00:00 2001 From: RoyalBlueRanger Date: Sun, 24 Nov 2019 23:19:10 -0500 Subject: [PATCH] Final update for v3.5.2-alpha.6 and looking good for a build artifact! The next release with be beta! --- changelog_v3.5.x.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/changelog_v3.5.x.md b/changelog_v3.5.x.md index 487713825..4ab459376 100644 --- a/changelog_v3.5.x.md +++ b/changelog_v3.5.x.md @@ -14,6 +14,11 @@ and address some of the outstanding bugs. If I can leave this in a slightly better state from what I found it, then I will consider this a success. +## tag v3.5.2-beta.1 - Next tag will be beta!! + +We are done with alpha tagging! Time to focus on getting this released! + + ## tag v3.5.2-alpha.6 - 2019-11-24 * **Guava Caching - Google Caching - Redundancy** @@ -168,7 +173,7 @@ then make needed adjustments before moving onward. * gradlew build :: Will build project with the new version to ensure all is good. If build is good, then you can try to upgrade to the next version. - * v5.0 Incompatibility issues: + * Gradle v4.10.3 v5.0 Incompatibility issues: * v4.6 hit an incompatibility with v5.0 with command line warnings - Added the gradle.properties to better control the logging of errors. * v4.7 hit another incompatibility with v5.0 with the lack of annotationProcessor for resources that are using annotations. - Later versions of Gradle identified the source of this issue and I was able to add an annotationProcessor to the prison-sponge's build.gradle settings. * v4.9 hit another incompatibility with v5.0. The 'deferred configurable' behavior of the 'publishing {}' block has been deprecated. From what I can tell, it should be all right? @@ -177,6 +182,10 @@ then make needed adjustments before moving onward. I'm going to call it quits for now with upgrading gradle. v4.10.3 is closer to a current release and I need more time to review the last few issues. +* **Few minor bug fixes** +A few changes that fixed when the mines and ranks were being saved. There were a few issues +with them saving when there were no changes made (server start and shutdown). + **Build artifacts:** Be aware that this build artifact is not production grade and still needs more testing.