[jira] [Commented] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

2015-10-03 Thread Ismael Juma (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942247#comment-14942247
 ] 

Ismael Juma commented on KAFKA-2247:


Gwen, I think you meant to say that `kafka.utils.SystemTime` is a Scala object 
and can be accessed as if those methods were static. Both `kafka.utils.Time` 
and `o.a.k.common.utils.Time` are interfaces. Ideally we'd not refer to 
`SystemTime` directly in classes.

> Merge kafka.utils.Time and kafka.common.utils.Time
> --
>
> Key: KAFKA-2247
> URL: https://issues.apache.org/jira/browse/KAFKA-2247
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Aditya Auradkar
>Assignee: Aditya Auradkar
>Priority: Minor
>
> We currently have 2 different versions of Time in clients and core. These 
> need to be merged.
> It's worth noting that `kafka.utils.MockTime` includes a `scheduler` that is 
> used by some tests while `o.a.kafka.common.utils.Time` does not. We either 
> need to add this functionality or change the tests not to need it anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-2566) Improve Jenkins set-up

2015-10-03 Thread Ismael Juma (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942257#comment-14942257
 ] 

Ismael Juma commented on KAFKA-2566:


[~junrao], thanks for the correction, I had missed that we invoke gradle a 
second time with "-PscalaVersion=2.11". I will update the description to make 
this clear. I still think that it's better to use `testAll` because it will 
automatically do the right thing as we update the build. Having said that, this 
changes perhaps what we should do for the PR job, if we are already testing 
multiple Scala versions there. Maybe it should be:

1. kafka-trunk-jdk7: "Poll SCM" every hour, GRADLE_2_1, jdk-1.7u51, "./gradlew 
clean jarAll docsJarAll testAll"
2. kafka-trunk-jdk8: "Poll SCM" every hour, GRADLE_2_1, jdk1.8.0_45, "./gradlew 
clean jarAll docsJarAll testAll"
3. kafka-trunk-git-pr-jdk8: "Pull requests", GRADLE_2_1, jdk1.7.0_51, 
"./gradlew clean testAll"

Thoughts?

[~guozhang], for the Java 8 build, we need to merge Gwen's javadoc PR:
https://github.com/apache/kafka/pull/147

> Improve Jenkins set-up
> --
>
> Key: KAFKA-2566
> URL: https://issues.apache.org/jira/browse/KAFKA-2566
> Project: Kafka
>  Issue Type: Task
>Reporter: Ismael Juma
>
> There are currently two Jenkins jobs:
> https://builds.apache.org/job/Kafka-trunk
> https://builds.apache.org/job/kafka-trunk-git-pr
> They both run with Java 7 and execute the following gradle command:
> ./gradlew -PscalaVersion=2.10.1 test
> There are a few issues with this:
> * We don't test Java 8 even though that's the only stable release of the JDK 
> that still receives security fixes
> * We are testing with Scala 2.10.1 even though we should be testing with 
> Scala 2.10.5
> * We are not testing with Scala 2.11.x
> * We are not doing clean builds
> I suggest the following:
> 1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean test` 
> command.
> 2. Change the `Kafka-trunk` job to use the `./gradlew clean jarAll docsJarAll 
> testAll` command.
> 3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean jarAll 
> docsJarAll testAll`
> This is a compromise that doesn't slow down the PR job (which is executed 
> much more often) while still testing trunk in all of our supported JDK and 
> Scala versions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KAFKA-2566) Improve Jenkins set-up

2015-10-03 Thread Ismael Juma (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KAFKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ismael Juma updated KAFKA-2566:
---
Description: 
There are currently two Jenkins jobs:

https://builds.apache.org/job/Kafka-trunk
https://builds.apache.org/job/kafka-trunk-git-pr

They both run with Java 7 and execute the following gradle commands:

./gradlew -PscalaVersion=2.10.1 test
./gradlew -PscalaVersion=2.11 test

There are a few issues with this:
* We don't test Java 8 even though that's the only stable release of the JDK 
that still receives security fixes
* We are testing with Scala 2.10.1 even though we should be testing with Scala 
2.10.5
* We are not doing clean builds
* The versions tested are defined in Jenkins instead of the build

I suggest the following:

1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean testAll` 
command.
2. Change the `Kafka-trunk` job to use the `./gradlew clean jarAll docsJarAll 
testAll` command.
3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean jarAll 
docsJarAll testAll`

We only test the PR job against Java 7 as it's executed much more often than 
the trunk job.

  was:
There are currently two Jenkins jobs:

https://builds.apache.org/job/Kafka-trunk
https://builds.apache.org/job/kafka-trunk-git-pr

They both run with Java 7 and execute the following gradle command:

./gradlew -PscalaVersion=2.10.1 test

There are a few issues with this:
* We don't test Java 8 even though that's the only stable release of the JDK 
that still receives security fixes
* We are testing with Scala 2.10.1 even though we should be testing with Scala 
2.10.5
* We are not testing with Scala 2.11.x
* We are not doing clean builds

I suggest the following:

1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean test` 
command.
2. Change the `Kafka-trunk` job to use the `./gradlew clean jarAll docsJarAll 
testAll` command.
3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean jarAll 
docsJarAll testAll`

This is a compromise that doesn't slow down the PR job (which is executed much 
more often) while still testing trunk in all of our supported JDK and Scala 
versions.


> Improve Jenkins set-up
> --
>
> Key: KAFKA-2566
> URL: https://issues.apache.org/jira/browse/KAFKA-2566
> Project: Kafka
>  Issue Type: Task
>Reporter: Ismael Juma
>
> There are currently two Jenkins jobs:
> https://builds.apache.org/job/Kafka-trunk
> https://builds.apache.org/job/kafka-trunk-git-pr
> They both run with Java 7 and execute the following gradle commands:
> ./gradlew -PscalaVersion=2.10.1 test
> ./gradlew -PscalaVersion=2.11 test
> There are a few issues with this:
> * We don't test Java 8 even though that's the only stable release of the JDK 
> that still receives security fixes
> * We are testing with Scala 2.10.1 even though we should be testing with 
> Scala 2.10.5
> * We are not doing clean builds
> * The versions tested are defined in Jenkins instead of the build
> I suggest the following:
> 1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean testAll` 
> command.
> 2. Change the `Kafka-trunk` job to use the `./gradlew clean jarAll docsJarAll 
> testAll` command.
> 3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean jarAll 
> docsJarAll testAll`
> We only test the PR job against Java 7 as it's executed much more often than 
> the trunk job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-2425) Migrate website from SVN to Git

2015-10-03 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942297#comment-14942297
 ] 

ASF GitHub Bot commented on KAFKA-2425:
---

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/171


> Migrate website from SVN to Git 
> 
>
> Key: KAFKA-2425
> URL: https://issues.apache.org/jira/browse/KAFKA-2425
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Manikumar Reddy
>
> The preference is to share the same Git repo for the code and website as per 
> discussion in the mailing list:
> http://search-hadoop.com/m/uyzND1Dux842dm7vg2
> Useful reference:
> https://blogs.apache.org/infra/entry/git_based_websites_available



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

2015-10-03 Thread Gwen Shapira (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942301#comment-14942301
 ] 

Gwen Shapira commented on KAFKA-2247:
-

I have absolutely no idea what I was trying to say back in June, sorry :)

> Merge kafka.utils.Time and kafka.common.utils.Time
> --
>
> Key: KAFKA-2247
> URL: https://issues.apache.org/jira/browse/KAFKA-2247
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Aditya Auradkar
>Assignee: Aditya Auradkar
>Priority: Minor
>
> We currently have 2 different versions of Time in clients and core. These 
> need to be merged.
> It's worth noting that `kafka.utils.MockTime` includes a `scheduler` that is 
> used by some tests while `o.a.kafka.common.utils.Time` does not. We either 
> need to add this functionality or change the tests not to need it anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KAFKA-2425) Migrate website from SVN to Git

2015-10-03 Thread Gwen Shapira (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gwen Shapira resolved KAFKA-2425.
-
   Resolution: Fixed
Fix Version/s: 0.9.0.0

Issue resolved by pull request 171
[https://github.com/apache/kafka/pull/171]

> Migrate website from SVN to Git 
> 
>
> Key: KAFKA-2425
> URL: https://issues.apache.org/jira/browse/KAFKA-2425
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Manikumar Reddy
> Fix For: 0.9.0.0
>
>
> The preference is to share the same Git repo for the code and website as per 
> discussion in the mailing list:
> http://search-hadoop.com/m/uyzND1Dux842dm7vg2
> Useful reference:
> https://blogs.apache.org/infra/entry/git_based_websites_available



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

2015-10-03 Thread Ismael Juma (JIRA) 
Ismael Juma created KAFKA-2608:
--

 Summary: Recommend kafka_2.11 for 0.9.0.0 on the website
 Key: KAFKA-2608
 URL: https://issues.apache.org/jira/browse/KAFKA-2608
 Project: Kafka
  Issue Type: Task
  Components: website
Reporter: Ismael Juma
 Fix For: 0.9.0.0


Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
anymore. We should recommend the Scala 2.11 version on the website.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

2015-10-03 Thread Ismael Juma (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KAFKA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ismael Juma updated KAFKA-2608:
---
Description: 
Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
anymore. We should recommend the Scala 2.11 version on the website:

http://kafka.apache.org/downloads.html

  was:Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
anymore. We should recommend the Scala 2.11 version on the website.


> Recommend kafka_2.11 for 0.9.0.0 on the website
> ---
>
> Key: KAFKA-2608
> URL: https://issues.apache.org/jira/browse/KAFKA-2608
> Project: Kafka
>  Issue Type: Task
>  Components: website
>Reporter: Ismael Juma
> Fix For: 0.9.0.0
>
>
> Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
> anymore. We should recommend the Scala 2.11 version on the website:
> http://kafka.apache.org/downloads.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-2566) Improve Jenkins set-up

2015-10-03 Thread Ismael Juma (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942347#comment-14942347
 ] 

Ismael Juma commented on KAFKA-2566:


[~guozhang], I filed KAFKA-2608 to recommend the Scala 2.11 version on the 
downloads page of the website. We list all the versions, so the only thing to 
change is the recommendation that follows the list:

http://kafka.apache.org/downloads.html

> Improve Jenkins set-up
> --
>
> Key: KAFKA-2566
> URL: https://issues.apache.org/jira/browse/KAFKA-2566
> Project: Kafka
>  Issue Type: Task
>Reporter: Ismael Juma
>
> There are currently two Jenkins jobs:
> https://builds.apache.org/job/Kafka-trunk
> https://builds.apache.org/job/kafka-trunk-git-pr
> They both run with Java 7 and execute the following gradle commands:
> ./gradlew -PscalaVersion=2.10.1 test
> ./gradlew -PscalaVersion=2.11 test
> There are a few issues with this:
> * We don't test Java 8 even though that's the only stable release of the JDK 
> that still receives security fixes
> * We are testing with Scala 2.10.1 even though we should be testing with 
> Scala 2.10.5
> * We are not doing clean builds
> * The versions tested are defined in Jenkins instead of the build
> I suggest the following:
> 1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean testAll` 
> command.
> 2. Change the `Kafka-trunk` job to use the `./gradlew clean jarAll docsJarAll 
> testAll` command.
> 3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean jarAll 
> docsJarAll testAll`
> We only test the PR job against Java 7 as it's executed much more often than 
> the trunk job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

2015-10-03 Thread Ismael Juma (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KAFKA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ismael Juma updated KAFKA-2608:
---
Description: 
Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
anymore. We should recommend the Scala 2.11 version of 0.9.0.0 on the website:

http://kafka.apache.org/downloads.html

  was:
Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
anymore. We should recommend the Scala 2.11 version on the website:

http://kafka.apache.org/downloads.html


> Recommend kafka_2.11 for 0.9.0.0 on the website
> ---
>
> Key: KAFKA-2608
> URL: https://issues.apache.org/jira/browse/KAFKA-2608
> Project: Kafka
>  Issue Type: Task
>  Components: website
>Reporter: Ismael Juma
> Fix For: 0.9.0.0
>
>
> Scala 2.11 has been out for 17 months and Scala 2.10 is not being updated 
> anymore. We should recommend the Scala 2.11 version of 0.9.0.0 on the website:
> http://kafka.apache.org/downloads.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: Kafka-trunk #657

2015-10-03 Thread Apache Jenkins Server 
See 

Changes:

[cshapi] KAFKA-2425; Copy latest docs to kafka repo docs/ directory

--
[...truncated 1715 lines...]
kafka.log.LogCleanerIntegrationTest > cleanerTest[0] PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicAlreadyMarkedAsDeleted PASSED

kafka.integration.PlaintextTopicMetadataTest > 
testAliveBrokersListWithNoTopicsAfterABrokerShutdown PASSED

kafka.common.ConfigTest > testInvalidGroupIds PASSED

kafka.common.ConfigTest > testInvalidClientIds PASSED

kafka.controller.ControllerFailoverTest > testMetadataUpdate PASSED

kafka.network.SocketServerTest > testMaxConnectionsPerIp PASSED

kafka.network.SocketServerTest > simpleRequest PASSED

kafka.network.SocketServerTest > testSessionPrincipal PASSED

kafka.network.SocketServerTest > testSocketsCloseOnShutdown PASSED

kafka.network.SocketServerTest > testMaxConnectionsPerIPOverrides PASSED

kafka.api.ConsumerTest > testListTopics PASSED

kafka.network.SocketServerTest > testSSLSocketServer PASSED

kafka.network.SocketServerTest > tooBigRequestIsRejected PASSED

kafka.integration.UncleanLeaderElectionTest > testUncleanLeaderElectionEnabled 
PASSED

kafka.admin.AddPartitionsTest > testReplicaPlacement PASSED

kafka.log.LogTest > testCorruptLog PASSED

kafka.integration.FetcherTest > testFetcher PASSED

kafka.zk.ZKEphemeralTest > testZkWatchedEphemeralRecursive PASSED

kafka.zk.ZKEphemeralTest > testOverlappingSessions PASSED

kafka.zk.ZKEphemeralTest > testEphemeralNodeCleanup PASSED

kafka.admin.DeleteTopicTest > testPartitionReassignmentDuringDeleteTopic PASSED

kafka.zk.ZKEphemeralTest > testZkWatchedEphemeral PASSED

kafka.zk.ZKEphemeralTest > testSameSession PASSED

kafka.api.ConsumerTest > testExpandingTopicSubscriptions PASSED

kafka.log.LogTest > testLogRecoversToCorrectOffset PASSED

kafka.log.LogTest > testReopenThenTruncate PASSED

kafka.log.LogTest > testParseTopicPartitionNameForMissingPartition PASSED

kafka.log.LogTest > testParseTopicPartitionNameForEmptyName PASSED

kafka.log.LogTest > testOpenDeletesObsoleteFiles PASSED

kafka.log.LogTest > testSizeBasedLogRoll PASSED

kafka.log.LogTest > testTimeBasedLogRollJitter PASSED

kafka.log.LogTest > testParseTopicPartitionName PASSED

kafka.log.LogTest > testTruncateTo PASSED

kafka.log.LogTest > testCleanShutdownFile PASSED

kafka.admin.DeleteTopicTest > testDeleteNonExistingTopic PASSED

kafka.api.ConsumerTest > testPatternUnsubscription PASSED

kafka.api.ProducerFailureHandlingTest > testCannotSendToInternalTopic PASSED

kafka.admin.DeleteTopicTest > testRecreateTopicAfterDeletion PASSED

kafka.api.ProducerFailureHandlingTest > testTooLargeRecordWithAckOne PASSED

kafka.api.ConsumerBounceTest > testConsumptionWithBrokerFailures PASSED

kafka.utils.ByteBoundedBlockingQueueTest > testByteBoundedBlockingQueue PASSED

kafka.api.ConsumerTest > testGroupConsumption PASSED

kafka.integration.UncleanLeaderElectionTest > 
testCleanLeaderElectionDisabledByTopicOverride PASSED

kafka.admin.DeleteTopicTest > testAddPartitionDuringDeleteTopic PASSED

kafka.api.ProducerFailureHandlingTest > testWrongBrokerList PASSED

kafka.api.ConsumerTest > testPartitionsFor PASSED

kafka.log.LogCleanerIntegrationTest > cleanerTest[1] PASSED

kafka.api.ProducerFailureHandlingTest > testNotEnoughReplicas PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicWithAllAliveReplicas PASSED

kafka.api.ConsumerTest > testAutoCommitOnRebalance PASSED

kafka.api.ProducerFailureHandlingTest > testNonExistentTopic PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicDuringAddPartition PASSED

kafka.api.ConsumerTest > testSimpleConsumption PASSED

kafka.api.ProducerFailureHandlingTest > testInvalidPartition PASSED

kafka.api.ProducerFailureHandlingTest > testSendAfterClosed PASSED

kafka.api.ConsumerTest > testPartitionPauseAndResume PASSED

kafka.integration.UncleanLeaderElectionTest > testUncleanLeaderElectionDisabled 
PASSED

kafka.integration.UncleanLeaderElectionTest > 
testUncleanLeaderElectionInvalidTopicOverride PASSED

kafka.api.ProducerFailureHandlingTest > testTooLargeRecordWithAckZero PASSED

kafka.integration.RollingBounceTest > testRollingBounce PASSED

kafka.common.TopicTest > testInvalidTopicNames PASSED

kafka.common.TopicTest > testTopicHasCollision PASSED

kafka.common.TopicTest > testTopicHasCollisionChars PASSED

kafka.log.LogCleanerIntegrationTest > cleanerTest[2] PASSED

kafka.api.ProducerFailureHandlingTest > 
testNotEnoughReplicasAfterBrokerShutdown PASSED

kafka.utils.UtilsTest > testAbs PASSED

kafka.utils.UtilsTest > testReplaceSuffix PASSED

kafka.utils.UtilsTest > testDoublyLinkedList PASSED

kafka.utils.UtilsTest > testCircularIterator PASSED

kafka.utils.UtilsTest > testReadBytes PASSED

kafka.utils.UtilsTest > testCsvList PASSED

kafka.utils.UtilsTest > testReadInt PASSED

kafka.utils.UtilsTest > testCsvMap PASSED

kafka.utils.UtilsTest > testInLock PASSED

kafka.utils.UtilsTest > testSwallow PASSED

[ANNOUCE] Apache Kafka 0.8.2.2 Released

2015-10-03 Thread Jun Rao 
The Apache Kafka community is pleased to announce the release for Apache Kafka 
0.8.2.2.

The 0.8.2.2 release fixes 2 critical issues in 0.8.2.1.

All of the changes in this release can be found: 
https://archive.apache.org/dist/kafka/0.8.2.2/RELEASE_NOTES.html

Apache Kafka is high-throughput, publish-subscribe messaging system rethought 
of as a distributed commit log.

** Fast => A single Kafka broker can handle hundreds of megabytes of reads and
writes per second from thousands of clients.

** Scalable => Kafka is designed to allow a single cluster to serve as the 
central data backbone
for a large organization. It can be elastically and transparently expanded 
without downtime.
Data streams are partitioned and spread over a cluster of machines to allow 
data streams
larger than the capability of any single machine and to allow clusters of 
co-ordinated consumers.

** Durable => Messages are persisted on disk and replicated within the cluster 
to prevent
data loss. Each broker can handle terabytes of messages without performance 
impact.

** Distributed by Design => Kafka has a modern cluster-centric design that 
offers
strong durability and fault-tolerance guarantees.

You can download the source release from
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2/kafka-0.8.2.2-src.tgz

and binary releases from
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2/kafka_2.9.1-0.8.2.2.tgz
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2/kafka_2.9.2-0.8.2.2.tgz
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2/kafka_2.10-0.8.2.2.tgz
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2/kafka_2.11-0.8.2.2.tgz

We will update the download link in our website shortly.

We welcome your help and feedback. For more information on how to
report problems, and to get involved, visit the project website at 
http://kafka.apache.org/

Thanks,

Jun

[GitHub] kafka pull request: KAFKA-2425; Copy latest docs to kafka repo doc...

2015-10-03 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/171


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: KAFKA-2364 migrate docs from SVN to git

2015-10-03 Thread Gwen Shapira 
OK, PR 171 is in, and the latest version of the docs is now in docs/
directory of trunk!

Next steps:
1. Follow up with infra on our github site
2. Update the docs contribution guide
3. Update the release guide (since we are releasing docs as part of our
release artifacts)

Mani, I assume you are on those?
Anything I'm missing?

Gwen

On Fri, Oct 2, 2015 at 11:28 PM, Manikumar Reddy 
wrote:

> Thanks Gwen,  i will
> update the next steps.
> On Oct 3, 2015 1:08 AM, "Gwen Shapira"  wrote:
>
> > Hi,
> >
> > I created asf-git under
> https://git-wip-us.apache.org/repos/asf/kafka-site
> > .
> > git and pushed our existing docs in there.
> > What do we need to do to get infra to show this in our website?
> >
> > Next steps:
> > 1) Minor fix to PR 171
> > 2) Merge PR 171
> > 3) Get Apache to show our git site
> > 4) Update wiki with "contributing to docs" process
> >
> > Gwen
> >
> >
> >
> > On Tue, Sep 15, 2015 at 8:40 AM, Manikumar Reddy 
> > wrote:
> >
> > > Hi Gwen,
> > >
> > > We need to create new branch named "asf-site"  in new git
> repository[1].
> > > This is requirement from Apache Infra
> > > for git based websites [2].  After creating new branch, we will the
> copy
> > > the existing to svn repo contents to
> > > new branch.
> > >
> > >
> > > 1. https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > 2. https://issues.apache.org/jira/browse/INFRA-10143
> > >
> > >
> > > Kumar
> > >
> > > On Tue, Sep 15, 2015 at 2:19 AM, Gwen Shapira 
> wrote:
> > >
> > > > Hi Manikumar,
> > > >
> > > > Sorry for huge delay!
> > > >
> > > > 1) This looks good, I'll get it in
> > > >
> > > > 2) I'm confused - do we need a new branch or a new repository? it
> looks
> > > > like you already got a new repository, so why do we need a branch as
> > > well?
> > > >
> > > >
> > > >
> > > > On Wed, Sep 2, 2015 at 8:11 AM, Manikumar Reddy <
> ku...@nmsworks.co.in>
> > > > wrote:
> > > >
> > > > > Jun/Gwen/Guozhang,
> > > > >Need your help to complete this.
> > > > >
> > > > >   (1) Copy latest docs to kafka repo:
> > > > > https://github.com/apache/kafka/pull/171
> > > > >
> > > > >   (2) svn site repo -> git site repo migration : need committer
> help
> > to
> > > > > create a branch "asf-site".
> > > > >
> > > > >new git site repo :
> > > > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > >
> > > > > Kumar
> > > > >
> > > > > On Wed, Aug 26, 2015 at 7:43 PM, Manikumar Reddy <
> > ku...@nmsworks.co.in
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Guozhang,
> > > > > >
> > > > > >   Our plan is to follow Gwen's suggested approach and migrate the
> > > > > existing
> > > > > > svn site repo to new git repo.
> > > > > >
> > > > > >   (1) Gwen's suggestion will help to us maintain latest docs in
> > Kafka
> > > > > repo
> > > > > > itself.  We periodically need to copy these latest docs to site
> > > repo. I
> > > > > > will submit patch for this.
> > > > > >
> > > > > >   (2)  svn repo -> git repo  migration will help us to integrate
> > site
> > > > > repo
> > > > > > to git tooling/github. It will be easy to maintain the site repo
> > and
> > > > > > changes.  So we have created new git repo for docs and need
> > committer
> > > > > help
> > > > > > to create a branch "asf-site".
> > > > > >
> > > > > >new git repo:
> > > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > > >
> > > > > >   Hope this clears the confusion.
> > > > > >
> > > > > > Kumar
> > > > > > I thought Gwen's suggestion was to us a separate folder in the
> same
> > > > repo
> > > > > > for docs instead of a separate branch, Gwen can correct me if I
> was
> > > > > wrong?
> > > > > >
> > > > > > Guozhang
> > > > > >
> > > > > > On Mon, Aug 24, 2015 at 10:31 AM, Manikumar Reddy <
> > > > ku...@nmsworks.co.in>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > >Infra team created git repo for kafka site docs.
> > > > > > >
> > > > > > >Gwen/Guozhang,
> > > > > > >Need your help to create a branch "asf-site" and copy
> the
> > > > > exiting
> > > > > > > svn contents to that branch.
> > > > > > >
> > > > > > > git repo:
> > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/INFRA-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709630#comment-14709630
> > > > > > >
> > > > > > > Kumar
> > > > > > >
> > > > > > > On Fri, Aug 21, 2015 at 6:16 PM, Ismael Juma <
> ism...@juma.me.uk>
> > > > > wrote:
> > > > > > >
> > > > > > > > My preference would be to do `2` because it reduces the
> number
> > of
> > > > > tools
> > > > > > > we
> > > > > > > > need to know. If we want to clone the repo for the generated
> > > site,
> > > > we
> > > > > > can
> > > > > > > > use the same tools as we do for the code repo and we can
> watch
> > > for
> > > > > > > changes
> > > > > > > > on GitHub, etc.
> > > > >

Re: KAFKA-2364 migrate docs from SVN to git

2015-10-03 Thread Manikumar Reddy 
Thanks gwen..  I am working on remaining steps. I will update you on the
progress.

Regards,
Mani

On Sat, Oct 3, 2015 at 7:27 PM, Gwen Shapira  wrote:

> OK, PR 171 is in, and the latest version of the docs is now in docs/
> directory of trunk!
>
> Next steps:
> 1. Follow up with infra on our github site
> 2. Update the docs contribution guide
> 3. Update the release guide (since we are releasing docs as part of our
> release artifacts)
>
> Mani, I assume you are on those?
> Anything I'm missing?
>
> Gwen
>
> On Fri, Oct 2, 2015 at 11:28 PM, Manikumar Reddy 
> wrote:
>
> > Thanks Gwen,  i will
> > update the next steps.
> > On Oct 3, 2015 1:08 AM, "Gwen Shapira"  wrote:
> >
> > > Hi,
> > >
> > > I created asf-git under
> > https://git-wip-us.apache.org/repos/asf/kafka-site
> > > .
> > > git and pushed our existing docs in there.
> > > What do we need to do to get infra to show this in our website?
> > >
> > > Next steps:
> > > 1) Minor fix to PR 171
> > > 2) Merge PR 171
> > > 3) Get Apache to show our git site
> > > 4) Update wiki with "contributing to docs" process
> > >
> > > Gwen
> > >
> > >
> > >
> > > On Tue, Sep 15, 2015 at 8:40 AM, Manikumar Reddy  >
> > > wrote:
> > >
> > > > Hi Gwen,
> > > >
> > > > We need to create new branch named "asf-site"  in new git
> > repository[1].
> > > > This is requirement from Apache Infra
> > > > for git based websites [2].  After creating new branch, we will the
> > copy
> > > > the existing to svn repo contents to
> > > > new branch.
> > > >
> > > >
> > > > 1. https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > 2. https://issues.apache.org/jira/browse/INFRA-10143
> > > >
> > > >
> > > > Kumar
> > > >
> > > > On Tue, Sep 15, 2015 at 2:19 AM, Gwen Shapira 
> > wrote:
> > > >
> > > > > Hi Manikumar,
> > > > >
> > > > > Sorry for huge delay!
> > > > >
> > > > > 1) This looks good, I'll get it in
> > > > >
> > > > > 2) I'm confused - do we need a new branch or a new repository? it
> > looks
> > > > > like you already got a new repository, so why do we need a branch
> as
> > > > well?
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Sep 2, 2015 at 8:11 AM, Manikumar Reddy <
> > ku...@nmsworks.co.in>
> > > > > wrote:
> > > > >
> > > > > > Jun/Gwen/Guozhang,
> > > > > >Need your help to complete this.
> > > > > >
> > > > > >   (1) Copy latest docs to kafka repo:
> > > > > > https://github.com/apache/kafka/pull/171
> > > > > >
> > > > > >   (2) svn site repo -> git site repo migration : need committer
> > help
> > > to
> > > > > > create a branch "asf-site".
> > > > > >
> > > > > >new git site repo :
> > > > > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > > >
> > > > > > Kumar
> > > > > >
> > > > > > On Wed, Aug 26, 2015 at 7:43 PM, Manikumar Reddy <
> > > ku...@nmsworks.co.in
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Guozhang,
> > > > > > >
> > > > > > >   Our plan is to follow Gwen's suggested approach and migrate
> the
> > > > > > existing
> > > > > > > svn site repo to new git repo.
> > > > > > >
> > > > > > >   (1) Gwen's suggestion will help to us maintain latest docs in
> > > Kafka
> > > > > > repo
> > > > > > > itself.  We periodically need to copy these latest docs to site
> > > > repo. I
> > > > > > > will submit patch for this.
> > > > > > >
> > > > > > >   (2)  svn repo -> git repo  migration will help us to
> integrate
> > > site
> > > > > > repo
> > > > > > > to git tooling/github. It will be easy to maintain the site
> repo
> > > and
> > > > > > > changes.  So we have created new git repo for docs and need
> > > committer
> > > > > > help
> > > > > > > to create a branch "asf-site".
> > > > > > >
> > > > > > >new git repo:
> > > > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > > > >
> > > > > > >   Hope this clears the confusion.
> > > > > > >
> > > > > > > Kumar
> > > > > > > I thought Gwen's suggestion was to us a separate folder in the
> > same
> > > > > repo
> > > > > > > for docs instead of a separate branch, Gwen can correct me if I
> > was
> > > > > > wrong?
> > > > > > >
> > > > > > > Guozhang
> > > > > > >
> > > > > > > On Mon, Aug 24, 2015 at 10:31 AM, Manikumar Reddy <
> > > > > ku...@nmsworks.co.in>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > >Infra team created git repo for kafka site docs.
> > > > > > > >
> > > > > > > >Gwen/Guozhang,
> > > > > > > >Need your help to create a branch "asf-site" and copy
> > the
> > > > > > exiting
> > > > > > > > svn contents to that branch.
> > > > > > > >
> > > > > > > > git repo:
> > > > https://git-wip-us.apache.org/repos/asf/kafka-site.git
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/INFRA-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709630#comment-14709630
> > > > > > > >
> > > > > > > > Kumar
> > > > > > > >
> > > > > > >

Re: KAFKA-2364 migrate docs from SVN to git

2015-10-03 Thread Ismael Juma 
On 3 Oct 2015 16:44, "Gwen Shapira"  wrote:

> OK, PR 171 is in, and the latest version of the docs is now in docs/
> directory of trunk!

Awesome. :)

> Next steps:
> 1. Follow up with infra on our github site

Follow-up issue filed:
https://issues.apache.org/jira/browse/INFRA-10539. Geoffrey
Corey assigned the issue to himself.

> 2. Update the docs contribution guide
> 3. Update the release guide (since we are releasing docs as part of our
> release artifacts)
>
> Mani, I assume you are on those?
> Anything I'm missing?

I can't think of anything else at this point.

Ismael