Re: Apache Geode Branch Housekeeping
The branch named "master" claims to be mine. I don't exactly know how it became "mine". -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Thu, Nov 8, 2018 at 7:55 PM Patrick Rhomberg wrote: > Hello all! > > We currently have 182 branches on the apache/geode repository. This is > excessive. > Please fork the main repository and save your branches there. If you > must use the apache/geode repository for some reason, please be diligent in > your removal of dead branches. > > *I would like to begin removing branches soon.* > > Many branches appear to refer to JIRA tickets that are closed, or have > pull requests against them that have been merged. These seem safe to > delete. > Many branches are thousands of commits behind develop or months to even > years old. Some of these branches have no commits since they were > branched. Release branches notwithstanding, these seem relatively safe to > delete. I suspect there are some that should be maintained for legal or > legacy reasons, in which case please let me know. > > This can be done most safely if you, as a responsible developer and > reasonably-clean adult, were to pick up your own room. If you have > anything listed under "Your branches" at [1], please copy them to your fork > and remove them from apache/geode. > > Thank you. > > Imagination is Change. > ~ Patrick > > [1] https://github.com/apache/geode/branches/yours >
Re: Apache Geode Branch Housekeeping
For a matter of safety, perhaps we should as INFRA to protect those branches? > On Nov 8, 2018, at 5:04 PM, Anthony Baker wrote: > > Notes: > > - Older release/* branches may be removed. > - Do not remove branches like native-client-software-grant, sga2, > wan_cq_donation, etc. Those need to be preserved as a provenance record. > - Do not remove master or develop :-) > > > Anthony > > >> On Nov 8, 2018, at 4:55 PM, Patrick Rhomberg wrote: >> >> Hello all! >> >> We currently have 182 branches on the apache/geode repository. This is >> excessive. >> Please fork the main repository and save your branches there. If you >> must use the apache/geode repository for some reason, please be diligent in >> your removal of dead branches. >> >> *I would like to begin removing branches soon.* >> >> Many branches appear to refer to JIRA tickets that are closed, or have >> pull requests against them that have been merged. These seem safe to >> delete. >> Many branches are thousands of commits behind develop or months to even >> years old. Some of these branches have no commits since they were >> branched. Release branches notwithstanding, these seem relatively safe to >> delete. I suspect there are some that should be maintained for legal or >> legacy reasons, in which case please let me know. >> >> This can be done most safely if you, as a responsible developer and >> reasonably-clean adult, were to pick up your own room. If you have >> anything listed under "Your branches" at [1], please copy them to your fork >> and remove them from apache/geode. >> >> Thank you. >> >> Imagination is Change. >> ~ Patrick >> >> [1] https://github.com/apache/geode/branches/yours >
Re: Apache Geode Branch Housekeeping
Our release tags should already be protected. We create all of our release tags under rel/ which apache protects by default. [1] Maybe we should just create rel/XXX tags for the heads of the branches Anthony mentioned and delete the branches themselves? https://git-wip-us.apache.org/docs/switching-to-git.html#protected-ref-lists On Thu, Nov 8, 2018 at 4:55 PM Patrick Rhomberg wrote: > Hello all! > > We currently have 182 branches on the apache/geode repository. This is > excessive. > Please fork the main repository and save your branches there. If you > must use the apache/geode repository for some reason, please be diligent in > your removal of dead branches. > > *I would like to begin removing branches soon.* > > Many branches appear to refer to JIRA tickets that are closed, or have > pull requests against them that have been merged. These seem safe to > delete. > Many branches are thousands of commits behind develop or months to even > years old. Some of these branches have no commits since they were > branched. Release branches notwithstanding, these seem relatively safe to > delete. I suspect there are some that should be maintained for legal or > legacy reasons, in which case please let me know. > > This can be done most safely if you, as a responsible developer and > reasonably-clean adult, were to pick up your own room. If you have > anything listed under "Your branches" at [1], please copy them to your fork > and remove them from apache/geode. > > Thank you. > > Imagination is Change. > ~ Patrick > > [1] https://github.com/apache/geode/branches/yours >
Re: Apache Geode Branch Housekeeping
I'm pretty sure we want to keep the release tags for every release we've made, in case someone wants to check something against old releases. On Thu, Nov 8, 2018 at 5:04 PM Anthony Baker wrote: > Notes: > > - Older release/* branches may be removed. > - Do not remove branches like native-client-software-grant, sga2, > wan_cq_donation, etc. Those need to be preserved as a provenance record. > - Do not remove master or develop :-) > > > Anthony > > > > On Nov 8, 2018, at 4:55 PM, Patrick Rhomberg > wrote: > > > > Hello all! > > > > We currently have 182 branches on the apache/geode repository. This is > > excessive. > > Please fork the main repository and save your branches there. If you > > must use the apache/geode repository for some reason, please be diligent > in > > your removal of dead branches. > > > > *I would like to begin removing branches soon.* > > > > Many branches appear to refer to JIRA tickets that are closed, or have > > pull requests against them that have been merged. These seem safe to > > delete. > > Many branches are thousands of commits behind develop or months to even > > years old. Some of these branches have no commits since they were > > branched. Release branches notwithstanding, these seem relatively safe > to > > delete. I suspect there are some that should be maintained for legal or > > legacy reasons, in which case please let me know. > > > > This can be done most safely if you, as a responsible developer and > > reasonably-clean adult, were to pick up your own room. If you have > > anything listed under "Your branches" at [1], please copy them to your > fork > > and remove them from apache/geode. > > > > Thank you. > > > > Imagination is Change. > > ~ Patrick > > > > [1] https://github.com/apache/geode/branches/yours > >
Re: Apache Geode Branch Housekeeping
Notes: - Older release/* branches may be removed. - Do not remove branches like native-client-software-grant, sga2, wan_cq_donation, etc. Those need to be preserved as a provenance record. - Do not remove master or develop :-) Anthony > On Nov 8, 2018, at 4:55 PM, Patrick Rhomberg wrote: > > Hello all! > > We currently have 182 branches on the apache/geode repository. This is > excessive. > Please fork the main repository and save your branches there. If you > must use the apache/geode repository for some reason, please be diligent in > your removal of dead branches. > > *I would like to begin removing branches soon.* > > Many branches appear to refer to JIRA tickets that are closed, or have > pull requests against them that have been merged. These seem safe to > delete. > Many branches are thousands of commits behind develop or months to even > years old. Some of these branches have no commits since they were > branched. Release branches notwithstanding, these seem relatively safe to > delete. I suspect there are some that should be maintained for legal or > legacy reasons, in which case please let me know. > > This can be done most safely if you, as a responsible developer and > reasonably-clean adult, were to pick up your own room. If you have > anything listed under "Your branches" at [1], please copy them to your fork > and remove them from apache/geode. > > Thank you. > > Imagination is Change. > ~ Patrick > > [1] https://github.com/apache/geode/branches/yours
