+1 From: crowbar-bounces On Behalf Of Williams, J T Sent: Friday, March 21, 2014 1:27 PM To: j...@suse.de; crowbar Subject: Re: [Crowbar] Removing branches fully merged into "master".
Dell - Internal Use - Confidential I am not arguing the point that anything will be lost. I agree that with the tags, nothing will be lost. I am only voicing the concerns of the team who uses the branches that I mentioned as "not to delete" on a regular basis for supporting their hadoop customers on different releases. In our view, the benefit to the team to leave the branches in place for quick customer support of their different hadoop releases has more benefit than the arguments posed here. Basically the branches listed have become maintenance (sustaining) branches for several team members. While they look to be dead, I was assured that the team works on these branches and thus they requested that they not to be deleted. Outside of the previously listed branches, all other actions listed in the spreadsheet please feel free to move forward on. -----Original Message----- From: J. Daniel Schmidt [mailto:j...@suse.de] Sent: Friday, March 21, 2014 9:23 AM To: crowbar Cc: Williams, J T; tboer...@suse.de<mailto:tboer...@suse.de>; aspi...@suse.com<mailto:aspi...@suse.com> Subject: Re: [Crowbar] Removing branches fully merged into "master". Just a short reply on behalf of Thomas: On Friday 21 March 2014 08:43:57 j_t_willi...@dell.com<mailto:j_t_willi...@dell.com> wrote: > 3) It is tested and validated that we are capable of recreating our > releases. You can recreate any branch at any time. Nothing will be lost. > · Do not delete pebbles and fred - they are earlier versions of Hadoop. > > · Do not delete anything with a hadoop- prefix - These are locked version of > in-field code. > > · Do not delete the ApacheHadoop repo - it is a meta barclamp with > referenced dependencies and the build will break if you do. Nothing will be deleted at all. Branches that are dead or unused will be tagged and the branch will be removed. Note: In git a branch is a reference to a commit. Same for tags. The difference: A branch is moving (updated with each commit, thus tracking work-in-progress) and a tag is static. No repo, commit or line of code will be deleted. Just some branches are switched to tags. And if you need to work on such a tagged tree again in the future, you can recreate the branch anytime to indicate that there is work going on in this tree. > For our assurances, you will be tagging the branch head prior to any > branch deletion. Is this correct? That is what all this is about. Its about to create tags. Ciao, Daniel -- J. Daniel Schmidt <j...@suse.de<mailto:j...@suse.de>> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
