[jira] [Resolved] (KAFKA-17193) Pin external GitHub actions to specific git hash
[ https://issues.apache.org/jira/browse/KAFKA-17193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-17193. Fix Version/s: 4.0.0 Resolution: Fixed > Pin external GitHub actions to specific git hash > > > Key: KAFKA-17193 > URL: https://issues.apache.org/jira/browse/KAFKA-17193 > Project: Kafka > Issue Type: Task >Reporter: Mickael Maison >Assignee: Mickael Maison >Priority: Major > Fix For: 4.0.0 > > > As per [https://infra.apache.org/github-actions-policy.html] we must pin any > GitHub action that is not from the apache/*, github/* and actions/* > namespaces to a specific git hash. > We are currently using actions from aquasecurity and docker and these are not > pinned to specific git hashes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-17193) Pin external GitHub actions to specific git hash
Mickael Maison created KAFKA-17193: -- Summary: Pin external GitHub actions to specific git hash Key: KAFKA-17193 URL: https://issues.apache.org/jira/browse/KAFKA-17193 Project: Kafka Issue Type: Task Reporter: Mickael Maison As per [https://infra.apache.org/github-actions-policy.html] we must pin any GitHub action that is not from the apache/*, github/* and actions/* namespaces to a specific git hash. We are currently using actions from aquasecurity and docker and these are not pinned to specific git hashes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] ISSUE-1020 Print git log in validate patch [kafka-merge-queue-sandbox]
mumrah merged PR #24: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/24 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] ISSUE-1020 Print git log in validate patch [kafka-merge-queue-sandbox]
mumrah opened a new pull request, #24: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/24 This will let us verify the merge group behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Development with Git Worktree
Greg, Thanks for making the change and sharing the benefit with the overall group. Ismael On Mon, Oct 23, 2023 at 10:03 AM Greg Harris wrote: > Hey Kafka Developers, > > This is a small announcement that the gradle build now supports the > git-worktree subcommand [1] on the 3.4, 3.5, 3.6, and trunk branches > [2]. > > If you've needed to check out multiple copies of Kafka concurrently, > you previously needed to manage multiple full clones of the > repository. Now you can add a worktree that shares a common git > repository, transparently sharing all commits and branches with a > single local repository. > > With this, you can run tests in the background for one or more > branches while actively working on a different branch. If you have > open PRs right now, you can take advantage of this change by merging > or rebasing with trunk. > > [1] https://git-scm.com/docs/git-worktree > [2] https://issues.apache.org/jira/browse/KAFKA-14767 > > Thanks, > Greg >
Development with Git Worktree
Hey Kafka Developers, This is a small announcement that the gradle build now supports the git-worktree subcommand [1] on the 3.4, 3.5, 3.6, and trunk branches [2]. If you've needed to check out multiple copies of Kafka concurrently, you previously needed to manage multiple full clones of the repository. Now you can add a worktree that shares a common git repository, transparently sharing all commits and branches with a single local repository. With this, you can run tests in the background for one or more branches while actively working on a different branch. If you have open PRs right now, you can take advantage of this change by merging or rebasing with trunk. [1] https://git-scm.com/docs/git-worktree [2] https://issues.apache.org/jira/browse/KAFKA-14767 Thanks, Greg
[jira] [Created] (KAFKA-15201) When git fails, script goes into a loop
Divij Vaidya created KAFKA-15201: Summary: When git fails, script goes into a loop Key: KAFKA-15201 URL: https://issues.apache.org/jira/browse/KAFKA-15201 Project: Kafka Issue Type: Sub-task Reporter: Divij Vaidya When the git push to remote fails (let's say with unauthenticated exception), then the script runs into a loop. It should not retry and fail gracefully instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-14767) Gradle build fails with missing commitId after git gc
Greg Harris created KAFKA-14767:
---
Summary: Gradle build fails with missing commitId after git gc
Key: KAFKA-14767
URL: https://issues.apache.org/jira/browse/KAFKA-14767
Project: Kafka
Issue Type: Bug
Components: build
Reporter: Greg Harris
Reproduction steps:
1. `git gc`
2. `./gradlew jar`
Expected behavior: build completes successfully (or shows other build errors)
Actual behavior:
{noformat}
Task failed with an exception.
---
* What went wrong:
A problem was found with the configuration of task ':storage:createVersionFile'
(type 'DefaultTask').
- Property 'commitId' doesn't have a configured value.
Reason: This property isn't marked as optional and no value has been
configured.
Possible solutions:
1. Assign a value to 'commitId'.
2. Mark property 'commitId' as optional.
Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#value_not_set
for more details about this problem.{noformat}
This appears to be due to the fact that the build.gradle determineCommitId()
function is unable to read the git commit hash for the current HEAD. This
appears to happen after a `git gc` takes place, which causes the
`.git/refs/heads/*` files to be moved to `.git/packed-refs`.
The determineCommitId() should be patched to also try reading from the
packed-refs to determine the commit hash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [kafka-site] Venom-git opened a new pull request #395: Update powered-by.html
Venom-git opened a new pull request #395: URL: https://github.com/apache/kafka-site/pull/395 Please help to update our organization as well , as we are using #Apache Kafka in our environment.  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (KAFKA-10463) the necessary utilities in Dockerfile should include git
[ https://issues.apache.org/jira/browse/KAFKA-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10463. Fix Version/s: 2.7.0 Resolution: Fixed > the necessary utilities in Dockerfile should include git > > > Key: KAFKA-10463 > URL: https://issues.apache.org/jira/browse/KAFKA-10463 > Project: Kafka > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 2.7.0 > > > the default image of Dockerfile is openjdk:8 and it pre-installed git so it > is fine that necessary utilities does not include git. However, the later > version of openjdk image does not include git by default and error message > "git: command not found" ensues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KAFKA-10463) the necessary utilities in Dockerfile should include git
Chia-Ping Tsai created KAFKA-10463: -- Summary: the necessary utilities in Dockerfile should include git Key: KAFKA-10463 URL: https://issues.apache.org/jira/browse/KAFKA-10463 Project: Kafka Issue Type: Bug Reporter: Chia-Ping Tsai Assignee: Chia-Ping Tsai the default image of Dockerfile is openjdk:8 and it pre-installed git so it is fine that necessary utilities does not include git. However, the later version of openjdk image does not include git by default and error message "git: command not found" ensues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Please Add Jira and Git Users
Hi David, First, you'll need to set up an account with Jira, then share you Jira user-id on the list here and we can add you to the contributors list. You'll also want to read https://kafka.apache.org/contributing. Thanks for your interest in Apache Kafka. -Bill On Thu, Sep 26, 2019 at 5:42 PM David Swift wrote: > Please add southcoastdavidsw...@gmail.com to your git contributors and > Jira users or let me know if I need to do something else first. > > Thanks! > -David Swift > Cloudera
Please Add Jira and Git Users
Please add southcoastdavidsw...@gmail.com to your git contributors and Jira users or let me know if I need to do something else first. Thanks! -David Swift Cloudera
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Thanks Daniel and Christopher! My bad for missing the header. :) Ismael On Fri, Dec 7, 2018, 9:31 AM Daniel Gruno On 12/7/18 6:28 PM, Ismael Juma wrote: > > Hi Daniel, > > > > We moved to Gitbox a while back for kafka and kafka-site. Which > > repository is still using git-wip-us.apache.org > > <http://git-wip-us.apache.org>? > > > > Ismael > > Hi Ismael, > You do not have any repositories that need to be moved, Kafka can safely > disregard the email, as stated in the header :) >
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
On Fri, Dec 7, 2018 at 12:29 PM Ismael Juma wrote: > > Hi Daniel, > > We moved to Gitbox a while back for kafka and kafka-site. Which repository is > still using git-wip-us.apache.org? > > Ismael None of yours. The message was sent to every PMC. I believe https://git1-us-west.apache.org/repos/asf has a list of affected repos still on git-wip. > > On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno wrote: >> >> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >> >> Hello Apache projects, >> >> I am writing to you because you may have git repositories on the >> git-wip-us server, which is slated to be decommissioned in the coming >> months. All repositories will be moved to the new gitbox service which >> includes direct write access on github as well as the standard ASF >> commit access via gitbox.apache.org. >> >> ## Why this move? ## >> The move comes as a result of retiring the git-wip service, as the >> hardware it runs on is longing for retirement. In lieu of this, we >> have decided to consolidate the two services (git-wip and gitbox), to >> ease the management of our repository systems and future-proof the >> underlying hardware. The move is fully automated, and ideally, nothing >> will change in your workflow other than added features and access to >> GitHub. >> >> ## Timeframe for relocation ## >> Initially, we are asking that projects voluntarily request to move >> their repositories to gitbox, hence this email. The voluntary >> timeframe is between now and January 9th 2019, during which projects >> are free to either move over to gitbox or stay put on git-wip. After >> this phase, we will be requiring the remaining projects to move within >> one month, after which we will move the remaining projects over. >> >> To have your project moved in this initial phase, you will need: >> >> - Consensus in the project (documented via the mailing list) >> - File a JIRA ticket with INFRA to voluntarily move your project repos >>over to gitbox (as stated, this is highly automated and will take >>between a minute and an hour, depending on the size and number of >>your repositories) >> >> To sum up the preliminary timeline; >> >> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >>relocation >> - January 9th -> February 6th: Mandated (coordinated) relocation >> - February 7th: All remaining repositories are mass migrated. >> >> This timeline may change to accommodate various scenarios. >> >> ## Using GitHub with ASF repositories ## >> When your project has moved, you are free to use either the ASF >> repository system (gitbox.apache.org) OR GitHub for your development >> and code pushes. To be able to use GitHub, please follow the primer >> at: https://reference.apache.org/committer/github >> >> >> We appreciate your understanding of this issue, and hope that your >> project can coordinate voluntarily moving your repositories in a >> timely manner. >> >> All settings, such as commit mail targets, issue linking, PR >> notification schemes etc will automatically be migrated to gitbox as >> well. >> >> With regards, Daniel on behalf of ASF Infra. >> >> PS:For inquiries, please reply to us...@infra.apache.org, not your >> project's dev list :-). >> >>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
On 12/7/18 6:28 PM, Ismael Juma wrote: Hi Daniel, We moved to Gitbox a while back for kafka and kafka-site. Which repository is still using git-wip-us.apache.org <http://git-wip-us.apache.org>? Ismael Hi Ismael, You do not have any repositories that need to be moved, Kafka can safely disregard the email, as stated in the header :)
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hi Daniel, We moved to Gitbox a while back for kafka and kafka-site. Which repository is still using git-wip-us.apache.org? Ismael On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno wrote: > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE > DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] > > Hello Apache projects, > > I am writing to you because you may have git repositories on the > git-wip-us server, which is slated to be decommissioned in the coming > months. All repositories will be moved to the new gitbox service which > includes direct write access on github as well as the standard ASF > commit access via gitbox.apache.org. > > ## Why this move? ## > The move comes as a result of retiring the git-wip service, as the > hardware it runs on is longing for retirement. In lieu of this, we > have decided to consolidate the two services (git-wip and gitbox), to > ease the management of our repository systems and future-proof the > underlying hardware. The move is fully automated, and ideally, nothing > will change in your workflow other than added features and access to > GitHub. > > ## Timeframe for relocation ## > Initially, we are asking that projects voluntarily request to move > their repositories to gitbox, hence this email. The voluntary > timeframe is between now and January 9th 2019, during which projects > are free to either move over to gitbox or stay put on git-wip. After > this phase, we will be requiring the remaining projects to move within > one month, after which we will move the remaining projects over. > > To have your project moved in this initial phase, you will need: > > - Consensus in the project (documented via the mailing list) > - File a JIRA ticket with INFRA to voluntarily move your project repos >over to gitbox (as stated, this is highly automated and will take >between a minute and an hour, depending on the size and number of >your repositories) > > To sum up the preliminary timeline; > > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >relocation > - January 9th -> February 6th: Mandated (coordinated) relocation > - February 7th: All remaining repositories are mass migrated. > > This timeline may change to accommodate various scenarios. > > ## Using GitHub with ASF repositories ## > When your project has moved, you are free to use either the ASF > repository system (gitbox.apache.org) OR GitHub for your development > and code pushes. To be able to use GitHub, please follow the primer > at: https://reference.apache.org/committer/github > > > We appreciate your understanding of this issue, and hope that your > project can coordinate voluntarily moving your repositories in a > timely manner. > > All settings, such as commit mail targets, issue linking, PR > notification schemes etc will automatically be migrated to gitbox as > well. > > With regards, Daniel on behalf of ASF Infra. > > PS:For inquiries, please reply to us...@infra.apache.org, not your > project's dev list :-). > > >
[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-).
Re: 0.11 git tags
That was it, thanks! But I still don't understand how I had tags for 1.0.0, but not 0.11.0.0. On 10 November 2017 at 13:10, Kamal wrote: > Try, `git fetch upstream --tags` > > On Fri, Nov 10, 2017 at 6:32 PM, Mickael Maison > wrote: > > > Have you tried: > > git fetch --tags ? > > > > On Fri, Nov 10, 2017 at 12:54 PM, Tom Bentley > > wrote: > > > Not when I run `git tag` locally though. > > > > > > On 10 November 2017 at 12:44, Ismael Juma wrote: > > > > > >> They seem to be there: > > >> > > >> https://github.com/apache/kafka/tree/0.11.0.0 > > >> https://github.com/apache/kafka/tree/0.11.0.1 > > >> > > >> Ismael > > >> > > >> On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley > > >> wrote: > > >> > > >> > I just noticed that although every other release is tagged in git > > there > > >> are > > >> > no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please > can > > >> they > > >> > be tagged retrospectively? > > >> > > > >> > Cheers, > > >> > > > >> > Tom > > >> > > > >> > > >
Re: 0.11 git tags
Try, `git fetch upstream --tags` On Fri, Nov 10, 2017 at 6:32 PM, Mickael Maison wrote: > Have you tried: > git fetch --tags ? > > On Fri, Nov 10, 2017 at 12:54 PM, Tom Bentley > wrote: > > Not when I run `git tag` locally though. > > > > On 10 November 2017 at 12:44, Ismael Juma wrote: > > > >> They seem to be there: > >> > >> https://github.com/apache/kafka/tree/0.11.0.0 > >> https://github.com/apache/kafka/tree/0.11.0.1 > >> > >> Ismael > >> > >> On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley > >> wrote: > >> > >> > I just noticed that although every other release is tagged in git > there > >> are > >> > no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can > >> they > >> > be tagged retrospectively? > >> > > >> > Cheers, > >> > > >> > Tom > >> > > >> >
Re: 0.11 git tags
Have you tried: git fetch --tags ? On Fri, Nov 10, 2017 at 12:54 PM, Tom Bentley wrote: > Not when I run `git tag` locally though. > > On 10 November 2017 at 12:44, Ismael Juma wrote: > >> They seem to be there: >> >> https://github.com/apache/kafka/tree/0.11.0.0 >> https://github.com/apache/kafka/tree/0.11.0.1 >> >> Ismael >> >> On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley >> wrote: >> >> > I just noticed that although every other release is tagged in git there >> are >> > no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can >> they >> > be tagged retrospectively? >> > >> > Cheers, >> > >> > Tom >> > >>
Re: 0.11 git tags
Not when I run `git tag` locally though. On 10 November 2017 at 12:44, Ismael Juma wrote: > They seem to be there: > > https://github.com/apache/kafka/tree/0.11.0.0 > https://github.com/apache/kafka/tree/0.11.0.1 > > Ismael > > On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley > wrote: > > > I just noticed that although every other release is tagged in git there > are > > no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can > they > > be tagged retrospectively? > > > > Cheers, > > > > Tom > > >
Re: 0.11 git tags
They seem to be there: https://github.com/apache/kafka/tree/0.11.0.0 https://github.com/apache/kafka/tree/0.11.0.1 Ismael On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley wrote: > I just noticed that although every other release is tagged in git there are > no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can they > be tagged retrospectively? > > Cheers, > > Tom >
0.11 git tags
I just noticed that although every other release is tagged in git there are no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can they be tagged retrospectively? Cheers, Tom
[jira] [Commented] (KAFKA-4519) Delete old unused branches in git repo
[
https://issues.apache.org/jira/browse/KAFKA-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15788849#comment-15788849
]
Ewen Cheslack-Postava commented on KAFKA-4519:
--
There are probably more of these we should retire. Besides feature branches
like {{consumer_redesign}} and {{transactional_messaging}}, there are a ton of
version branches that we should retire, e.g. {{0.7.0}}, {{0.7.1}}, {{0.7.2}},
etc. In fact, except for 2 or 3 branches, almost all branches should probably
be retired as they are no longer active. We've recently started to follow a bit
more strict policy re: tagging RCs and releases; we might want to also come up
with a policy for retiring & tagging the final version of branches.
> Delete old unused branches in git repo
> --
>
> Key: KAFKA-4519
> URL: https://issues.apache.org/jira/browse/KAFKA-4519
> Project: Kafka
> Issue Type: Task
>Reporter: Jeff Widman
> Priority: Trivial
>
> Delete these old git branches, as they're quite outdated and not relevant for
> various version branches:
> * consumer_redesign
> * transactional_messaging
> * 0.8.0-beta1-candidate1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KAFKA-4519) Delete old unused branches in git repo
Jeff Widman created KAFKA-4519: -- Summary: Delete old unused branches in git repo Key: KAFKA-4519 URL: https://issues.apache.org/jira/browse/KAFKA-4519 Project: Kafka Issue Type: Task Reporter: Jeff Widman Priority: Trivial Delete these old git branches, as they're quite outdated and not relevant for various version branches: * consumer_redesign * transactional_messaging * 0.8.0-beta1-candidate1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] kafka pull request #1922: HOTFIX: remove git conflicts
Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/1922 --- 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. ---
[GitHub] kafka pull request #1922: HOTFIX: remove git conflicts
GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1922 HOTFIX: remove git conflicts You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KHotfix-streams-html Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1922.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1922 commit b5aa255de60589ebce0c8a1aaa4f828bf1ae9bfe Author: Guozhang Wang Date: 2016-09-28T00:54:42Z remove git info --- 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. ---
[GitHub] kafka pull request: Git ignore idea's specific /out/ and .DS_Store...
Github user SinghAsDev closed the pull request at: https://github.com/apache/kafka/pull/1274 --- 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. ---
[GitHub] kafka pull request: Git ignore idea's specific /out/ and .DS_Store...
GitHub user SinghAsDev opened a pull request:
https://github.com/apache/kafka/pull/1274
Git ignore idea's specific /out/ and .DS_Store.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SinghAsDev/kafka MinorGitignore
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1274.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1274
commit 2a7f7a9e59bf9815f74de7d2d2771860b5e43ffb
Author: Ashish Singh
Date: 2016-04-27T17:08:19Z
Git ignore idea's specific /out/ and .DS_Store.
---
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.
---
[jira] [Commented] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999055#comment-14999055
]
ASF GitHub Bot commented on KAFKA-2797:
---
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/485
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9.0.0
>Reporter: Flavio Junqueira
>Assignee: Ewen Cheslack-Postava
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> When running gradle on the RC0 for 0.9, we get an error because the build
> expects to find a git repo here:
> {noformat}
> line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
> {noformat}
> and we get this error message:
> {noformat}
> FAILURE: Build failed with an exception.
> * Where:
> Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
> * What went wrong:
> A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> > repository not found: kafka-0.9.0.0-src
> {noformat}
> The definitions for rat make sense when working on a git branch, but not for
> the release artifact. One way around this is to disable rat by commenting out
> the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2797:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 485
[https://github.com/apache/kafka/pull/485]
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9.0.0
>Reporter: Flavio Junqueira
>Assignee: Ewen Cheslack-Postava
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> When running gradle on the RC0 for 0.9, we get an error because the build
> expects to find a git repo here:
> {noformat}
> line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
> {noformat}
> and we get this error message:
> {noformat}
> FAILURE: Build failed with an exception.
> * Where:
> Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
> * What went wrong:
> A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> > repository not found: kafka-0.9.0.0-src
> {noformat}
> The definitions for rat make sense when working on a git branch, but not for
> the release artifact. One way around this is to disable rat by commenting out
> the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] kafka pull request: KAFKA-2797: Only run rat when in the .git repo...
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/485 --- 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. ---
[jira] [Assigned] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava reassigned KAFKA-2797:
Assignee: Ewen Cheslack-Postava
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9.0.0
>Reporter: Flavio Junqueira
>Assignee: Ewen Cheslack-Postava
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> When running gradle on the RC0 for 0.9, we get an error because the build
> expects to find a git repo here:
> {noformat}
> line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
> {noformat}
> and we get this error message:
> {noformat}
> FAILURE: Build failed with an exception.
> * Where:
> Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
> * What went wrong:
> A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> > repository not found: kafka-0.9.0.0-src
> {noformat}
> The definitions for rat make sense when working on a git branch, but not for
> the release artifact. One way around this is to disable rat by commenting out
> the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2797:
-
Reviewer: Gwen Shapira
Status: Patch Available (was: Open)
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9.0.0
>Reporter: Flavio Junqueira
>Assignee: Ewen Cheslack-Postava
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> When running gradle on the RC0 for 0.9, we get an error because the build
> expects to find a git repo here:
> {noformat}
> line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
> {noformat}
> and we get this error message:
> {noformat}
> FAILURE: Build failed with an exception.
> * Where:
> Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
> * What went wrong:
> A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> > repository not found: kafka-0.9.0.0-src
> {noformat}
> The definitions for rat make sense when working on a git branch, but not for
> the release artifact. One way around this is to disable rat by commenting out
> the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998996#comment-14998996
]
ASF GitHub Bot commented on KAFKA-2797:
---
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/485
KAFKA-2797: Only run rat when in the .git repository since it require s the
.gitignore to generate the list of files to ignore
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka
kafka-2797-disable-rat-when-git-missing
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/485.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #485
commit 79c6cac66644b458eff8141e13dacd0b859f5c3c
Author: Ewen Cheslack-Postava
Date: 2015-11-10T17:33:45Z
KAFKA-2797: Only run rat when in the .git repository since it requires the
.gitignore to generate the list of files to ignore
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9.0.0
>Reporter: Flavio Junqueira
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> When running gradle on the RC0 for 0.9, we get an error because the build
> expects to find a git repo here:
> {noformat}
> line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
> {noformat}
> and we get this error message:
> {noformat}
> FAILURE: Build failed with an exception.
> * Where:
> Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
> * What went wrong:
> A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> > repository not found: kafka-0.9.0.0-src
> {noformat}
> The definitions for rat make sense when working on a git branch, but not for
> the release artifact. One way around this is to disable rat by commenting out
> the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] kafka pull request: KAFKA-2797: Only run rat when in the .git repo...
GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/485 KAFKA-2797: Only run rat when in the .git repository since it require s the .gitignore to generate the list of files to ignore You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-2797-disable-rat-when-git-missing Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/485.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #485 commit 79c6cac66644b458eff8141e13dacd0b859f5c3c Author: Ewen Cheslack-Postava Date: 2015-11-10T17:33:45Z KAFKA-2797: Only run rat when in the .git repository since it requires the .gitignore to generate the list of files to ignore --- 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. ---
[jira] [Created] (KAFKA-2797) Release artifact expects a git repository for the release audit tool (RAT)
Flavio Junqueira created KAFKA-2797:
---
Summary: Release artifact expects a git repository for the release
audit tool (RAT)
Key: KAFKA-2797
URL: https://issues.apache.org/jira/browse/KAFKA-2797
Project: Kafka
Issue Type: Bug
Components: build
Affects Versions: 0.9.0.0
Reporter: Flavio Junqueira
Priority: Blocker
Fix For: 0.9.0.0
When running gradle on the RC0 for 0.9, we get an error because the build
expects to find a git repo here:
{noformat}
line 68 of build.gradle: def repo = Grgit.open(project.file('.'))
{noformat}
and we get this error message:
{noformat}
FAILURE: Build failed with an exception.
* Where:
Build file 'kafka-0.9.0.0-src/build.gradle' line: 68
* What went wrong:
A problem occurred evaluating root project 'kafka-0.9.0.0-src'.
> repository not found: kafka-0.9.0.0-src
{noformat}
The definitions for rat make sense when working on a git branch, but not for
the release artifact. One way around this is to disable rat by commenting out
the corresponding lines, but that isn't what the README file says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira resolved KAFKA-2612. - Resolution: Fixed > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma >Assignee: Flavio Junqueira > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944990#comment-14944990 ] Flavio Junqueira edited comment on KAFKA-2612 at 10/6/15 1:07 PM: -- (I said 15 previously but set to 14, so I'm just correcting the value with this edit) OK, to play nicely, I've set for the git-pr job the number of days to keep to 14 and max number of builds to 100. It sounds better to set a threshold, even if large. was (Author: fpj): OK, to play nicely, I've set for the git-pr job the number of days to keep to 15 and max number of builds to 100. It sounds better to set a threshold, even if large. > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma >Assignee: Flavio Junqueira > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944997#comment-14944997 ] Ismael Juma commented on KAFKA-2612: Thanks! > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma >Assignee: Flavio Junqueira > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944990#comment-14944990 ] Flavio Junqueira commented on KAFKA-2612: - OK, to play nicely, I've set for the git-pr job the number of days to keep to 15 and max number of builds to 100. It sounds better to set a threshold, even if large. > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma >Assignee: Flavio Junqueira > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira reassigned KAFKA-2612: --- Assignee: Flavio Junqueira > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma >Assignee: Flavio Junqueira > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: KAFKA-2364 migrate docs from SVN to git
Comments below. On Tue, Oct 6, 2015 at 1:39 PM, Manikumar Reddy wrote: > On Tue, Oct 6, 2015 at 1:34 PM, Ismael Juma wrote: > > > Thanks Mani. Regarding the release process changes, a couple of comments: > > > > 1. Under "bug-fix releases", you mention "major release directory" a > couple > > of times. Is this right? > > > > hmm..not sure. For bug fix releases like 0.8.2.X, we are referring its > major release docs (0.8.2 release). In that sense, i used "major release > directory". I may be wrong. > I see what you mean. I actually don't know what is the current process in that regard, so I'll leave it to Gwen. :) > 2. "Auto-generate the configuration docs" is mentioned a couple of times, > > would it be worth including the command used to do this as well? > > > > Yes, updated the wiki page. > Thanks. Ismael
[jira] [Commented] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944978#comment-14944978 ] Ismael Juma commented on KAFKA-2612: That sounds good to me [~fpj]. > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944966#comment-14944966 ] Flavio Junqueira commented on KAFKA-2612: - There is also the option of "Days to keep builds" rather than "Max # of builds to keep". I think we should switch to number of days, something like 21 days, sounds good? [~ijuma] > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: KAFKA-2364 migrate docs from SVN to git
On Tue, Oct 6, 2015 at 1:34 PM, Ismael Juma wrote: > Thanks Mani. Regarding the release process changes, a couple of comments: > > 1. Under "bug-fix releases", you mention "major release directory" a couple > of times. Is this right? > hmm..not sure. For bug fix releases like 0.8.2.X, we are referring its major release docs (0.8.2 release). In that sense, i used "major release directory". I may be wrong. > 2. "Auto-generate the configuration docs" is mentioned a couple of times, > would it be worth including the command used to do this as well? > Yes, updated the wiki page. > > Ismael > > On Tue, Oct 6, 2015 at 3:37 AM, Manikumar Reddy > wrote: > > > Hi Gwen, > > > > Kafka site is updated to use Git repo. We can now push any site changes > to > > git web site repo. > > > > 1) "Contributing website changes" wiki page: > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes > > > > 2) "Website update process" added to Release Process wiki page: > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Process > > > > 3) PR to update contributing.html: > > https://github.com/apache/kafka-site/pull/1 > > > > > > Regards > > Mani > > > > On Sat, Oct 3, 2015 at 9:28 PM, Ismael Juma wrote: > > > > > 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 > > > > > >
[jira] [Updated] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2612: --- Component/s: build > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement > Components: build >Reporter: Ismael Juma > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
[ https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944832#comment-14944832 ] Ismael Juma commented on KAFKA-2612: [~fpj] or [~guozhang], can any of you help? > Increase the number of retained builds for kafka-trunk-git-pr-jdk7 > -- > > Key: KAFKA-2612 > URL: https://issues.apache.org/jira/browse/KAFKA-2612 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma > > It seems like we only retain 12 and this means that we get a 404 for PRs that > are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-2612) Increase the number of retained builds for kafka-trunk-git-pr-jdk7
Ismael Juma created KAFKA-2612: -- Summary: Increase the number of retained builds for kafka-trunk-git-pr-jdk7 Key: KAFKA-2612 URL: https://issues.apache.org/jira/browse/KAFKA-2612 Project: Kafka Issue Type: Improvement Reporter: Ismael Juma It seems like we only retain 12 and this means that we get a 404 for PRs that are still active. We need a much higher number, maybe 50? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: KAFKA-2364 migrate docs from SVN to git
Thanks Mani. Regarding the release process changes, a couple of comments: 1. Under "bug-fix releases", you mention "major release directory" a couple of times. Is this right? 2. "Auto-generate the configuration docs" is mentioned a couple of times, would it be worth including the command used to do this as well? Ismael On Tue, Oct 6, 2015 at 3:37 AM, Manikumar Reddy wrote: > Hi Gwen, > > Kafka site is updated to use Git repo. We can now push any site changes to > git web site repo. > > 1) "Contributing website changes" wiki page: > > https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes > > 2) "Website update process" added to Release Process wiki page: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Process > > 3) PR to update contributing.html: > https://github.com/apache/kafka-site/pull/1 > > > Regards > Mani > > On Sat, Oct 3, 2015 at 9:28 PM, Ismael Juma wrote: > > > 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 > > >
Re: KAFKA-2364 migrate docs from SVN to git
Hi Gwen, Kafka site is updated to use Git repo. We can now push any site changes to git web site repo. 1) "Contributing website changes" wiki page: https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes 2) "Website update process" added to Release Process wiki page: https://cwiki.apache.org/confluence/display/KAFKA/Release+Process 3) PR to update contributing.html: https://github.com/apache/kafka-site/pull/1 Regards Mani On Sat, Oct 3, 2015 at 9:28 PM, Ismael Juma wrote: > 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 >
Re: KAFKA-2364 migrate docs from SVN to git
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
Re: KAFKA-2364 migrate docs from SVN to git
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 >
Re: KAFKA-2364 migrate docs from SVN to git
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 > &
[jira] [Resolved] (KAFKA-2425) Migrate website from SVN to Git
[ 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] [Commented] (KAFKA-2425) Migrate website from SVN to Git
[ 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)
Re: KAFKA-2364 migrate docs from SVN to git
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 > > > 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.apach
Re: KAFKA-2364 migrate docs from SVN to git
On Fri, Oct 2, 2015 at 9:36 PM, Ashish wrote: > > Does this mean doc patches would be welcome only for a production > release? else you would need a diff branch for accepting docs for > trunk features/patches which don't get reflected on the website. > Yes, you will contribute changes to the relevant branch of the code repository and this will be pushed to the website Git repo as needed. Does Infra supports git based sites? > Yes. Ismael
Re: KAFKA-2364 migrate docs from SVN to git
Thanks Gwen. Comments below. On Fri, Oct 2, 2015 at 8:38 PM, Gwen Shapira wrote: > 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? > You need to reopen the ticket that was closed due to inactivity and tell them that the branch was created: https://issues.apache.org/jira/browse/INFRA-10143 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 > The contributing to website instructions are on the website at the moment, so we need to update that too: http://kafka.apache.org/contributing.html And we also need to update the release instructions. Ismael
Re: KAFKA-2364 migrate docs from SVN to git
On Fri, Oct 2, 2015 at 12:38 PM, 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 Does this mean doc patches would be welcome only for a production release? else you would need a diff branch for accepting docs for trunk features/patches which don't get reflected on the website. Does Infra supports git based sites?
Re: KAFKA-2364 migrate docs from SVN to git
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 > > 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 > > > > 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 > > > 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 > >
Re: KAFKA-2364 migrate docs from SVN to git
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 > 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 > > 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 > > 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. > > > > > > > > > > Ismael > > > > > > > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy < > > ku...@nmsworks.co.in > > > > > > > > > wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > > > > > > > 1. Gwen's suggestion + existing svn repo > > > > > > 2. Gwen's suggestion + new git repo for docs > > > > > > > > > > > > kumar > > > > > > > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > > > > ku...@nmsworks.co.in> > > > > > > wrote: > > > > > > > > > > > > > Also can we migrate svn
Re: KAFKA-2364 migrate docs from SVN to git
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 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 > 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 > > 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 > 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. > > > > > > > > Ismael > > > > > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy < > ku...@nmsworks.co.in > > > > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > > > > > 1. Gwen's suggestion + existing svn repo > > > > > 2. Gwen's suggestion + new git repo for docs > > > > > > > > > > kumar > > > > > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > > > ku...@nmsworks.co.in> > > > > > wrote: > > > > > > > > > > > Also can we migrate svn repo to git repo? This will help us to > > fix > > > > > > occasional doc changes/bug fixes through github PR. > > > > > > > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang < > wangg...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > >> Gwen: I remembered it wrong. We would not need another round of > > > > voting. > > > > > >> > > > > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira < > g...@confluent.io> > > > > > wrote: > > > > > >> > > > > > >> > Looking back at this thread, the +1 mention "same repo", so > I'm > > > not > > > > > >> sure a > > > > > >> > new vote is required. > > > > > >> > > > > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang
Re: KAFKA-2364 migrate docs from SVN to git
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 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 > 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 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. > > > > > > Ismael > > > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy > > > > wrote: > > > > > > > Hi All, > > > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > > > 1. Gwen's suggestion + existing svn repo > > > > 2. Gwen's suggestion + new git repo for docs > > > > > > > > kumar > > > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > > ku...@nmsworks.co.in> > > > > wrote: > > > > > > > > > Also can we migrate svn repo to git repo? This will help us to > fix > > > > > occasional doc changes/bug fixes through github PR. > > > > > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > > > > > wrote: > > > > > > > > > >> Gwen: I remembered it wrong. We would not need another round of > > > voting. > > > > >> > > > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > > > > wrote: > > > > >> > > > > >> > Looking back at this thread, the +1 mention "same repo", so I'm > > not > > > > >> sure a > > > > >> > new vote is required. > > > > >> > > > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang < > > wangg...@gmail.com> > > > > >> wrote: > > > > >> > > > > > >> > > So I think we have two different approaches here. The original > > > > >> proposal > > > > >> > > from Aseem is to move website from SVN to a separate Git repo, > > and > > > > >> hence > > > > >> > > have separate commits on code / doc changes. For that we have > > > > >> accumulated > > > > >> > > enough binging +1s to move on; Gwen's proposal is to move > > website > > > > into > > > > >> > the > > > > >> > > same repo under a different folder. If people feel they prefer > > > this > > > > >> over > > > > >> > > the previous approach I would like to call for anot
[jira] [Commented] (KAFKA-2425) Migrate website from SVN to Git
[
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716460#comment-14716460
]
ASF GitHub Bot commented on KAFKA-2425:
---
GitHub user omkreddy reopened a pull request:
https://github.com/apache/kafka/pull/171
KAFKA-2425; Copy latest docs to kafka repo docs/ directory
This PR copies the latest kafka docs to kafka repo docs directory. Here I
have copied 0.8.3/ directory contents from svn website repo to kafka/docs
repository.
Some questions: This PR contains generated javadocs also. Do we need to
copy javadocs here?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka
KAFKA-2425-MOVE-DOCS-TO-KAFKA-REPO
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/171.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #171
commit e4e0fe30b8f2a966a81b1225038fe6fad9e303d4
Author: Manikumar reddy O
Date: 2015-08-27T09:44:26Z
KAFKA-2425; Copy latest docs to kafka repo docs/ directory
commit 2ace9b365565470d6f7f0b79ea5fa78fbb2f5029
Author: Manikumar reddy O
Date: 2015-08-27T10:38:56Z
KAFKA-2425; exclude docs from rat check
> 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716459#comment-14716459 ] ASF GitHub Bot commented on KAFKA-2425: --- Github user omkreddy 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-2425) Migrate website from SVN to Git
[
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716436#comment-14716436
]
ASF GitHub Bot commented on KAFKA-2425:
---
GitHub user omkreddy opened a pull request:
https://github.com/apache/kafka/pull/171
KAFKA-2425; Copy latest docs to kafka repo docs/ directory
This PR copies the latest kafka docs to kafka repo docs directory. Here I
have copied 0.8.3/ directory contents from svn website repo to kafka/docs
repository.
Some questions: This PR contains generated javadocs also. Do we need to
copy javadocs here?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka
KAFKA-2425-MOVE-DOCS-TO-KAFKA-REPO
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/171.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #171
commit e4e0fe30b8f2a966a81b1225038fe6fad9e303d4
Author: Manikumar reddy O
Date: 2015-08-27T09:44:26Z
KAFKA-2425; Copy latest docs to kafka repo docs/ directory
> 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)
Re: KAFKA-2364 migrate docs from SVN to git
Hi Kumar, One note: we need to update the documentation on how to submit changes to the website here: http://kafka.apache.org/contributing.html Ismael On Wed, Aug 26, 2015 at 3:13 PM, Manikumar Reddy 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 > 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 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. > > > > > > Ismael > > > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy > > > > wrote: > > > > > > > Hi All, > > > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > > > 1. Gwen's suggestion + existing svn repo > > > > 2. Gwen's suggestion + new git repo for docs > > > > > > > > kumar > > > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > > ku...@nmsworks.co.in> > > > > wrote: > > > > > > > > > Also can we migrate svn repo to git repo? This will help us to > fix > > > > > occasional doc changes/bug fixes through github PR. > > > > > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > > > > > wrote: > > > > > > > > > >> Gwen: I remembered it wrong. We would not need another round of > > > voting. > > > > >> > > > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > > > > wrote: > > > > >> > > > > >> > Looking back at this thread, the +1 mention "same repo", so I'm > > not > > > > >> sure a > > > > >> > new vote is required. > > > > >> > > > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang < > > wangg...@gmail.com> > > > > >> wrote: > > > > >> > > > > > >> > > So I think we have two different approaches here. The original > > > > >> proposal > > > > >> > > from Aseem is to move website from SVN to a separate Git repo, > > and > > > > >> hence > > > > >> > > have separate commits on code / doc changes. For that we have > > > > >> accumulated > > > > >> > > enough binging +1s to move on; Gwen's proposal is to move > > website > > > > into > > > > >> > the > > > > >> > > same repo under a different folder. If people feel they prefer > > > this > > > > >> over > > > > >> > > the previous approach I would like to call for another round > of > > > > >> voting. > > > > >> > > > > > > >> > > Guozhang > > > > >> > >
Re: KAFKA-2364 migrate docs from SVN to git
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 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 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. > > > > Ismael > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy > > wrote: > > > > > Hi All, > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > 1. Gwen's suggestion + existing svn repo > > > 2. Gwen's suggestion + new git repo for docs > > > > > > kumar > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > ku...@nmsworks.co.in> > > > wrote: > > > > > > > Also can we migrate svn repo to git repo? This will help us to fix > > > > occasional doc changes/bug fixes through github PR. > > > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > > > wrote: > > > > > > > >> Gwen: I remembered it wrong. We would not need another round of > > voting. > > > >> > > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > > > wrote: > > > >> > > > >> > Looking back at this thread, the +1 mention "same repo", so I'm > not > > > >> sure a > > > >> > new vote is required. > > > >> > > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang < > wangg...@gmail.com> > > > >> wrote: > > > >> > > > > >> > > So I think we have two different approaches here. The original > > > >> proposal > > > >> > > from Aseem is to move website from SVN to a separate Git repo, > and > > > >> hence > > > >> > > have separate commits on code / doc changes. For that we have > > > >> accumulated > > > >> > > enough binging +1s to move on; Gwen's proposal is to move > website > > > into > > > >> > the > > > >> > > same repo under a different folder. If people feel they prefer > > this > > > >> over > > > >> > > the previous approach I would like to call for another round of > > > >> voting. > > > >> > > > > > >> > > Guozhang > > > >> > > > > > >> > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish < > paliwalash...@gmail.com > > > > > > >> > wrote: > > > >> > > > > > >> > > > +1 to what Gwen has suggested. This is what we follow in > Flume. > > > >> > > > > > > >> > > > All the latest doc changes are in git, once ready you move > > changes > > > >> to > > > >> > > > svn to update website. > > > >> > > > The only catch is, when you need to update specific changes to > > > >> website > > > >> > > > outside release cycle, need to be a bit careful :)
Re: KAFKA-2364 migrate docs from SVN to git
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 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 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. > > > > Ismael > > > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy > > wrote: > > > > > Hi All, > > > > > > Can we finalize the approach? So that we can proceed further. > > > > > > 1. Gwen's suggestion + existing svn repo > > > 2. Gwen's suggestion + new git repo for docs > > > > > > kumar > > > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy < > ku...@nmsworks.co.in> > > > wrote: > > > > > > > Also can we migrate svn repo to git repo? This will help us to fix > > > > occasional doc changes/bug fixes through github PR. > > > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > > > wrote: > > > > > > > >> Gwen: I remembered it wrong. We would not need another round of > > voting. > > > >> > > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > > > wrote: > > > >> > > > >> > Looking back at this thread, the +1 mention "same repo", so I'm > not > > > >> sure a > > > >> > new vote is required. > > > >> > > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang < > wangg...@gmail.com> > > > >> wrote: > > > >> > > > > >> > > So I think we have two different approaches here. The original > > > >> proposal > > > >> > > from Aseem is to move website from SVN to a separate Git repo, > and > > > >> hence > > > >> > > have separate commits on code / doc changes. For that we have > > > >> accumulated > > > >> > > enough binging +1s to move on; Gwen's proposal is to move > website > > > into > > > >> > the > > > >> > > same repo under a different folder. If people feel they prefer > > this > > > >> over > > > >> > > the previous approach I would like to call for another round of > > > >> voting. > > > >> > > > > > >> > > Guozhang > > > >> > > > > > >> > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish < > paliwalash...@gmail.com > > > > > > >> > wrote: > > > >> > > > > > >> > > > +1 to what Gwen has suggested. This is what we follow in > Flume. > > > >> > > > > > > >> > > > All the latest doc changes are in git, once ready you move > > changes > > > >> to > > > >> > > > svn to update website. > > > >> > > > The only catch is, when you need to update specific changes to > > > >> website > > > >> > > > outside release cycle, need to be a bit careful :) > > > >> > > > > > > >> > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira < > > g...@confluent.io> > > > >> > wrote: > > > >> > > > > Yeah, so the way this works in few other projects I worked > on > > > is: > > > >> > > > > > > > >> > > > > * The code repo has a /docs directory with the latest > revision > > > of > > > >> the > > > >> > > > docs > > > >> > > > > (not multiple versions, just one that matches the latest > state > > >
Re: KAFKA-2364 migrate docs from SVN to git
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 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. > > Ismael > > On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy > wrote: > > > Hi All, > > > > Can we finalize the approach? So that we can proceed further. > > > > 1. Gwen's suggestion + existing svn repo > > 2. Gwen's suggestion + new git repo for docs > > > > kumar > > > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy > > wrote: > > > > > Also can we migrate svn repo to git repo? This will help us to fix > > > occasional doc changes/bug fixes through github PR. > > > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > > wrote: > > > > > >> Gwen: I remembered it wrong. We would not need another round of > voting. > > >> > > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > > wrote: > > >> > > >> > Looking back at this thread, the +1 mention "same repo", so I'm not > > >> sure a > > >> > new vote is required. > > >> > > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang > > >> wrote: > > >> > > > >> > > So I think we have two different approaches here. The original > > >> proposal > > >> > > from Aseem is to move website from SVN to a separate Git repo, and > > >> hence > > >> > > have separate commits on code / doc changes. For that we have > > >> accumulated > > >> > > enough binging +1s to move on; Gwen's proposal is to move website > > into > > >> > the > > >> > > same repo under a different folder. If people feel they prefer > this > > >> over > > >> > > the previous approach I would like to call for another round of > > >> voting. > > >> > > > > >> > > Guozhang > > >> > > > > >> > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish > > > >> > wrote: > > >> > > > > >> > > > +1 to what Gwen has suggested. This is what we follow in Flume. > > >> > > > > > >> > > > All the latest doc changes are in git, once ready you move > changes > > >> to > > >> > > > svn to update website. > > >> > > > The only catch is, when you need to update specific changes to > > >> website > > >> > > > outside release cycle, need to be a bit careful :) > > >> > > > > > >> > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira < > g...@confluent.io> > > >> > wrote: > > >> > > > > Yeah, so the way this works in few other projects I worked on > > is: > > >> > > > > > > >> > > > > * The code repo has a /docs directory with the latest revision > > of > > >> the > > >> > > > docs > > >> > > > > (not multiple versions, just one that matches the latest state > > of > > >> > code) > > >> > > > > * When you submit a patch that requires doc modification, you > > >> modify > > >> > > all > > >> > > > > relevant files in same patch and they get reviewed and > committed > > >> > > together > > >> > > > > (ideally) > > >> > > > > * When we release, we copy the docs matching the release and > > >> commit > > >> > to > > >> > > > SVN > > >> > > > > website. We also do this occasionally to fix bugs in earlier > > docs. > > >> > > > > * Release artifacts include a copy of the docs > > >> > > > > > > >> >
Re: KAFKA-2364 migrate docs from SVN to git
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. Ismael On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy wrote: > Hi All, > > Can we finalize the approach? So that we can proceed further. > > 1. Gwen's suggestion + existing svn repo > 2. Gwen's suggestion + new git repo for docs > > kumar > > On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy > wrote: > > > Also can we migrate svn repo to git repo? This will help us to fix > > occasional doc changes/bug fixes through github PR. > > > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang > wrote: > > > >> Gwen: I remembered it wrong. We would not need another round of voting. > >> > >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira > wrote: > >> > >> > Looking back at this thread, the +1 mention "same repo", so I'm not > >> sure a > >> > new vote is required. > >> > > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang > >> wrote: > >> > > >> > > So I think we have two different approaches here. The original > >> proposal > >> > > from Aseem is to move website from SVN to a separate Git repo, and > >> hence > >> > > have separate commits on code / doc changes. For that we have > >> accumulated > >> > > enough binging +1s to move on; Gwen's proposal is to move website > into > >> > the > >> > > same repo under a different folder. If people feel they prefer this > >> over > >> > > the previous approach I would like to call for another round of > >> voting. > >> > > > >> > > Guozhang > >> > > > >> > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish > >> > wrote: > >> > > > >> > > > +1 to what Gwen has suggested. This is what we follow in Flume. > >> > > > > >> > > > All the latest doc changes are in git, once ready you move changes > >> to > >> > > > svn to update website. > >> > > > The only catch is, when you need to update specific changes to > >> website > >> > > > outside release cycle, need to be a bit careful :) > >> > > > > >> > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira > >> > wrote: > >> > > > > Yeah, so the way this works in few other projects I worked on > is: > >> > > > > > >> > > > > * The code repo has a /docs directory with the latest revision > of > >> the > >> > > > docs > >> > > > > (not multiple versions, just one that matches the latest state > of > >> > code) > >> > > > > * When you submit a patch that requires doc modification, you > >> modify > >> > > all > >> > > > > relevant files in same patch and they get reviewed and committed > >> > > together > >> > > > > (ideally) > >> > > > > * When we release, we copy the docs matching the release and > >> commit > >> > to > >> > > > SVN > >> > > > > website. We also do this occasionally to fix bugs in earlier > docs. > >> > > > > * Release artifacts include a copy of the docs > >> > > > > > >> > > > > Nice to have: > >> > > > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is > >> > easier > >> > > > to > >> > > > > edit and review. > >> > > > > > >> > > > > I suggest a similar process for Kafka. > >> > > > > > >> > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma > > >> > > wrote: > >> > > > > > >> > > > >> I should clarify: it's not possible unless we add an additional > >> step > >> > > > that > >> > > > >> moves the docs from the code repo to the website repo. > >> > > > >> > >> > > > >> Ismael > >> > > > >> > >> > > > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma < > ism...@juma.me.uk> > >> > > w
Re: KAFKA-2364 migrate docs from SVN to git
Hi All, Can we finalize the approach? So that we can proceed further. 1. Gwen's suggestion + existing svn repo 2. Gwen's suggestion + new git repo for docs kumar On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy wrote: > Also can we migrate svn repo to git repo? This will help us to fix > occasional doc changes/bug fixes through github PR. > > On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang wrote: > >> Gwen: I remembered it wrong. We would not need another round of voting. >> >> On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira wrote: >> >> > Looking back at this thread, the +1 mention "same repo", so I'm not >> sure a >> > new vote is required. >> > >> > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang >> wrote: >> > >> > > So I think we have two different approaches here. The original >> proposal >> > > from Aseem is to move website from SVN to a separate Git repo, and >> hence >> > > have separate commits on code / doc changes. For that we have >> accumulated >> > > enough binging +1s to move on; Gwen's proposal is to move website into >> > the >> > > same repo under a different folder. If people feel they prefer this >> over >> > > the previous approach I would like to call for another round of >> voting. >> > > >> > > Guozhang >> > > >> > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish >> > wrote: >> > > >> > > > +1 to what Gwen has suggested. This is what we follow in Flume. >> > > > >> > > > All the latest doc changes are in git, once ready you move changes >> to >> > > > svn to update website. >> > > > The only catch is, when you need to update specific changes to >> website >> > > > outside release cycle, need to be a bit careful :) >> > > > >> > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira >> > wrote: >> > > > > Yeah, so the way this works in few other projects I worked on is: >> > > > > >> > > > > * The code repo has a /docs directory with the latest revision of >> the >> > > > docs >> > > > > (not multiple versions, just one that matches the latest state of >> > code) >> > > > > * When you submit a patch that requires doc modification, you >> modify >> > > all >> > > > > relevant files in same patch and they get reviewed and committed >> > > together >> > > > > (ideally) >> > > > > * When we release, we copy the docs matching the release and >> commit >> > to >> > > > SVN >> > > > > website. We also do this occasionally to fix bugs in earlier docs. >> > > > > * Release artifacts include a copy of the docs >> > > > > >> > > > > Nice to have: >> > > > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is >> > easier >> > > > to >> > > > > edit and review. >> > > > > >> > > > > I suggest a similar process for Kafka. >> > > > > >> > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma >> > > wrote: >> > > > > >> > > > >> I should clarify: it's not possible unless we add an additional >> step >> > > > that >> > > > >> moves the docs from the code repo to the website repo. >> > > > >> >> > > > >> Ismael >> > > > >> >> > > > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma >> > > wrote: >> > > > >> >> > > > >> > Hi all, >> > > > >> > >> > > > >> > It looks like it's not feasible to update the code and website >> in >> > > the >> > > > >> same >> > > > >> > commit given existing limitations of the Apache infra: >> > > > >> > >> > > > >> > >> > > > >> > >> > > > >> >> > > > >> > > >> > >> https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 >> > > > >> > >> > > > >> > Best
Re: KAFKA-2364 migrate docs from SVN to git
Also can we migrate svn repo to git repo? This will help us to fix occasional doc changes/bug fixes through github PR. On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang wrote: > Gwen: I remembered it wrong. We would not need another round of voting. > > On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira wrote: > > > Looking back at this thread, the +1 mention "same repo", so I'm not sure > a > > new vote is required. > > > > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang > wrote: > > > > > So I think we have two different approaches here. The original proposal > > > from Aseem is to move website from SVN to a separate Git repo, and > hence > > > have separate commits on code / doc changes. For that we have > accumulated > > > enough binging +1s to move on; Gwen's proposal is to move website into > > the > > > same repo under a different folder. If people feel they prefer this > over > > > the previous approach I would like to call for another round of voting. > > > > > > Guozhang > > > > > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish > > wrote: > > > > > > > +1 to what Gwen has suggested. This is what we follow in Flume. > > > > > > > > All the latest doc changes are in git, once ready you move changes to > > > > svn to update website. > > > > The only catch is, when you need to update specific changes to > website > > > > outside release cycle, need to be a bit careful :) > > > > > > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira > > wrote: > > > > > Yeah, so the way this works in few other projects I worked on is: > > > > > > > > > > * The code repo has a /docs directory with the latest revision of > the > > > > docs > > > > > (not multiple versions, just one that matches the latest state of > > code) > > > > > * When you submit a patch that requires doc modification, you > modify > > > all > > > > > relevant files in same patch and they get reviewed and committed > > > together > > > > > (ideally) > > > > > * When we release, we copy the docs matching the release and commit > > to > > > > SVN > > > > > website. We also do this occasionally to fix bugs in earlier docs. > > > > > * Release artifacts include a copy of the docs > > > > > > > > > > Nice to have: > > > > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is > > easier > > > > to > > > > > edit and review. > > > > > > > > > > I suggest a similar process for Kafka. > > > > > > > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma > > > wrote: > > > > > > > > > >> I should clarify: it's not possible unless we add an additional > step > > > > that > > > > >> moves the docs from the code repo to the website repo. > > > > >> > > > > >> Ismael > > > > >> > > > > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma > > > wrote: > > > > >> > > > > >> > Hi all, > > > > >> > > > > > >> > It looks like it's not feasible to update the code and website > in > > > the > > > > >> same > > > > >> > commit given existing limitations of the Apache infra: > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > > > > >> > > > > > >> > Best, > > > > >> > Ismael > > > > >> > > > > > >> > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma < > ism...@juma.me.uk> > > > > wrote: > > > > >> > > > > > >> >> Hi Gwen, > > > > >> >> > > > > >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website > > > > >> >> documentation. Aseem Bansal seemed interested in helping us > with > > > the > > > > >> move > > > > >> >> so I pinged him in the issue. &g
Re: KAFKA-2364 migrate docs from SVN to git
Gwen: I remembered it wrong. We would not need another round of voting. On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira wrote: > Looking back at this thread, the +1 mention "same repo", so I'm not sure a > new vote is required. > > On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang wrote: > > > So I think we have two different approaches here. The original proposal > > from Aseem is to move website from SVN to a separate Git repo, and hence > > have separate commits on code / doc changes. For that we have accumulated > > enough binging +1s to move on; Gwen's proposal is to move website into > the > > same repo under a different folder. If people feel they prefer this over > > the previous approach I would like to call for another round of voting. > > > > Guozhang > > > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish > wrote: > > > > > +1 to what Gwen has suggested. This is what we follow in Flume. > > > > > > All the latest doc changes are in git, once ready you move changes to > > > svn to update website. > > > The only catch is, when you need to update specific changes to website > > > outside release cycle, need to be a bit careful :) > > > > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira > wrote: > > > > Yeah, so the way this works in few other projects I worked on is: > > > > > > > > * The code repo has a /docs directory with the latest revision of the > > > docs > > > > (not multiple versions, just one that matches the latest state of > code) > > > > * When you submit a patch that requires doc modification, you modify > > all > > > > relevant files in same patch and they get reviewed and committed > > together > > > > (ideally) > > > > * When we release, we copy the docs matching the release and commit > to > > > SVN > > > > website. We also do this occasionally to fix bugs in earlier docs. > > > > * Release artifacts include a copy of the docs > > > > > > > > Nice to have: > > > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is > easier > > > to > > > > edit and review. > > > > > > > > I suggest a similar process for Kafka. > > > > > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma > > wrote: > > > > > > > >> I should clarify: it's not possible unless we add an additional step > > > that > > > >> moves the docs from the code repo to the website repo. > > > >> > > > >> Ismael > > > >> > > > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma > > wrote: > > > >> > > > >> > Hi all, > > > >> > > > > >> > It looks like it's not feasible to update the code and website in > > the > > > >> same > > > >> > commit given existing limitations of the Apache infra: > > > >> > > > > >> > > > > >> > > > > >> > > > > > > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > > > >> > > > > >> > Best, > > > >> > Ismael > > > >> > > > > >> > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma > > > wrote: > > > >> > > > > >> >> Hi Gwen, > > > >> >> > > > >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website > > > >> >> documentation. Aseem Bansal seemed interested in helping us with > > the > > > >> move > > > >> >> so I pinged him in the issue. > > > >> >> > > > >> >> Best, > > > >> >> Ismael > > > >> >> > > > >> >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > > > > >> wrote: > > > >> >> > > > >> >>> Ah, there is already a JIRA in the title. Never mind :) > > > >> >>> > > > >> >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira < > g...@confluent.io> > > > >> wrote: > > > >> >>> > > > >> >>> > The vote opened 5 days ago. I believe we can conclude with 3 > > > binding > > >
Re: KAFKA-2364 migrate docs from SVN to git
Looking back at this thread, the +1 mention "same repo", so I'm not sure a new vote is required. On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang wrote: > So I think we have two different approaches here. The original proposal > from Aseem is to move website from SVN to a separate Git repo, and hence > have separate commits on code / doc changes. For that we have accumulated > enough binging +1s to move on; Gwen's proposal is to move website into the > same repo under a different folder. If people feel they prefer this over > the previous approach I would like to call for another round of voting. > > Guozhang > > On Wed, Aug 19, 2015 at 10:24 AM, Ashish wrote: > > > +1 to what Gwen has suggested. This is what we follow in Flume. > > > > All the latest doc changes are in git, once ready you move changes to > > svn to update website. > > The only catch is, when you need to update specific changes to website > > outside release cycle, need to be a bit careful :) > > > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira wrote: > > > Yeah, so the way this works in few other projects I worked on is: > > > > > > * The code repo has a /docs directory with the latest revision of the > > docs > > > (not multiple versions, just one that matches the latest state of code) > > > * When you submit a patch that requires doc modification, you modify > all > > > relevant files in same patch and they get reviewed and committed > together > > > (ideally) > > > * When we release, we copy the docs matching the release and commit to > > SVN > > > website. We also do this occasionally to fix bugs in earlier docs. > > > * Release artifacts include a copy of the docs > > > > > > Nice to have: > > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is easier > > to > > > edit and review. > > > > > > I suggest a similar process for Kafka. > > > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma > wrote: > > > > > >> I should clarify: it's not possible unless we add an additional step > > that > > >> moves the docs from the code repo to the website repo. > > >> > > >> Ismael > > >> > > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma > wrote: > > >> > > >> > Hi all, > > >> > > > >> > It looks like it's not feasible to update the code and website in > the > > >> same > > >> > commit given existing limitations of the Apache infra: > > >> > > > >> > > > >> > > > >> > > > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > > >> > > > >> > Best, > > >> > Ismael > > >> > > > >> > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma > > wrote: > > >> > > > >> >> Hi Gwen, > > >> >> > > >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website > > >> >> documentation. Aseem Bansal seemed interested in helping us with > the > > >> move > > >> >> so I pinged him in the issue. > > >> >> > > >> >> Best, > > >> >> Ismael > > >> >> > > >> >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > > >> wrote: > > >> >> > > >> >>> Ah, there is already a JIRA in the title. Never mind :) > > >> >>> > > >> >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > > >> wrote: > > >> >>> > > >> >>> > The vote opened 5 days ago. I believe we can conclude with 3 > > binding > > >> >>> +1, 3 > > >> >>> > non-binding +1 and no -1. > > >> >>> > > > >> >>> > Ismael, are you opening and JIRA and migrating? Or are we > looking > > >> for a > > >> >>> > volunteer? > > >> >>> > > > >> >>> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh < > > asi...@cloudera.com> > > >> >>> wrote: > > >> >>> > > > >> >>> >> +1 on same repo. > > >> >>> >> > > >>
Re: KAFKA-2364 migrate docs from SVN to git
So I think we have two different approaches here. The original proposal from Aseem is to move website from SVN to a separate Git repo, and hence have separate commits on code / doc changes. For that we have accumulated enough binging +1s to move on; Gwen's proposal is to move website into the same repo under a different folder. If people feel they prefer this over the previous approach I would like to call for another round of voting. Guozhang On Wed, Aug 19, 2015 at 10:24 AM, Ashish wrote: > +1 to what Gwen has suggested. This is what we follow in Flume. > > All the latest doc changes are in git, once ready you move changes to > svn to update website. > The only catch is, when you need to update specific changes to website > outside release cycle, need to be a bit careful :) > > On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira wrote: > > Yeah, so the way this works in few other projects I worked on is: > > > > * The code repo has a /docs directory with the latest revision of the > docs > > (not multiple versions, just one that matches the latest state of code) > > * When you submit a patch that requires doc modification, you modify all > > relevant files in same patch and they get reviewed and committed together > > (ideally) > > * When we release, we copy the docs matching the release and commit to > SVN > > website. We also do this occasionally to fix bugs in earlier docs. > > * Release artifacts include a copy of the docs > > > > Nice to have: > > * Docs are in Asciidoc and build generates the HTML. Asciidoc is easier > to > > edit and review. > > > > I suggest a similar process for Kafka. > > > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma wrote: > > > >> I should clarify: it's not possible unless we add an additional step > that > >> moves the docs from the code repo to the website repo. > >> > >> Ismael > >> > >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma wrote: > >> > >> > Hi all, > >> > > >> > It looks like it's not feasible to update the code and website in the > >> same > >> > commit given existing limitations of the Apache infra: > >> > > >> > > >> > > >> > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > >> > > >> > Best, > >> > Ismael > >> > > >> > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma > wrote: > >> > > >> >> Hi Gwen, > >> >> > >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website > >> >> documentation. Aseem Bansal seemed interested in helping us with the > >> move > >> >> so I pinged him in the issue. > >> >> > >> >> Best, > >> >> Ismael > >> >> > >> >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > >> wrote: > >> >> > >> >>> Ah, there is already a JIRA in the title. Never mind :) > >> >>> > >> >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > >> wrote: > >> >>> > >> >>> > The vote opened 5 days ago. I believe we can conclude with 3 > binding > >> >>> +1, 3 > >> >>> > non-binding +1 and no -1. > >> >>> > > >> >>> > Ismael, are you opening and JIRA and migrating? Or are we looking > >> for a > >> >>> > volunteer? > >> >>> > > >> >>> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh < > asi...@cloudera.com> > >> >>> wrote: > >> >>> > > >> >>> >> +1 on same repo. > >> >>> >> > >> >>> >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < > >> >>> >> edward.ribe...@gmail.com> > >> >>> >> wrote: > >> >>> >> > >> >>> >> > +1. As soon as possible, please. :) > >> >>> >> > > >> >>> >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede < > n...@confluent.io> > >> >>> >> wrote: > >> >>> >> > > >> >>> >> > > +1 on the same repo for code and website. It helps to keep > both > >> in > >> >>> >> sync. > >> >>&g
Re: KAFKA-2364 migrate docs from SVN to git
+1 to what Gwen has suggested. This is what we follow in Flume. All the latest doc changes are in git, once ready you move changes to svn to update website. The only catch is, when you need to update specific changes to website outside release cycle, need to be a bit careful :) On Wed, Aug 19, 2015 at 9:06 AM, Gwen Shapira wrote: > Yeah, so the way this works in few other projects I worked on is: > > * The code repo has a /docs directory with the latest revision of the docs > (not multiple versions, just one that matches the latest state of code) > * When you submit a patch that requires doc modification, you modify all > relevant files in same patch and they get reviewed and committed together > (ideally) > * When we release, we copy the docs matching the release and commit to SVN > website. We also do this occasionally to fix bugs in earlier docs. > * Release artifacts include a copy of the docs > > Nice to have: > * Docs are in Asciidoc and build generates the HTML. Asciidoc is easier to > edit and review. > > I suggest a similar process for Kafka. > > On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma wrote: > >> I should clarify: it's not possible unless we add an additional step that >> moves the docs from the code repo to the website repo. >> >> Ismael >> >> On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma wrote: >> >> > Hi all, >> > >> > It looks like it's not feasible to update the code and website in the >> same >> > commit given existing limitations of the Apache infra: >> > >> > >> > >> https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 >> > >> > Best, >> > Ismael >> > >> > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma wrote: >> > >> >> Hi Gwen, >> >> >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website >> >> documentation. Aseem Bansal seemed interested in helping us with the >> move >> >> so I pinged him in the issue. >> >> >> >> Best, >> >> Ismael >> >> >> >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira >> wrote: >> >> >> >>> Ah, there is already a JIRA in the title. Never mind :) >> >>> >> >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira >> wrote: >> >>> >> >>> > The vote opened 5 days ago. I believe we can conclude with 3 binding >> >>> +1, 3 >> >>> > non-binding +1 and no -1. >> >>> > >> >>> > Ismael, are you opening and JIRA and migrating? Or are we looking >> for a >> >>> > volunteer? >> >>> > >> >>> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh >> >>> wrote: >> >>> > >> >>> >> +1 on same repo. >> >>> >> >> >>> >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < >> >>> >> edward.ribe...@gmail.com> >> >>> >> wrote: >> >>> >> >> >>> >> > +1. As soon as possible, please. :) >> >>> >> > >> >>> >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede >> >>> >> wrote: >> >>> >> > >> >>> >> > > +1 on the same repo for code and website. It helps to keep both >> in >> >>> >> sync. >> >>> >> > > >> >>> >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < >> ghe...@cloudera.com> >> >>> >> wrote: >> >>> >> > > >> >>> >> > > > +1 for the same repo. The closer docs can be to code the more >> >>> >> accurate >> >>> >> > > they >> >>> >> > > > are likely to be. The same way we encourage unit tests for a >> new >> >>> >> > > > feature/patch. Updating the docs can be the same. >> >>> >> > > > >> >>> >> > > > If we follow Sqoop's process for example, how would small >> >>> >> > > > fixes/adjustments/additions to the live documentation occur >> >>> without >> >>> >> a >> >>> >> > new >> >>> >> > > > release? >> >&g
[jira] [Comment Edited] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703327#comment-14703327 ] Aseem Bansal edited comment on KAFKA-2425 at 8/19/15 4:47 PM: -- Sorry [~omkreddy] but not getting the time currently. Been busy for past some days. I checked INFRA team ticket and it says that only asf-site branch is supported. I understand that it is definitely a bummer. Just thinking whether it would be possible to use travis or something else to auto cherry pick from trunk/master to this branch? Then the commits can be done to master and let the script do the cherry picks. Don't know how to do it but will look if it is possible. Something like http://lea.verou.me/2011/10/easily-keep-gh-pages-in-sync-with-master/ was (Author: anshbansal): Sorry [~omkreddy] but not getting the time currently. Been busy for past some days. I checked INFRA team ticket and it says that only asf-site branch is supported. I understand that it is definitely a bummer. Just thinking whether it would be possible to use travis or something else to auto cherry pick from trunk/master to this branch? Then the commits can be done to master and let the script do the cherry picks. Don't know how to do it but will look if it is possible. > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703327#comment-14703327 ] Aseem Bansal commented on KAFKA-2425: - Sorry [~omkreddy] but not getting the time currently. Been busy for past some days. I checked INFRA team ticket and it says that only asf-site branch is supported. I understand that it is definitely a bummer. Just thinking whether it would be possible to use travis or something else to auto cherry pick from trunk/master to this branch? Then the commits can be done to master and let the script do the cherry picks. Don't know how to do it but will look if it is possible. > 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)
Re: KAFKA-2364 migrate docs from SVN to git
yes. we can not. we need two separate github PRs for code and doc changes. On Wed, Aug 19, 2015 at 9:35 PM, Guozhang Wang wrote: > Even under the second option, it sounds like we still cannot include the > code and doc changes in one commit? > > Guozhang > > On Wed, Aug 19, 2015 at 8:56 AM, Manikumar Reddy > wrote: > > > oops.. i did not check Ismail's mail. > > > > On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy > > wrote: > > > > > Hi, > > > > > > We have raised a Apache Infra ticket for migrating site docs from svn > > > -> git . > > > Currently, the gitwcsub client only supports using the "asf-site" > > > branch for site docs. > > > Infra team is suggesting to create new git repo for site docs. > > > > > >Infra ticket here: > > >https://issues.apache.org/jira/browse/INFRA-10143 > > > > > >Possible Options: > > >1. Maintain code and docs in same repo, but on different branches > > > (trunk and asf-site) > > >2. Create a new git repo for docs and integrate with gitwcsub. > > > > > >I vote for second option. > > > > > > > > > Kumar > > > > > > On Wed, Aug 12, 2015 at 3:51 PM, Edward Ribeiro < > > edward.ribe...@gmail.com> > > > wrote: > > > > > >> FYI, I created a tiny trivial patch to address a typo in the web site > > >> (KAFKA-2418), so maybe you can review it and eventually commit before > > >> moving to github. ;) > > >> > > >> Cheers, > > >> Eddie > > >> Em 12/08/2015 06:01, "Ismael Juma" escreveu: > > >> > > >> > Hi Gwen, > > >> > > > >> > I filed KAFKA-2425 as KAFKA-2364 is about improving the website > > >> > documentation. Aseem Bansal seemed interested in helping us with the > > >> move > > >> > so I pinged him in the issue. > > >> > > > >> > Best, > > >> > Ismael > > >> > > > >> > On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > > >> wrote: > > >> > > > >> > > Ah, there is already a JIRA in the title. Never mind :) > > >> > > > > >> > > On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > > >> wrote: > > >> > > > > >> > > > The vote opened 5 days ago. I believe we can conclude with 3 > > binding > > >> > +1, > > >> > > 3 > > >> > > > non-binding +1 and no -1. > > >> > > > > > >> > > > Ismael, are you opening and JIRA and migrating? Or are we > looking > > >> for a > > >> > > > volunteer? > > >> > > > > > >> > > > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh < > > asi...@cloudera.com> > > >> > > wrote: > > >> > > > > > >> > > >> +1 on same repo. > > >> > > >> > > >> > > >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < > > >> > > >> edward.ribe...@gmail.com> > > >> > > >> wrote: > > >> > > >> > > >> > > >> > +1. As soon as possible, please. :) > > >> > > >> > > > >> > > >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede < > > n...@confluent.io > > >> > > > >> > > >> wrote: > > >> > > >> > > > >> > > >> > > +1 on the same repo for code and website. It helps to keep > > >> both in > > >> > > >> sync. > > >> > > >> > > > > >> > > >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < > > >> ghe...@cloudera.com> > > >> > > >> wrote: > > >> > > >> > > > > >> > > >> > > > +1 for the same repo. The closer docs can be to code the > > more > > >> > > >> accurate > > >> > > >> > > they > > >> > > >> > > > are likely to be. The same way we encourage unit tests > for > > a > > >> new > > >> > > >> > > > feature/patch. Updating the docs can be the same. > > &
Re: KAFKA-2364 migrate docs from SVN to git
Yeah, so the way this works in few other projects I worked on is: * The code repo has a /docs directory with the latest revision of the docs (not multiple versions, just one that matches the latest state of code) * When you submit a patch that requires doc modification, you modify all relevant files in same patch and they get reviewed and committed together (ideally) * When we release, we copy the docs matching the release and commit to SVN website. We also do this occasionally to fix bugs in earlier docs. * Release artifacts include a copy of the docs Nice to have: * Docs are in Asciidoc and build generates the HTML. Asciidoc is easier to edit and review. I suggest a similar process for Kafka. On Wed, Aug 19, 2015 at 8:53 AM, Ismael Juma wrote: > I should clarify: it's not possible unless we add an additional step that > moves the docs from the code repo to the website repo. > > Ismael > > On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma wrote: > > > Hi all, > > > > It looks like it's not feasible to update the code and website in the > same > > commit given existing limitations of the Apache infra: > > > > > > > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > > > > Best, > > Ismael > > > > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma wrote: > > > >> Hi Gwen, > >> > >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website > >> documentation. Aseem Bansal seemed interested in helping us with the > move > >> so I pinged him in the issue. > >> > >> Best, > >> Ismael > >> > >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > wrote: > >> > >>> Ah, there is already a JIRA in the title. Never mind :) > >>> > >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > wrote: > >>> > >>> > The vote opened 5 days ago. I believe we can conclude with 3 binding > >>> +1, 3 > >>> > non-binding +1 and no -1. > >>> > > >>> > Ismael, are you opening and JIRA and migrating? Or are we looking > for a > >>> > volunteer? > >>> > > >>> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh > >>> wrote: > >>> > > >>> >> +1 on same repo. > >>> >> > >>> >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < > >>> >> edward.ribe...@gmail.com> > >>> >> wrote: > >>> >> > >>> >> > +1. As soon as possible, please. :) > >>> >> > > >>> >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede > >>> >> wrote: > >>> >> > > >>> >> > > +1 on the same repo for code and website. It helps to keep both > in > >>> >> sync. > >>> >> > > > >>> >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < > ghe...@cloudera.com> > >>> >> wrote: > >>> >> > > > >>> >> > > > +1 for the same repo. The closer docs can be to code the more > >>> >> accurate > >>> >> > > they > >>> >> > > > are likely to be. The same way we encourage unit tests for a > new > >>> >> > > > feature/patch. Updating the docs can be the same. > >>> >> > > > > >>> >> > > > If we follow Sqoop's process for example, how would small > >>> >> > > > fixes/adjustments/additions to the live documentation occur > >>> without > >>> >> a > >>> >> > new > >>> >> > > > release? > >>> >> > > > > >>> >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < > >>> wangg...@gmail.com> > >>> >> > > wrote: > >>> >> > > > > >>> >> > > > > I am +1 on same repo too. I think keeping one git history of > >>> code > >>> >> / > >>> >> > doc > >>> >> > > > > change may actually be beneficial for this approach as well. > >>> >> > > > > > >>> >> > > > > Guozhang > >>> >> > > > > > >>> >> > >
Re: KAFKA-2364 migrate docs from SVN to git
Even under the second option, it sounds like we still cannot include the code and doc changes in one commit? Guozhang On Wed, Aug 19, 2015 at 8:56 AM, Manikumar Reddy wrote: > oops.. i did not check Ismail's mail. > > On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy > wrote: > > > Hi, > > > > We have raised a Apache Infra ticket for migrating site docs from svn > > -> git . > > Currently, the gitwcsub client only supports using the "asf-site" > > branch for site docs. > > Infra team is suggesting to create new git repo for site docs. > > > >Infra ticket here: > >https://issues.apache.org/jira/browse/INFRA-10143 > > > >Possible Options: > >1. Maintain code and docs in same repo, but on different branches > > (trunk and asf-site) > >2. Create a new git repo for docs and integrate with gitwcsub. > > > >I vote for second option. > > > > > > Kumar > > > > On Wed, Aug 12, 2015 at 3:51 PM, Edward Ribeiro < > edward.ribe...@gmail.com> > > wrote: > > > >> FYI, I created a tiny trivial patch to address a typo in the web site > >> (KAFKA-2418), so maybe you can review it and eventually commit before > >> moving to github. ;) > >> > >> Cheers, > >> Eddie > >> Em 12/08/2015 06:01, "Ismael Juma" escreveu: > >> > >> > Hi Gwen, > >> > > >> > I filed KAFKA-2425 as KAFKA-2364 is about improving the website > >> > documentation. Aseem Bansal seemed interested in helping us with the > >> move > >> > so I pinged him in the issue. > >> > > >> > Best, > >> > Ismael > >> > > >> > On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira > >> wrote: > >> > > >> > > Ah, there is already a JIRA in the title. Never mind :) > >> > > > >> > > On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > >> wrote: > >> > > > >> > > > The vote opened 5 days ago. I believe we can conclude with 3 > binding > >> > +1, > >> > > 3 > >> > > > non-binding +1 and no -1. > >> > > > > >> > > > Ismael, are you opening and JIRA and migrating? Or are we looking > >> for a > >> > > > volunteer? > >> > > > > >> > > > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh < > asi...@cloudera.com> > >> > > wrote: > >> > > > > >> > > >> +1 on same repo. > >> > > >> > >> > > >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < > >> > > >> edward.ribe...@gmail.com> > >> > > >> wrote: > >> > > >> > >> > > >> > +1. As soon as possible, please. :) > >> > > >> > > >> > > >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede < > n...@confluent.io > >> > > >> > > >> wrote: > >> > > >> > > >> > > >> > > +1 on the same repo for code and website. It helps to keep > >> both in > >> > > >> sync. > >> > > >> > > > >> > > >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < > >> ghe...@cloudera.com> > >> > > >> wrote: > >> > > >> > > > >> > > >> > > > +1 for the same repo. The closer docs can be to code the > more > >> > > >> accurate > >> > > >> > > they > >> > > >> > > > are likely to be. The same way we encourage unit tests for > a > >> new > >> > > >> > > > feature/patch. Updating the docs can be the same. > >> > > >> > > > > >> > > >> > > > If we follow Sqoop's process for example, how would small > >> > > >> > > > fixes/adjustments/additions to the live documentation occur > >> > > without > >> > > >> a > >> > > >> > new > >> > > >> > > > release? > >> > > >> > > > > >> > > >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < > >> > wangg...@gmail.com > >> > > > > >> > > >> > > wrote: >
Re: KAFKA-2364 migrate docs from SVN to git
oops.. i did not check Ismail's mail. On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy wrote: > Hi, > > We have raised a Apache Infra ticket for migrating site docs from svn > -> git . > Currently, the gitwcsub client only supports using the "asf-site" > branch for site docs. > Infra team is suggesting to create new git repo for site docs. > >Infra ticket here: >https://issues.apache.org/jira/browse/INFRA-10143 > >Possible Options: >1. Maintain code and docs in same repo, but on different branches > (trunk and asf-site) >2. Create a new git repo for docs and integrate with gitwcsub. > >I vote for second option. > > > Kumar > > On Wed, Aug 12, 2015 at 3:51 PM, Edward Ribeiro > wrote: > >> FYI, I created a tiny trivial patch to address a typo in the web site >> (KAFKA-2418), so maybe you can review it and eventually commit before >> moving to github. ;) >> >> Cheers, >> Eddie >> Em 12/08/2015 06:01, "Ismael Juma" escreveu: >> >> > Hi Gwen, >> > >> > I filed KAFKA-2425 as KAFKA-2364 is about improving the website >> > documentation. Aseem Bansal seemed interested in helping us with the >> move >> > so I pinged him in the issue. >> > >> > Best, >> > Ismael >> > >> > On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira >> wrote: >> > >> > > Ah, there is already a JIRA in the title. Never mind :) >> > > >> > > On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira >> wrote: >> > > >> > > > The vote opened 5 days ago. I believe we can conclude with 3 binding >> > +1, >> > > 3 >> > > > non-binding +1 and no -1. >> > > > >> > > > Ismael, are you opening and JIRA and migrating? Or are we looking >> for a >> > > > volunteer? >> > > > >> > > > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh >> > > wrote: >> > > > >> > > >> +1 on same repo. >> > > >> >> > > >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < >> > > >> edward.ribe...@gmail.com> >> > > >> wrote: >> > > >> >> > > >> > +1. As soon as possible, please. :) >> > > >> > >> > > >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede > > >> > > >> wrote: >> > > >> > >> > > >> > > +1 on the same repo for code and website. It helps to keep >> both in >> > > >> sync. >> > > >> > > >> > > >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < >> ghe...@cloudera.com> >> > > >> wrote: >> > > >> > > >> > > >> > > > +1 for the same repo. The closer docs can be to code the more >> > > >> accurate >> > > >> > > they >> > > >> > > > are likely to be. The same way we encourage unit tests for a >> new >> > > >> > > > feature/patch. Updating the docs can be the same. >> > > >> > > > >> > > >> > > > If we follow Sqoop's process for example, how would small >> > > >> > > > fixes/adjustments/additions to the live documentation occur >> > > without >> > > >> a >> > > >> > new >> > > >> > > > release? >> > > >> > > > >> > > >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < >> > wangg...@gmail.com >> > > > >> > > >> > > wrote: >> > > >> > > > >> > > >> > > > > I am +1 on same repo too. I think keeping one git history >> of >> > > code >> > > >> / >> > > >> > doc >> > > >> > > > > change may actually be beneficial for this approach as >> well. >> > > >> > > > > >> > > >> > > > > Guozhang >> > > >> > > > > >> > > >> > > > > On Thu, Aug 6, 2015 at 9:16 AM, Gwen Shapira < >> > g...@confluent.io >> > > > >> > > >> > > wrote: >> > > >> > > > > >> > > >> > > > > >
Re: KAFKA-2364 migrate docs from SVN to git
Hi, We have raised a Apache Infra ticket for migrating site docs from svn -> git . Currently, the gitwcsub client only supports using the "asf-site" branch for site docs. Infra team is suggesting to create new git repo for site docs. Infra ticket here: https://issues.apache.org/jira/browse/INFRA-10143 Possible Options: 1. Maintain code and docs in same repo, but on different branches (trunk and asf-site) 2. Create a new git repo for docs and integrate with gitwcsub. I vote for second option. Kumar On Wed, Aug 12, 2015 at 3:51 PM, Edward Ribeiro wrote: > FYI, I created a tiny trivial patch to address a typo in the web site > (KAFKA-2418), so maybe you can review it and eventually commit before > moving to github. ;) > > Cheers, > Eddie > Em 12/08/2015 06:01, "Ismael Juma" escreveu: > > > Hi Gwen, > > > > I filed KAFKA-2425 as KAFKA-2364 is about improving the website > > documentation. Aseem Bansal seemed interested in helping us with the move > > so I pinged him in the issue. > > > > Best, > > Ismael > > > > On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira wrote: > > > > > Ah, there is already a JIRA in the title. Never mind :) > > > > > > On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira > wrote: > > > > > > > The vote opened 5 days ago. I believe we can conclude with 3 binding > > +1, > > > 3 > > > > non-binding +1 and no -1. > > > > > > > > Ismael, are you opening and JIRA and migrating? Or are we looking > for a > > > > volunteer? > > > > > > > > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh > > > wrote: > > > > > > > >> +1 on same repo. > > > >> > > > >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < > > > >> edward.ribe...@gmail.com> > > > >> wrote: > > > >> > > > >> > +1. As soon as possible, please. :) > > > >> > > > > >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede > > > >> wrote: > > > >> > > > > >> > > +1 on the same repo for code and website. It helps to keep both > in > > > >> sync. > > > >> > > > > > >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke < > ghe...@cloudera.com> > > > >> wrote: > > > >> > > > > > >> > > > +1 for the same repo. The closer docs can be to code the more > > > >> accurate > > > >> > > they > > > >> > > > are likely to be. The same way we encourage unit tests for a > new > > > >> > > > feature/patch. Updating the docs can be the same. > > > >> > > > > > > >> > > > If we follow Sqoop's process for example, how would small > > > >> > > > fixes/adjustments/additions to the live documentation occur > > > without > > > >> a > > > >> > new > > > >> > > > release? > > > >> > > > > > > >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < > > wangg...@gmail.com > > > > > > > >> > > wrote: > > > >> > > > > > > >> > > > > I am +1 on same repo too. I think keeping one git history of > > > code > > > >> / > > > >> > doc > > > >> > > > > change may actually be beneficial for this approach as well. > > > >> > > > > > > > >> > > > > Guozhang > > > >> > > > > > > > >> > > > > On Thu, Aug 6, 2015 at 9:16 AM, Gwen Shapira < > > g...@confluent.io > > > > > > > >> > > wrote: > > > >> > > > > > > > >> > > > > > I prefer same repo for one-commit / lower-barrier > benefits. > > > >> > > > > > > > > >> > > > > > Sqoop has the following process, which decouples > > documentation > > > >> > > changes > > > >> > > > > from > > > >> > > > > > website changes: > > > >> > > > > > > > > >> > > > > > 1. Code github repo contains a doc directory, with the > > > >> > documentation &
Re: KAFKA-2364 migrate docs from SVN to git
I should clarify: it's not possible unless we add an additional step that moves the docs from the code repo to the website repo. Ismael On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma wrote: > Hi all, > > It looks like it's not feasible to update the code and website in the same > commit given existing limitations of the Apache infra: > > > https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 > > Best, > Ismael > > On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma wrote: > >> Hi Gwen, >> >> I filed KAFKA-2425 as KAFKA-2364 is about improving the website >> documentation. Aseem Bansal seemed interested in helping us with the move >> so I pinged him in the issue. >> >> Best, >> Ismael >> >> On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira wrote: >> >>> Ah, there is already a JIRA in the title. Never mind :) >>> >>> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira wrote: >>> >>> > The vote opened 5 days ago. I believe we can conclude with 3 binding >>> +1, 3 >>> > non-binding +1 and no -1. >>> > >>> > Ismael, are you opening and JIRA and migrating? Or are we looking for a >>> > volunteer? >>> > >>> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh >>> wrote: >>> > >>> >> +1 on same repo. >>> >> >>> >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < >>> >> edward.ribe...@gmail.com> >>> >> wrote: >>> >> >>> >> > +1. As soon as possible, please. :) >>> >> > >>> >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede >>> >> wrote: >>> >> > >>> >> > > +1 on the same repo for code and website. It helps to keep both in >>> >> sync. >>> >> > > >>> >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke >>> >> wrote: >>> >> > > >>> >> > > > +1 for the same repo. The closer docs can be to code the more >>> >> accurate >>> >> > > they >>> >> > > > are likely to be. The same way we encourage unit tests for a new >>> >> > > > feature/patch. Updating the docs can be the same. >>> >> > > > >>> >> > > > If we follow Sqoop's process for example, how would small >>> >> > > > fixes/adjustments/additions to the live documentation occur >>> without >>> >> a >>> >> > new >>> >> > > > release? >>> >> > > > >>> >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < >>> wangg...@gmail.com> >>> >> > > wrote: >>> >> > > > >>> >> > > > > I am +1 on same repo too. I think keeping one git history of >>> code >>> >> / >>> >> > doc >>> >> > > > > change may actually be beneficial for this approach as well. >>> >> > > > > >>> >> > > > > Guozhang >>> >> > > > > >>> >> > > > > On Thu, Aug 6, 2015 at 9:16 AM, Gwen Shapira < >>> g...@confluent.io> >>> >> > > wrote: >>> >> > > > > >>> >> > > > > > I prefer same repo for one-commit / lower-barrier benefits. >>> >> > > > > > >>> >> > > > > > Sqoop has the following process, which decouples >>> documentation >>> >> > > changes >>> >> > > > > from >>> >> > > > > > website changes: >>> >> > > > > > >>> >> > > > > > 1. Code github repo contains a doc directory, with the >>> >> > documentation >>> >> > > > > > written and maintained in AsciiDoc. Only one version of the >>> >> > > > > documentation, >>> >> > > > > > since it is source controlled with the code. (unlike >>> current SVN >>> >> > > where >>> >> > > > we >>> >> > > > > > have directories per version) >>> >> > > > >
Re: KAFKA-2364 migrate docs from SVN to git
Hi all, It looks like it's not feasible to update the code and website in the same commit given existing limitations of the Apache infra: https://issues.apache.org/jira/browse/INFRA-10143?focusedCommentId=14703175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14703175 Best, Ismael On Wed, Aug 12, 2015 at 10:00 AM, Ismael Juma wrote: > Hi Gwen, > > I filed KAFKA-2425 as KAFKA-2364 is about improving the website > documentation. Aseem Bansal seemed interested in helping us with the move > so I pinged him in the issue. > > Best, > Ismael > > On Wed, Aug 12, 2015 at 1:51 AM, Gwen Shapira wrote: > >> Ah, there is already a JIRA in the title. Never mind :) >> >> On Tue, Aug 11, 2015 at 5:51 PM, Gwen Shapira wrote: >> >> > The vote opened 5 days ago. I believe we can conclude with 3 binding >> +1, 3 >> > non-binding +1 and no -1. >> > >> > Ismael, are you opening and JIRA and migrating? Or are we looking for a >> > volunteer? >> > >> > On Tue, Aug 11, 2015 at 5:46 PM, Ashish Singh >> wrote: >> > >> >> +1 on same repo. >> >> >> >> On Tue, Aug 11, 2015 at 12:21 PM, Edward Ribeiro < >> >> edward.ribe...@gmail.com> >> >> wrote: >> >> >> >> > +1. As soon as possible, please. :) >> >> > >> >> > On Sat, Aug 8, 2015 at 4:05 PM, Neha Narkhede >> >> wrote: >> >> > >> >> > > +1 on the same repo for code and website. It helps to keep both in >> >> sync. >> >> > > >> >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke >> >> wrote: >> >> > > >> >> > > > +1 for the same repo. The closer docs can be to code the more >> >> accurate >> >> > > they >> >> > > > are likely to be. The same way we encourage unit tests for a new >> >> > > > feature/patch. Updating the docs can be the same. >> >> > > > >> >> > > > If we follow Sqoop's process for example, how would small >> >> > > > fixes/adjustments/additions to the live documentation occur >> without >> >> a >> >> > new >> >> > > > release? >> >> > > > >> >> > > > On Thu, Aug 6, 2015 at 3:33 PM, Guozhang Wang < >> wangg...@gmail.com> >> >> > > wrote: >> >> > > > >> >> > > > > I am +1 on same repo too. I think keeping one git history of >> code >> >> / >> >> > doc >> >> > > > > change may actually be beneficial for this approach as well. >> >> > > > > >> >> > > > > Guozhang >> >> > > > > >> >> > > > > On Thu, Aug 6, 2015 at 9:16 AM, Gwen Shapira < >> g...@confluent.io> >> >> > > wrote: >> >> > > > > >> >> > > > > > I prefer same repo for one-commit / lower-barrier benefits. >> >> > > > > > >> >> > > > > > Sqoop has the following process, which decouples >> documentation >> >> > > changes >> >> > > > > from >> >> > > > > > website changes: >> >> > > > > > >> >> > > > > > 1. Code github repo contains a doc directory, with the >> >> > documentation >> >> > > > > > written and maintained in AsciiDoc. Only one version of the >> >> > > > > documentation, >> >> > > > > > since it is source controlled with the code. (unlike current >> SVN >> >> > > where >> >> > > > we >> >> > > > > > have directories per version) >> >> > > > > > >> >> > > > > > 2. Build process compiles the AsciiDoc to HTML and PDF >> >> > > > > > >> >> > > > > > 3. When releasing, we post the documentation of the new >> release >> >> to >> >> > > the >> >> > > > > > website >> >> > > > > > >> >> > > > > > Gwen >> >> > > > > > >> >> > > > > > On Thu, Aug 6, 2015 at 12:20 AM, Ismael Juma < >> ism...@juma.me.uk >
[jira] [Commented] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702665#comment-14702665 ] Manikumar Reddy commented on KAFKA-2425: Raised an INFRA-10143 ticket for this. > 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] [Assigned] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-2425: -- Assignee: Manikumar Reddy > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694929#comment-14694929 ] Ismael Juma commented on KAFKA-2425: [~omkreddy], I think it's OK because what appears under `documentation.html` is based on an include to a particular version (see the 07, 08, 081, etc. directories). So, we could still show the latest released version by default and we would have the opportunity to fix things in the documentation for released or unreleased versions. But let's see what [~gwenshap] says. > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694777#comment-14694777 ] Manikumar Reddy commented on KAFKA-2425: Yes, It is annoying. But it is not mandatory. We can request the INFRA team to use master branch. [~gwenshap], [~ijuma] After this migration, all doc changes will immediately published to kafka site. This will publish new feature docs even before official kafka release. Is that OK? [~anshbansal] Let me know if you need any help. > 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 > > 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] [Comment Edited] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693330#comment-14693330 ] Manikumar Reddy edited comment on KAFKA-2425 at 8/13/15 6:10 AM: - You can find the docs here : http://svn.apache.org/repos/asf/kafka/site Things to consider/to do: # Raise an Apache INFRA ticket to finalize the migration process. INFRA prefers new "asf-site" branch for site docs.. # checkout the site docs from svn and remove all .svn folders # open a github pull request and commit the site docs to new folder 'content' in kafka repo # Inform INFRA team to complete the migration. was (Author: omkreddy): You can find the docs here : http://svn.apache.org/repos/asf/kafka/site Things to consider/to do: # Raise an Apache INFRA ticket to finalize the migration process. INFRA prefers new "asf-site" branch for site docs.. # checkout the site docs from svn and remove all .svn folders # open a github pull request and commit the site docs # Inform INFRA team to complete the migration. > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694494#comment-14694494 ] Gwen Shapira commented on KAFKA-2425: - I guess I'm not imagining how it works correctly. Can you point me at a project that already does this, so I can see how it works? > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694393#comment-14694393 ] Ismael Juma commented on KAFKA-2425: Requiring a different branch is annoying. However, I think we can still push code and doc together [~gwenshap]. It just means that the website won't be updated until we merge the changes to the `asf-site` branch, right? Or am I missing something? Maybe this extra step is annoying enough that having all in a single repo is no longer worth it. Not sure. > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694034#comment-14694034 ] Gwen Shapira commented on KAFKA-2425: - Wouldn't a new branch mean that we can't push code and doc changes together, so the benefits of using git (or at least same repo) are reduced? > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693544#comment-14693544 ] Manikumar Reddy commented on KAFKA-2425: Issue Type can be simple "Bug". "SVN->GIT Migration" is for migrating svn repo to git repo Sample Ticket: https://issues.apache.org/jira/browse/INFRA-10032 > 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 > > 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] [Comment Edited] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693505#comment-14693505 ] Aseem Bansal edited comment on KAFKA-2425 at 8/12/15 1:54 PM: -- The Infra ticket has fields "Git Notification Mailing List" and "Git Repository Import Path". I am not sure what they are. Project: Infrastructure Issue Type: SVN->GIT Migration was (Author: anshbansal): The Infra ticket has fields "Git Notification Mailing List" and "Git Repository Import Path". I am not sure what they are. > 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 > > 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-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693505#comment-14693505 ] Aseem Bansal commented on KAFKA-2425: - The Infra ticket has fields "Git Notification Mailing List" and "Git Repository Import Path". I am not sure what they are. > 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 > > 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] [Comment Edited] (KAFKA-2425) Migrate website from SVN to Git
[ https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693330#comment-14693330 ] Manikumar Reddy edited comment on KAFKA-2425 at 8/12/15 11:24 AM: -- You can find the docs here : http://svn.apache.org/repos/asf/kafka/site Things to consider/to do: # Raise an Apache INFRA ticket to finalize the migration process. INFRA prefers new "asf-site" branch for site docs.. # checkout the site docs from svn and remove all .svn folders # open a github pull request and commit the site docs # Inform INFRA team to complete the migration. was (Author: omkreddy): You can find the docs here : http://svn.apache.org/repos/asf/kafka/site Things to consider/to do: # Raise an Apache INFRA ticket to finalize the migration process. INFRA prefers to new "asf-site" branch for site docs.. # checkout the site docs from svn and remove all .svn folders # open a github pull request and commit the site docs # Inform INFRA team to complete the migration. > 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 > > 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)
