Jon,

I agree so long as the history kept does not turn into hoarding. In a year, the 
android-api branch will be nothing but bloat as people forget what it contained.

If no one wants the branch, we should clean it up now.

If we keep the branch, we need to make one last commit that contains a 
README.BRANCH file that carries a synopsis of the branches purpose, warning on 
staleness and a please keep until date. Then, the branch can be locked. If we 
cannot lock it, the branch is a potential hazard.

No future maintainer should be burdened with researching when a branch can be 
garbage collected.

Pat

> -----Original Message-----
> From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-
> bounces at lists.iotivity.org] On Behalf Of Jon A. Cruz
> Sent: Thursday, May 21, 2015 5:57 PM
> To: iotivity-dev at lists.iotivity.org; Keane, Erich
> Subject: Re: [dev] removal of the android_api branch
> 
> On 05/21/2015 11:54 AM, Kourt, Tim A wrote:
> > Hi All,
> >
> > To eliminate any further confusion, we would like to delete the
> android_api branch as it is no longer properly maintained.
> >
> > Uze, please let Pat, Erich know once you are done with it and it can be
> safely deleted.
> >
> 
> Hi,
> 
> In general I like to see history preserved in SCM, especially when it comes to
> tracking things like cross-platform changes. Might it be sufficient to just 
> lock
> the branch and not delete it completely?
> 
> Deleting a branch from Git after it has been pushed publicly might present
> certain issues (though removing a commit definitely does). It starts to head
> off into areas similar to using the 'obliterate' command in Perforce (hint: 
> that
> one should be an extreme exception to common practice).
> 
> I seem to recall that a pre or post commit hook might do the job of
> preventing further changes.
> 
> 
> --
> Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group
> jonc at osg.samsung.com
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to