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" <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 <onich...@vmware.com> wrote:
    > 
    > A fresh checkout of geode and all but one geode-<relatedproject> 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%253E&amp;data=02%7C01%7Conichols%40vmware.com%7C0b94a8d480c948973a7008d828007e43%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637303329899842884&amp;sdata=pc1oOl0IBQITxVBWsPqfToAjHADHBKMFygzatJz2vA0%3D&amp;reserved=0


Reply via email to