Dell - Internal Use - Confidential Thomas, I have received word from our development teams. Here is the view our leadership team asserted that we need to address to ensure that we can quickly respond and support deployments in the field. We should not be taking chances with our code trees unless
1) There is a significant benefit to doing this 2) We understand exactly what is going to occur and what it's repercussions are 3) It is tested and validated that we are capable of recreating our releases. Outside of clearing up community confusion, I see no significant benefit to doing this. And even though we know what is going to occur and it's repercussion, we don't have time to invest in testing and validating that we can quickly recreate our releases. Therefore, based on their concerns, we do not want any changes made at this time to fred, pebbles, hadoop* or the ApacheHadoop repo. · 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. For our assurances, you will be tagging the branch head prior to any branch deletion. Is this correct? -John From: crowbar-bounces On Behalf Of Williams, J T Sent: Wednesday, March 19, 2014 10:46 AM To: tboer...@suse.de<mailto:tboer...@suse.de>; aspi...@suse.com<mailto:aspi...@suse.com> Cc: crowbar Subject: Re: [Crowbar] Removing branches fully merged into "master". Dell - Internal Use - Confidential Thomas, Give me another day to get a response from Dell's internal development team before taking any actions. I have sent out an internal email detail the actions you wish to take but need a day to receive and correlate the email responses. -John -----Original Message----- From: crowbar-bounces On Behalf Of Thomas Boerger Sent: Tuesday, March 18, 2014 12:32 PM To: Thomas Boerger Cc: crowbar Subject: Re: [Crowbar] Removing branches fully merged into "master". Reminder: I want to start tagging and removing the mentioned branches tomorrow. Quoting Thomas Boerger <tboer...@suse.de<mailto:tboer...@suse.de>>: > I have created a Gist with all branches of all barclamps. There you > can see what i think we should do with all these branches. > > https://gist.githubusercontent.com/tboerger/c959c41134cf39c5f409/raw/d > 59b2d250b6fbd323747ef4fe6843326e8edfc0e/gistfile1.txt > > I want to start with it on 19th March if nobody say something > important on that. > > > Thomas > > On Wednesday, March 12, 2014 10:35:15 AM Thomas Boerger wrote: >> Guys, are you serious? we started this thread multiple months ago and >> nobody really cared about it. And now we need to create again >> multiple lists for repositories you don't work with anymore? >> >> And even if some of the old release branches need a bugfix you can >> easily create branch out of the tag again. >> >> On Tuesday, March 11, 2014 09:05:28 AM >> j_t_willi...@dell.com<mailto:j_t_willi...@dell.com> wrote: >> > Dell - Internal Use - Confidential >> > I concur with Adam that we need a list of branches you wish to remove. >> > The hadoop branches 2.3 & 2.4 are relatively new and should not be >> > deleted. > > -- > Thomas Boerger <tboer...@suse.de<mailto:tboer...@suse.de>> > Research & Development > > SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany HRB > 16746 (AG Nürnberg), GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer _______________________________________________ Crowbar mailing list Crowbar@dell.com<mailto:Crowbar@dell.com> https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
