Re: [VOTE] change Default branch for geode-examples to 'develop'
Hi @Xiaojian, it's unclear what your -1 refers to. This VOTE has already closed. Perhaps you were just expressing content for keeping geode-examples a separate repo? When you checkout geode-examples, your first stop will likely be the README, which describes how to select the desired version of examples and desired version of Geode. More examples are always welcome! Feel free to submit a PR if you have some you would like to contribute. On 7/31/20, 11:02 AM, "Xiaojian Zhou" wrote: -1 I often need to build geode-examples on older geode version (more frequent than current version). One more irrelevant comments: we do need to enhance our geode-examples. The current examples are too weak. On 7/30/20, 8:16 AM, "Blake Bender" wrote: FWIW, Geode Native works around this by not keeping a separate examples repo at all. To build our examples, you *must* build your own Geode Native "installation," which includes the examples tree, or download the desired tarball/zip file from our GitHub releases. I’m pretty much agnostic as to which way we should go for any particular repository, which is why I wrote "remove or rename" in the title of GEODE-8335. Let's do the right thing for each repo, but not expend a ton of brain power on it. I brought this up as a *small* gesture we should make in the name of kindness, not a large effort. Thanks, Blake On 7/18/20, 2:42 AM, "Owen Nichols" wrote: Voting Results: +1: 5 votes 0: 0 votes -1: 1 vote The voting is successful by majority vote. INFRA has completed the requested change and git clone g...@github.com:apache/geode-examples.git now checks out develop, making geode-examples consistent with all other geode- projects, and clearing the way to eliminate master from all projects if @Blake or anyone else would like to move forward on that. Although it didn't seem to sway anyone else, let's still attempt to discuss/address @Anthony's concern that develop doesn't pair well with released versions of Geode. Maybe the brew install + git clone workflow is not how we want to introduce an application developer to Geode. We could suggest: if cloning from git, clone everything from git; if using released artifacts, use release artifacts for everything. If mix-n-match is necessary, the README.md could explain how to check out the correct branch or tag (or specify the Geode version parameter in the gradle command) to match the installed version of Geode. It's important and fundamental for application developers to be aware that client version must be <= server version, so perhaps it's beneficial to document that from the beginning. Another idea might be improving the error message when the client version is too new? We could also modify the release scripts to substitute the latest release version into the README as part of the release process, to keep the out-of-the-box experience as simple as copy-and-pasting a gradle command from the README. @Anthony I'd be happy to pair with you on updating the README or any other scripts/documentation. If anyone else has thoughts or ideas, please chime in. On 7/14/20, 7:16 AM, "Anthony Baker" wrote: Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony > On Jul 9, 2020, at 9:39 PM, Owen Nichols wrote: > > A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. > > [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Conichols%40vmware.com%7C19c883ecbe424f985a9f08d8357bdb52%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637318153360040138sdata=VRHfJDeh7MBHCe4ZeyShazLqjKU5nUjnfmTDW5tY1SI%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
-1 I often need to build geode-examples on older geode version (more frequent than current version). One more irrelevant comments: we do need to enhance our geode-examples. The current examples are too weak. On 7/30/20, 8:16 AM, "Blake Bender" wrote: FWIW, Geode Native works around this by not keeping a separate examples repo at all. To build our examples, you *must* build your own Geode Native "installation," which includes the examples tree, or download the desired tarball/zip file from our GitHub releases. I’m pretty much agnostic as to which way we should go for any particular repository, which is why I wrote "remove or rename" in the title of GEODE-8335. Let's do the right thing for each repo, but not expend a ton of brain power on it. I brought this up as a *small* gesture we should make in the name of kindness, not a large effort. Thanks, Blake On 7/18/20, 2:42 AM, "Owen Nichols" wrote: Voting Results: +1: 5 votes 0: 0 votes -1: 1 vote The voting is successful by majority vote. INFRA has completed the requested change and git clone g...@github.com:apache/geode-examples.git now checks out develop, making geode-examples consistent with all other geode- projects, and clearing the way to eliminate master from all projects if @Blake or anyone else would like to move forward on that. Although it didn't seem to sway anyone else, let's still attempt to discuss/address @Anthony's concern that develop doesn't pair well with released versions of Geode. Maybe the brew install + git clone workflow is not how we want to introduce an application developer to Geode. We could suggest: if cloning from git, clone everything from git; if using released artifacts, use release artifacts for everything. If mix-n-match is necessary, the README.md could explain how to check out the correct branch or tag (or specify the Geode version parameter in the gradle command) to match the installed version of Geode. It's important and fundamental for application developers to be aware that client version must be <= server version, so perhaps it's beneficial to document that from the beginning. Another idea might be improving the error message when the client version is too new? We could also modify the release scripts to substitute the latest release version into the README as part of the release process, to keep the out-of-the-box experience as simple as copy-and-pasting a gradle command from the README. @Anthony I'd be happy to pair with you on updating the README or any other scripts/documentation. If anyone else has thoughts or ideas, please chime in. On 7/14/20, 7:16 AM, "Anthony Baker" wrote: Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony > On Jul 9, 2020, at 9:39 PM, Owen Nichols wrote: > > A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. > > [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Czhouxh%40vmware.com%7Cd42c339465e54b6ad5af08d8349b7bc4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317189691026288sdata=iQD%2F3%2Bw4LXhrI6dczqML2vm%2Fc72YyKO80ueOu4elViI%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
FWIW, Geode Native works around this by not keeping a separate examples repo at all. To build our examples, you *must* build your own Geode Native "installation," which includes the examples tree, or download the desired tarball/zip file from our GitHub releases. I’m pretty much agnostic as to which way we should go for any particular repository, which is why I wrote "remove or rename" in the title of GEODE-8335. Let's do the right thing for each repo, but not expend a ton of brain power on it. I brought this up as a *small* gesture we should make in the name of kindness, not a large effort. Thanks, Blake On 7/18/20, 2:42 AM, "Owen Nichols" wrote: Voting Results: +1: 5 votes 0: 0 votes -1: 1 vote The voting is successful by majority vote. INFRA has completed the requested change and git clone g...@github.com:apache/geode-examples.git now checks out develop, making geode-examples consistent with all other geode- projects, and clearing the way to eliminate master from all projects if @Blake or anyone else would like to move forward on that. Although it didn't seem to sway anyone else, let's still attempt to discuss/address @Anthony's concern that develop doesn't pair well with released versions of Geode. Maybe the brew install + git clone workflow is not how we want to introduce an application developer to Geode. We could suggest: if cloning from git, clone everything from git; if using released artifacts, use release artifacts for everything. If mix-n-match is necessary, the README.md could explain how to check out the correct branch or tag (or specify the Geode version parameter in the gradle command) to match the installed version of Geode. It's important and fundamental for application developers to be aware that client version must be <= server version, so perhaps it's beneficial to document that from the beginning. Another idea might be improving the error message when the client version is too new? We could also modify the release scripts to substitute the latest release version into the README as part of the release process, to keep the out-of-the-box experience as simple as copy-and-pasting a gradle command from the README. @Anthony I'd be happy to pair with you on updating the README or any other scripts/documentation. If anyone else has thoughts or ideas, please chime in. On 7/14/20, 7:16 AM, "Anthony Baker" wrote: Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony > On Jul 9, 2020, at 9:39 PM, Owen Nichols wrote: > > A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. > > [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cbblake%40vmware.com%7Cb2eb424632174cd66c2408d82afee313%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637306621505139591sdata=DWUOSFvwEnJDJytU7qSjrzFEzR8gzjIm96pXAOqnxUQ%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
-1. Happy to change my mind if there’s a user-friendly way to deal with the scenario I mentioned below. Anthony On Jul 14, 2020, at 8:40 AM, Owen Nichols mailto:onich...@vmware.com>> wrote: Hi Anthony, there is a separate discuss thread [1] for this topic. This is the vote thread for the ASF INFRA ticket [2] to make this one specific change that came out of the discussion. Your input is valuable and I encourage you to both vote on this thread and continue the conversation on the discuss thread. [1] https://lists.apache.org/thread.html/rfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%3Cdev.geode.apache.org%3E [2] https://issues.apache.org/jira/browse/INFRA-20510 On 7/14/20, 7:16 AM, "Anthony Baker" mailto:bak...@vmware.com>> wrote: Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony On Jul 9, 2020, at 9:39 PM, Owen Nichols mailto:onich...@vmware.com>> wrote: A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cbakera%40vmware.com%7Ce9db02c2e21544dc02e608d8280c43d6%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637303380464893583sdata=1dCB0szNtuImpKWBSaL9ntHFY6z1KCVJWusiT5%2BEO0I%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
Hi Anthony, there is a separate discuss thread [1] for this topic. This is the vote thread for the ASF INFRA ticket [2] to make this one specific change that came out of the discussion. Your input is valuable and I encourage you to both vote on this thread and continue the conversation on the discuss thread. [1] https://lists.apache.org/thread.html/rfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%3Cdev.geode.apache.org%3E [2] https://issues.apache.org/jira/browse/INFRA-20510 On 7/14/20, 7:16 AM, "Anthony Baker" wrote: Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony > On Jul 9, 2020, at 9:39 PM, Owen Nichols wrote: > > A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. > > [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Conichols%40vmware.com%7C0b94a8d480c948973a7008d828007e43%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637303329899842884sdata=pc1oOl0IBQITxVBWsPqfToAjHADHBKMFygzatJz2vA0%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
+1 On Fri, 10 Jul 2020 at 15:52, Alberto Bustamante Reyes wrote: > +1 > > De: Joris Melchior > Enviado: viernes, 10 de julio de 2020 15:54 > Para: dev@geode.apache.org > Asunto: Re: [VOTE] change Default branch for geode-examples to 'develop' > > +1 > > On 2020-07-10, 12:39 AM, "Owen Nichols" wrote: > > A fresh checkout of geode and all but one geode- repos > checks out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in > favor of changing its Default branch to develop for consistency with the > other repos and other reasons as per recent discussion[1]. > > [1] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cjmelchior%40vmware.com%7C458c4abf934b43480f2308d8248b403a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527784977071sdata=7CRcXQYAkbVtQ5CMFZgKZCMtfyqHw2UxkNPA4KwSl8k%3Dreserved=0 > > -- Ju@N
Re: [VOTE] change Default branch for geode-examples to 'develop'
Consider the use case of an application developer who wants to run geode-examples against the latest geode release: 1) brew install apache-geode 2) git clone geode-examples 3) Get some runtime errors because geode-examples won’t connect to a previous geode release At this point, you have to do some detective work to either download the geode-examples from the corresponding source release or switch over to the appropriate git tag. I think there’s value in maintaining a default branch of geode-examples that tracks the latest release. Anthony > On Jul 9, 2020, at 9:39 PM, Owen Nichols wrote: > > A fresh checkout of geode and all but one geode- repos checks > out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of > changing its Default branch to develop for consistency with the other repos > and other reasons as per recent discussion[1]. > > [1] > https://lists.apache.org/x/thread.html/rfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee@%3Cdev.geode.apache.org%3E
RE: [VOTE] change Default branch for geode-examples to 'develop'
+1 De: Joris Melchior Enviado: viernes, 10 de julio de 2020 15:54 Para: dev@geode.apache.org Asunto: Re: [VOTE] change Default branch for geode-examples to 'develop' +1 On 2020-07-10, 12:39 AM, "Owen Nichols" wrote: A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cjmelchior%40vmware.com%7C458c4abf934b43480f2308d8248b403a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527784977071sdata=7CRcXQYAkbVtQ5CMFZgKZCMtfyqHw2UxkNPA4KwSl8k%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
+1 On 2020-07-10, 12:39 AM, "Owen Nichols" wrote: A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cjmelchior%40vmware.com%7C458c4abf934b43480f2308d8248b403a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527784977071sdata=7CRcXQYAkbVtQ5CMFZgKZCMtfyqHw2UxkNPA4KwSl8k%3Dreserved=0
Re: [VOTE] change Default branch for geode-examples to 'develop'
+1 > On Jul 9, 2020, at 10:04 PM, Dick Cavender wrote: > > +1 > > -Original Message- > From: Owen Nichols > Sent: Thursday, July 9, 2020 9:39 PM > To: dev@geode.apache.org > Subject: [VOTE] change Default branch for geode-examples to 'develop' > > A fresh checkout of geode and all but one geode- repos checks > out develop as the Default branch. > > The lone exception is geode-examples. Please vote +1 if you are in favor of > changing its Default branch to develop for consistency with the other repos > and other reasons as per recent discussion[1]. > > [1] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cdickc%40vmware.com%7C1a703cc22f784158523008d8248b4188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527805384154sdata=9BABTC6ROp6h3hD7lsOkezesyc%2BuJFAFQB08BFL7O%2FE%3Dreserved=0
RE: [VOTE] change Default branch for geode-examples to 'develop'
+1 -Original Message- From: Owen Nichols Sent: Thursday, July 9, 2020 9:39 PM To: dev@geode.apache.org Subject: [VOTE] change Default branch for geode-examples to 'develop' A fresh checkout of geode and all but one geode- repos checks out develop as the Default branch. The lone exception is geode-examples. Please vote +1 if you are in favor of changing its Default branch to develop for consistency with the other repos and other reasons as per recent discussion[1]. [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cdickc%40vmware.com%7C1a703cc22f784158523008d8248b4188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527805384154sdata=9BABTC6ROp6h3hD7lsOkezesyc%2BuJFAFQB08BFL7O%2FE%3Dreserved=0
