This vote is now cancelled.
Based on the comments, I will cut a new RC when we have fixes for GEODE-4913
and GEODE-4787.
On Fri, Mar 23, 2018 at 3:11 PM Udo Kohlmeyer wrote:
> -1 Due to the regression in functionality. GEODE-4913
>
> @John, I agree, GEODE-4787 should be addressed with priority
-1 Due to the regression in functionality. GEODE-4913
@John, I agree, GEODE-4787 should be addressed with priority.
--Udo
On 3/23/18 15:04, John Blum wrote:
The same could be said of GEODE-4787.
On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker wrote:
Thanks for catching this Diane. I agree;
The same could be said of GEODE-4787.
On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker wrote:
> Thanks for catching this Diane. I agree; we shouldn't break something that
> used to work.
>
> Anthony
>
>
> On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote:
>
> -1
> I filed GEODE-4913 based on scr
Thanks for catching this Diane. I agree; we shouldn't break something that
used to work.
Anthony
On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote:
-1
I filed GEODE-4913 based on scripts I have that create 2 clusters connected
by a WAN gateway on my local machine.
*Problem*: we are opening a
-1
I filed GEODE-4913 based on scripts I have that create 2 clusters connected
by a WAN gateway on my local machine.
*Problem*: we are opening a cache-server on default port (40404)
irrespective of the fact that one is explicitly specified in cache.xml.
*symptoms*: users who start more than one Geo
+1
Run geode-release-check. Verified no MD5 files in the distribution.
-Dan
On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker wrote:
> +1
>
> - verified signatures and checksums
> - checked source release for binaries
> - basic gfsh testing
> - ran all the examples
>
> Anthony
>
> > On Mar 20, 2
+1
- verified signatures and checksums
- checked source release for binaries
- basic gfsh testing
- ran all the examples
Anthony
> On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar wrote:
>
> This is the first release candidate for Apache Geode, version 1.5.0.
> Thanks to all the community members
Yep, the build inserts the username (in this case the release manager) into the
version properties file.
Anthony
> On Mar 21, 2018, at 10:20 AM, Jens Deppe wrote:
>
> Is it normal for the build id to contain an actual username. As in:
>
> Build-Date: 2018-03-20 11:43:49 -0700
> Build-Id: *
Is it normal for the build id to contain an actual username. As in:
Build-Date: 2018-03-20 11:43:49 -0700
Build-Id: *sbawaskar* 0
Build-Java-Version: 1.8.0_121
Build-Platform: Mac OS X 10.13.3 x86_64
Product-Name: Apache Geode
Product-Version: 1.5.0
Source-Date: 2018-03-19 10:31:04 -
+1 User Guide builds correctly from source, javadocs look up-to-date
On Wed, Mar 21, 2018 at 8:27 AM, Jens Deppe wrote:
> +1 - basic gfsh functionality looks good on Windows.
>
> On Tue, Mar 20, 2018 at 5:07 PM, Anthony Baker wrote:
>
> > md5 generation is already removed from geode, just need
+1 - basic gfsh functionality looks good on Windows.
On Tue, Mar 20, 2018 at 5:07 PM, Anthony Baker wrote:
> md5 generation is already removed from geode, just need to do this for
> geode-examples.
>
> Anthony
>
>
> > On Mar 20, 2018, at 3:30 PM, Swapnil Bawaskar
> wrote:
> >
> > Removed!
> >
>
md5 generation is already removed from geode, just need to do this for
geode-examples.
Anthony
> On Mar 20, 2018, at 3:30 PM, Swapnil Bawaskar wrote:
>
> Removed!
>
> I also filed a JIRA to not generate the md5 checksum file going forward:
> https://issues.apache.org/jira/browse/GEODE-4903
>
The release dir looked fine to me. Were you looking at maven? Those are
automatically generated during the upload and we don’t have explicit control
over them. I’ve spent hours just trying to get rid of the hash files for the
signatures :(
Anthony
> On Mar 20, 2018, at 3:18 PM, Dan Smith
Removed!
I also filed a JIRA to not generate the md5 checksum file going forward:
https://issues.apache.org/jira/browse/GEODE-4903
On Tue, Mar 20, 2018 at 3:18 PM Dan Smith wrote:
> It looks like we are still generating .md5 files. That doesn't necessarily
> need to hold up this release (you co
It looks like we are still generating .md5 files. That doesn't necessarily
need to hold up this release (you could just delete them from SVN), but
we're not supposed to be distributing .md5 files anymore.
http://www.apache.org/dev/release-distribution#sigs-and-sums
-Dan
On Tue, Mar 20, 2018 at 3
15 matches
Mail list logo