I just created the 0.8.2 branch and bumped up the version in trunk to 0.8.3.
Thanks,
Jun
On Mon, Sep 29, 2014 at 11:43 AM, Sriram Subramanian
srsubraman...@linkedin.com.invalid wrote:
+1 on 0.8.3-SNAPSHOT.
On 9/29/14 11:40 AM, Neha Narkhede neha.narkh...@gmail.com wrote:
2) change trunk
Thanks Jun! I created 0.8.3 in JIRA too just now.
- Joestein
On Tue, Sep 30, 2014 at 11:15 AM, Jun Rao jun...@gmail.com wrote:
I just created the 0.8.2 branch and bumped up the version in trunk to
0.8.3.
Thanks,
Jun
On Mon, Sep 29, 2014 at 11:43 AM, Sriram Subramanian
Thanks for making a pass of the open issues, Jun. I agree that it's not
worth blocking 0.8.2 more and we can push auto preferred replica election
to 0.8.3. I'm a +1 on cutting the branch.
On Sun, Sep 28, 2014 at 6:03 PM, Jun Rao jun...@gmail.com wrote:
Hi, everyone,
I made another pass of the
Agreed, I am +1 on creating the branch.
Three thoughts on the branching
1) we should change the version to be 0.8.2.0 (from 0.8.2-SNAPSHOT) on the
0.8.2 branch after the branch is created.
2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever).
3) after we branch I will prepare a
2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever).
I'd vote for changing trunk to 0.8.3-SNAPSHOT. I imagine it will be useful
to have 0.8.3 released with some features and bug fixes that we are pushing
out of 0.8.2. It will be a while before we get to a point where we can
release
+1 on 0.8.3-SNAPSHOT.
On 9/29/14 11:40 AM, Neha Narkhede neha.narkh...@gmail.com wrote:
2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever).
I'd vote for changing trunk to 0.8.3-SNAPSHOT. I imagine it will be useful
to have 0.8.3 released with some features and bug fixes that we
Harsha,
We are shooting to cut the 0.8.2 branch this month.
Thanks,
Jun
On Tue, Sep 16, 2014 at 11:25 AM, Harsha m...@harsha.io wrote:
Hi All,
Do we have any ballpark date on the release of 0.8.1.2 or 0.8.2.
Thanks,
Harsha
On Thu, Sep 11, 2014, at 03:53 PM, Jay Kreps wrote:
I
Hi All,
Do we have any ballpark date on the release of 0.8.1.2 or 0.8.2.
Thanks,
Harsha
On Thu, Sep 11, 2014, at 03:53 PM, Jay Kreps wrote:
I agree that a beta for 0.8.2 would be useful. It would also be good
to get it in production at LinkedIn before the final version.
Sorry about
Thanks a lot for going through the unresolved tickets, Guozhang!
On Thu, Sep 4, 2014 at 8:19 AM, Guozhang Wang wangg...@gmail.com wrote:
Just made a pass over the unresolved tickets tagged for 0.8.2, I think many
of them can be pushed to 0.8.3 / 0.9.
On Wed, Sep 3, 2014 at 8:05 PM, Jonathan
Joe,
Thanks for starting the discussion.
(1) I made a pass of the open jiras for 0.8.2 and marked a few of them as
blockers for now. There are currently 6 blockers. Ideally, we want to get
all those fixed before cutting the 0.8.2 branch. The rest of the jiras
don't really have to be fixed in
Just made a pass over the unresolved tickets tagged for 0.8.2, I think many
of them can be pushed to 0.8.3 / 0.9.
On Wed, Sep 3, 2014 at 8:05 PM, Jonathan Weeks jonathanbwe...@gmail.com
wrote:
+1 on a 0.8.1.2 release as described.
I manually applied patches to cobble together a working
Hey, I wanted to take a quick pulse to see if we are getting closer to a
branch for 0.8.2.
1) There still seems to be a lot of open issues
https://issues.apache.org/jira/browse/KAFKA/fixforversion/12326167/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
and our 30 day
+1 on a 0.8.1.2 release as described.
I manually applied patches to cobble together a working gradle build for kafka
for scala 2.11, but would really appreciate an official release — i.e. 0.8.1.2,
as we also have other dependent libraries we use as well (e.g. akka-kafka) that
would be much
13 matches
Mail list logo
