Re: Thoughts on release cadence?

[Sean Owen]

I'll fix that. It should just be removed as there is a whole section on
this below. Missed that one.

On Thu, Aug 24, 2017, 16:56 Tom Graves  wrote:

> I think we need to up date the FEATURE section on the version policy page
> to match.  It says feature releases are every 4 months.
>
>
> Tom
> On Monday, July 31, 2017, 2:23:10 PM CDT, Sean Owen 
> wrote:
>
>
> Done at https://spark.apache.org/versioning-policy.html
>
> On Mon, Jul 31, 2017 at 6:22 PM Reynold Xin  wrote:
>
> We can just say release in December, and code freeze mid Nov?
>
> On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen  wrote:
>
> Will do, just was waiting for some feedback. I'll give approximate dates
> towards the end of the year. It isn't binding or anything.
>
>

Re: Thoughts on release cadence?

[Tom Graves]

I think we need to up date the FEATURE section on the version policy page to 
match.  It says feature releases are every 4 months.

TomOn Monday, July 31, 2017, 2:23:10 PM CDT, Sean Owen  
wrote:

Done at https://spark.apache.org/versioning-policy.html

On Mon, Jul 31, 2017 at 6:22 PM Reynold Xin  wrote:

We can just say release in December, and code freeze mid Nov? 
On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen  wrote:

Will do, just was waiting for some feedback. I'll give approximate dates 
towards the end of the year. It isn't binding or anything.

Re: Thoughts on release cadence?

[Anirudh Ramanathan]

Is now the best time for submitting a SPIP
 for a feature
targeting the 2.3 release?

On Mon, Jul 31, 2017 at 12:22 PM, Sean Owen  wrote:

> Done at https://spark.apache.org/versioning-policy.html
>
> On Mon, Jul 31, 2017 at 6:22 PM Reynold Xin  wrote:
>
>> We can just say release in December, and code freeze mid Nov?
>>
>> On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen  wrote:
>>
>>> Will do, just was waiting for some feedback. I'll give approximate dates
>>> towards the end of the year. It isn't binding or anything.
>>
>>

Re: Thoughts on release cadence?

[Sean Owen]

Done at https://spark.apache.org/versioning-policy.html

On Mon, Jul 31, 2017 at 6:22 PM Reynold Xin  wrote:

> We can just say release in December, and code freeze mid Nov?
>
> On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen  wrote:
>
>> Will do, just was waiting for some feedback. I'll give approximate dates
>> towards the end of the year. It isn't binding or anything.
>
>

Re: Thoughts on release cadence?

[Reynold Xin]

We can just say release in December, and code freeze mid Nov?

On Mon, Jul 31, 2017 at 10:14 AM, Sean Owen  wrote:

> Will do, just was waiting for some feedback. I'll give approximate dates
> towards the end of the year. It isn't binding or anything.
>
>
> On Mon, Jul 31, 2017, 18:06 Michael Armbrust 
> wrote:
>
>> +1, should we update https://spark.apache.org/versioning-policy.html ?
>>
>> On Sun, Jul 30, 2017 at 3:34 PM, Reynold Xin  wrote:
>>
>>> This is reasonable ... +1
>>>
>>>
>>> On Sun, Jul 30, 2017 at 2:19 AM, Sean Owen  wrote:
>>>
 The project had traditionally posted some guidance about upcoming
 releases. The last release cycle was about 6 months. What about penciling
 in December 2017 for 2.3.0? http://spark.apache.org
 /versioning-policy.html

>>>
>>>
>>

Re: Thoughts on release cadence?

[Sean Owen]

Will do, just was waiting for some feedback. I'll give approximate dates
towards the end of the year. It isn't binding or anything.

On Mon, Jul 31, 2017, 18:06 Michael Armbrust  wrote:

> +1, should we update https://spark.apache.org/versioning-policy.html ?
>
> On Sun, Jul 30, 2017 at 3:34 PM, Reynold Xin  wrote:
>
>> This is reasonable ... +1
>>
>>
>> On Sun, Jul 30, 2017 at 2:19 AM, Sean Owen  wrote:
>>
>>> The project had traditionally posted some guidance about upcoming
>>> releases. The last release cycle was about 6 months. What about penciling
>>> in December 2017 for 2.3.0?
>>> http://spark.apache.org/versioning-policy.html
>>>
>>
>>
>

Re: Thoughts on release cadence?

[Michael Armbrust]

+1, should we update https://spark.apache.org/versioning-policy.html ?

On Sun, Jul 30, 2017 at 3:34 PM, Reynold Xin  wrote:

> This is reasonable ... +1
>
>
> On Sun, Jul 30, 2017 at 2:19 AM, Sean Owen  wrote:
>
>> The project had traditionally posted some guidance about upcoming
>> releases. The last release cycle was about 6 months. What about penciling
>> in December 2017 for 2.3.0? http://spark.apache.org
>> /versioning-policy.html
>>
>
>

Re: Thoughts on release cadence?

[Reynold Xin]

This is reasonable ... +1


On Sun, Jul 30, 2017 at 2:19 AM, Sean Owen  wrote:

> The project had traditionally posted some guidance about upcoming
> releases. The last release cycle was about 6 months. What about penciling
> in December 2017 for 2.3.0? http://spark.apache.org/versioning-policy.html
>

Re: Thoughts on release cadence?

[Dongjoon Hyun]

+1

Bests,
Dongjoon

On Sun, Jul 30, 2017 at 02:20 Sean Owen  wrote:

> The project had traditionally posted some guidance about upcoming
> releases. The last release cycle was about 6 months. What about penciling
> in December 2017 for 2.3.0? http://spark.apache.org/versioning-policy.html
>

Thoughts on release cadence?

[Sean Owen]

The project had traditionally posted some guidance about upcoming releases.
The last release cycle was about 6 months. What about penciling in December
2017 for 2.3.0? http://spark.apache.org/versioning-policy.html