>
> Mid-to-late September is good, but so is October.
The community-driven Cassandra Japan conference is tentatively
targeting the first week of October. We've had participants from Japan
the past couple of years at NGCC, so would be cool if we could
accommodate that.
+1 on Mid September. (We sho
+1.
Are there guidelines for how to set something like this up or is it tribal
knowledge?
On Wed, May 31, 2017 at 3:05 PM Gary Dusbabek wrote:
> +1. I'm happy to help with logistics.
>
> Mid-to-late September is good, but so is October.
>
> Gary.
>
> On Wed, May 31, 2017 at 2:19 PM, Eric Evans
+1. I'm happy to help with logistics.
Mid-to-late September is good, but so is October.
Gary.
On Wed, May 31, 2017 at 2:19 PM, Eric Evans
wrote:
> Hi,
>
> Is anyone working on an NGCC event for this year? Given all of the
> recent changes, it seems like it could be really useful. If not, is
>
I would love for this to happen as well. I don't have time to run
point on setting up an event, but am happy to help out. (I think a lot
of people feel similarly).
On Thu, Jun 1, 2017 at 7:19 AM, Eric Evans wrote:
> Hi,
>
> Is anyone working on an NGCC event for this year? Given all of the
> rece
Hi,
Is anyone working on an NGCC event for this year? Given all of the
recent changes, it seems like it could be really useful. If not, is
there interest? When would be good, September? October? What about
location? I think we could get the space to host such an even in
either San Antonio (central
I would guess there are way fewer people who have already upgraded than people
who haven't. So better to fix this as fast as possible and cut a release than
wait longer and not. At the very least we should pull 3.0.13 so even less
people can/have upgrade to it.
> On May 31, 2017, at 7:45 AM, J
The number of people isn't zero. Before we commit and cut a new release, we
need to be able to explain what that upgrade path is.
If this is just migration storms then it's not worth cutting a new release -
3.0 was doing that anyway until very recently. If it fails to start that's a
much bigger
On 31.05.2017 09:34, Stefania Alborghetti wrote:
> There shouldn't be too many people with 3.0.13 in
> production however, since upgrading to 3.0.13 is broken in the first place.
Keep in mind that there are always people upgrading from 2.x, especially
since we had a couple of important bug fixes
The patch for 13559 is available if we want to release it in 3.0.14. The
tests are still running but I don't expect problems. We need a reviewer
however.
Releasing the patch in 3.0.14 will cause problems for people that deployed
3.0.13 and upgrade upwards, but the schema will agree once the rollin