I'll post the checklist along with the preview release candidate (RC0).
I actually wanted to create it today (as announced three days ago) but
apache's git repositories are down :(
I'll try again tomorrow.
On Tue, Mar 31, 2015 at 11:35 AM, Maximilian Michels wrote:
> +1
>
> Would be great if we
+1
Would be great if we created a checklist with all the things to watch out
for when testing the release candidate.
On Mon, Mar 30, 2015 at 9:00 PM, Henry Saputra
wrote:
> +1
>
> Would be good to have well documented release process with all the
> black magic scripts we have =)
> Thanks for dr
+1
Would be good to have well documented release process with all the
black magic scripts we have =)
Thanks for driving this, Robert.
- Henry
On Mon, Mar 30, 2015 at 11:15 AM, Robert Metzger wrote:
> Okay, I think we have reached consensus on this.
>
> I'll create a "RC0" non-voting, preview re
Okay, I think we have reached consensus on this.
I'll create a "RC0" non-voting, preview release candidate for 0.9.0-
milestone-1 on Thursday (April 2) this week so that we have version to
tests against.
Once all issues of RC0 have been resolved, we'll start voting in the week
of April 6. (The vo
+1 for 0.9.0-milestone-1
On Fri, Mar 27, 2015 at 3:52 PM, Kostas Tzoumas wrote:
> +1
>
> On Fri, Mar 27, 2015 at 3:44 PM, Aljoscha Krettek
> wrote:
>
> > +1 for 0.9.0-M1 (or milestone-1)
> > On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
> >
> > > On Friday, March 27, 2015, Maximilian Michels
+1
On Fri, Mar 27, 2015 at 3:44 PM, Aljoscha Krettek
wrote:
> +1 for 0.9.0-M1 (or milestone-1)
> On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
>
> > On Friday, March 27, 2015, Maximilian Michels wrote:
> >
> > > +1 for 0.9.0-milestone-1
> > >
> >
> > +1
> >
>
+1 for 0.9.0-M1 (or milestone-1)
On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
> On Friday, March 27, 2015, Maximilian Michels wrote:
>
> > +1 for 0.9.0-milestone-1
> >
>
> +1
>
On Friday, March 27, 2015, Maximilian Michels wrote:
> +1 for 0.9.0-milestone-1
>
+1
+1 for 0.9.0-milestone-1
+1 for 0.9.0-milestone-1
On Fri, Mar 27, 2015 at 12:50 PM, Márton Balassi
wrote:
> +1 for 0.9.0-milestone-1.
>
> On Fri, Mar 27, 2015 at 12:47 PM, Stephan Ewen wrote:
>
> > Okay, to how about we make this
> >
> >
> > org.apache.flink
> > flink-core
> > 0.9.0-milestone-1
> >
> >
> > I think it
+1 for 0.9.0-milestone-1.
On Fri, Mar 27, 2015 at 12:47 PM, Stephan Ewen wrote:
> Okay, to how about we make this
>
>
> org.apache.flink
> flink-core
> 0.9.0-milestone-1
>
>
> I think it is common that milestones have numbers. There is no such thing
> as "the" milestone.
>
>
>
> On Thu, Mar 26
Okay, to how about we make this
org.apache.flink
flink-core
0.9.0-milestone-1
I think it is common that milestones have numbers. There is no such thing
as "the" milestone.
On Thu, Mar 26, 2015 at 10:02 PM, Henry Saputra
wrote:
> Yeah, always prefer to get it with consensus that VOTE
>
> I
Yeah, always prefer to get it with consensus that VOTE
I am fine with either.
- Henry
On Thu, Mar 26, 2015 at 11:03 AM, Kostas Tzoumas wrote:
> The ASF press team wants to announce next week, so a 3-day vote right now
> might cancel the subject line of this thread :-)
>
> Perhaps we can reach c
On Thursday, March 26, 2015, Robert Metzger wrote:
> I'm fine with milestone.
> But I would really like to call it "milestone" instead of "M1" .. because I
> actually never though about that weird version name of Jetty ... I fear
> that our users would also be confused by this.
Same here.
I'm fine with milestone.
But I would really like to call it "milestone" instead of "M1" .. because I
actually never though about that weird version name of Jetty ... I fear
that our users would also be confused by this.
On Thu, Mar 26, 2015 at 7:03 PM, Kostas Tzoumas wrote:
> The ASF press team
The ASF press team wants to announce next week, so a 3-day vote right now
might cancel the subject line of this thread :-)
Perhaps we can reach consensus in the DISCUSS thread or have a 24-hour vote?
I agree with Stephan on 0.9.0.M1 (or 0.9.0-m1 or whatever), as it seems
that other open source pr
I think "Milestone" pretty much says that we have some crucial things in
there, but not all. "Beta" in comparison, has an "immature early version"
connotation.
We are, for example, using a milestone 1 version of Jetty for the Web
Frontend, so that is a pretty standard thing, in my opinion:
org.e
If we wanted to, we could still release a -milestone2 even with a
-milestone.
On Thu, Mar 26, 2015 at 3:44 PM, Robert Metzger wrote:
> Looks like we need to vote on 0.9-beta or 0.9-milestone.
>
> Can we find consensus whether to add a 1 after the name? -beta1 or
> -milestone1.
> Adding a 1 allow
Looks like we need to vote on 0.9-beta or 0.9-milestone.
Can we find consensus whether to add a 1 after the name? -beta1 or
-milestone1.
Adding a 1 allows us to create a second beta/milestone release.
I'm against adding a 1.
On Thu, Mar 26, 2015 at 3:40 PM, Ufuk Celebi wrote:
>
> On 26 Mar 201
On 26 Mar 2015, at 11:01, Robert Metzger wrote:
> Two weeks have passed since we've discussed the 0.9 release the last time.
>
> The ApacheCon is in 18 days from now.
> If we want, we can also release a "0.9.0-beta" release that contains known
> bugs, but allows our users to try out the new fea
@Timo: No feature freeze for this, yes.
On Thu, Mar 26, 2015 at 3:36 PM, Timo Walther wrote:
> +1 for a beta release. So there is no feature-freeze until the RC right?
>
>
>
> On 26.03.2015 15:32, Márton Balassi wrote:
>
>> +1 for the early release.
>>
>> I'd call it 0.9-milestone1.
>>
>> On Thu
+1 for a beta release. So there is no feature-freeze until the RC right?
On 26.03.2015 15:32, Márton Balassi wrote:
+1 for the early release.
I'd call it 0.9-milestone1.
On Thu, Mar 26, 2015 at 1:37 PM, Maximilian Michels wrote:
+1 for a beta release: 0.9-beta.
On Thu, Mar 26, 2015 at 12:
+1 for the early release.
I'd call it 0.9-milestone1.
On Thu, Mar 26, 2015 at 1:37 PM, Maximilian Michels wrote:
> +1 for a beta release: 0.9-beta.
>
> On Thu, Mar 26, 2015 at 12:09 PM, Paris Carbone wrote:
>
> > +1 for an early release. It will help unblock the samoa PR that has 0.9
> > depen
+1 for a beta release: 0.9-beta.
On Thu, Mar 26, 2015 at 12:09 PM, Paris Carbone wrote:
> +1 for an early release. It will help unblock the samoa PR that has 0.9
> dependencies.
>
> > On 26 Mar 2015, at 11:44, Kostas Tzoumas wrote:
> >
> > +1 for an early milestone release. Perhaps we can call
+1 for an early release. It will help unblock the samoa PR that has 0.9
dependencies.
> On 26 Mar 2015, at 11:44, Kostas Tzoumas wrote:
>
> +1 for an early milestone release. Perhaps we can call it 0.9-milestone or
> so?
>
> On Thu, Mar 26, 2015 at 11:01 AM, Robert Metzger
> wrote:
>
>> Two
+1 for an early milestone release. Perhaps we can call it 0.9-milestone or
so?
On Thu, Mar 26, 2015 at 11:01 AM, Robert Metzger
wrote:
> Two weeks have passed since we've discussed the 0.9 release the last time.
>
> The ApacheCon is in 18 days from now.
> If we want, we can also release a "0.9.0
Two weeks have passed since we've discussed the 0.9 release the last time.
The ApacheCon is in 18 days from now.
If we want, we can also release a "0.9.0-beta" release that contains known
bugs, but allows our users to try out the new features easily (because they
are part of a release). The vote f
I've reopened https://issues.apache.org/jira/browse/FLINK-1650 because the
issue is still occurring.
On Thu, Mar 12, 2015 at 7:05 PM, Ufuk Celebi wrote:
> On Thursday, March 12, 2015, Till Rohrmann
> wrote:
>
> > Have you run the 20 builds with the new shading code? With new shading
> the
> > T
On Thursday, March 12, 2015, Till Rohrmann wrote:
> Have you run the 20 builds with the new shading code? With new shading the
> TaskManagerFailsITCase should no longer fail. If it still does, then we
> have to look into it again.
No, rebased on Monday before shading. Let me rebase and rerun to
Have you run the 20 builds with the new shading code? With new shading the
TaskManagerFailsITCase should no longer fail. If it still does, then we
have to look into it again.
On Thu, Mar 12, 2015 at 2:01 PM, Stephan Ewen wrote:
> I am also big time skeptical.
>
> There are some remaining stabili
I am also big time skeptical.
There are some remaining stability issues with 0.9
- Apparently a bug in the task canceling
- Blocking Data Exchange is premature at this point
- TaskManager startup is not robust
- TaskManager / JobManager registration is not robust
- Streaming fault tolera
I would like to get the Expression API for Java in there, as well.
On Thu, Mar 12, 2015 at 11:59 AM, Ufuk Celebi wrote:
> On Thu, Mar 12, 2015 at 10:11 AM, Robert Metzger
> wrote:
>
>> So you're saying regarding the release you don't feel very confident that
>> we manage to fork off release-0.9
On Thu, Mar 12, 2015 at 10:11 AM, Robert Metzger
wrote:
> So you're saying regarding the release you don't feel very confident that
> we manage to fork off release-0.9 next week?
>
Yes. At the moment I would be uncomfortable with forking off.
Regarding the failing tests: I thought that so
So you're saying regarding the release you don't feel very confident that
we manage to fork off release-0.9 next week?
The exceptions in the jobmanager-stderr from the YARN tests is the
following (from #347.5 and #344.5):
07:46:00,598 WARN org.apache.flink.yarn.YarnTestBase
- LINE: Mar 12,
On Tue, Mar 10, 2015 at 11:20 AM, Robert Metzger
wrote:
> I think
> it is time to evaluate whether we are confident that the master is stable.
>
In the course of finishing up #471 [1] I ran 20 Travis builds over night,
of which 7 failed.
The (unexpected) failing test cases:
- ExternalSortITCas
I will follow up again with Sally this week if there any special
messaging or communications needed to do for the Apache Con from our
side.
- Henry
On Tue, Mar 10, 2015 at 3:20 AM, Robert Metzger wrote:
> Hey,
>
> whats the status on this? There is one week left until we are going to fork
> off
On the streaming side:
Must have:
* Tests for the fault tolerance (My first priority this week)
* Merging Gyula's recent windowing PR [1]
Really needed:
* Self-join for DataStreams (Gabor has a prototype, PR coming today) [1]
* ITCase tests for streaming examples (Peter & myself, review a
Hey,
whats the status on this? There is one week left until we are going to fork
off a branch for 0.9 .. if we stick to the suggested timeline.
The initial email said "I am very much in favor of doing this, under the
strong condition that we
are very confident that the master has grown to be stabl
+1 for Marton as a release manager. Thank you!
On Tue, Mar 3, 2015 at 7:56 PM, Henry Saputra
wrote:
> Ah, thanks Márton.
>
> So we are chartering to the similar concept of Spark RRD staging execution
> =P
> I suppose there will be a runtime configuration or hint to tell the
> Flink Job manager
Ah, thanks Márton.
So we are chartering to the similar concept of Spark RRD staging execution =P
I suppose there will be a runtime configuration or hint to tell the
Flink Job manager to indicate which execution is preferred?
- Henry
On Tue, Mar 3, 2015 at 2:09 AM, Márton Balassi wrote:
> Hi He
Hi Henry,
Batch mode is a new execution mode for batch Flink jobs where instead of
pipelining the whole execution the job is scheduled in stages, thus
materializing the intermediate result before continuing to the next
operators. For implications see [1].
[1] http://www.slideshare.net/KostasTzoum
HI Stephan,
What is "Batch mode" feature in the list?
- Henry
On Mon, Mar 2, 2015 at 5:03 AM, Stephan Ewen wrote:
> Hi all!
>
> ApacheCon is coming up and it is the 15th anniversary of the Apache
> Software Foundation.
>
> In the course of the conference, Apache would like to make a series of
>
Hey,
We have a nice list of new features - it definitely makes sense to have
that as a release. On my side I really want to have a first limited version
of streaming fault tolerance in it.
+1 for Robert's proposal for the deadlines.
I'm also volunteering for release manager.
Best,
Marton
On Mo
Hi all!
ApacheCon is coming up and it is the 15th anniversary of the Apache
Software Foundation.
In the course of the conference, Apache would like to make a series of
announcements. If we manage to make a release during (or shortly before)
ApacheCon, they will announce it through their channels.
44 matches
Mail list logo
