On Tue, Aug 17, 2010 at 05:33:13PM -0500, Hyrum K. Wright wrote:
> It's that time again!  In looking at the list of current branches
> (excepting release and backport branches I've noticed several which
> look to be abandoned or unmaintained.  Branches which have not been
> touched in over a year include (along with author and date of last
> revision, stolen from ViewVC):
> 
>   artem-soc-work/      r863880         3 years         djames  Really, 
> actually, merge
> r23802 and r23803 from trunk to the artem-soc-work branc…
>   atomic-revprop/      r984264         6 days  danielsh        Tweak the 
> behaviour of a
> recently-added API to allow conveniently passing errors…
>   bdb-fixes/   r858217         4 years         brane   Working on issue 
> #2449. Move
> error_info refcount management where it belongs, t…
>   capabilities-abstraction/    r869334         2 years         kfogel  On the
> capabilities-abstraction branch: Start unifying some of the
> capabilities…
>   issue-2699-dev/      r863182         3 years         dlr     On the 
> issue-2699-dev
> branch: Improve locking error message. * subversion/libsv…
>   issue-2897/  r869309         2 years         kameshj         On the 
> issue-2897 branch:
> Improve documentation. * subversion/libsvn_client/me…
>   issue-2897-take2/    r875276         19 months       kameshj         On 
> issue-2897-take2:
> Merge from ^/trunk revisions r35038 through r35201.
>   issue-3081/  r869126         2 years         kfogel  On the issue-3081 
> branch: *
> 3081-repro/: New directory, with patches, repro scr…
>   meta-data-versioning/        r858153         4 years         pmarek  Change 
> the "live"
> properties only if they have really changed. Without this chan…
>   perl-bindings-improvements/  r867175         2 years         jpeacock       
>  Merge with
> tr...@27098
>   record_exact_merge_and_commit_revs/  r868556         2 years         
> kameshj         On
> the 'record_exact_merge_and_commit_revs' branch, merge 28395:28481
> from /trun…
>   scheme-bindings/     r869778         2 years                
>   scons-build-system/  r862146         3 years         danderson       Make 
> the source
> path creator safer. * build/builder.py (SvnBuild._make_src_…
>   server-l10n/         r857339         4 years         dlr     * 
> subversion/mod_dav_svn/lang.c
> (sort_lang_pref): Swap return values to correc…
>   status--filter/      r867402         2 years         epg     *** Just 
> stashing this away
> until after 1.5 branches. Add status --filter, for …
>   svnserve-ssl/        r859467         4 years         mbk     Make svnserve 
> SSL config items
> repo-conf-dir-relative, rather than absolute path…
>   youngest-common-ancestor/    r867405         2 years         cmpilato       
>  Begin work on
> a client-side youngest-common-ancestor API. NOTE: This code is…

That list is quite hard to read here.
Here's a shorter alternative (svn ls -v ^/subversion/branches):

 986608 stefan2               Aug 18 11:29 ./
 873205 hwright               Sep 17  2008 1.0.x/
 873092 cmpilato              Sep 10  2008 1.1.x/
 873092 cmpilato              Sep 10  2008 1.2.x/
 873208 hwright               Sep 17  2008 1.3.x/
 904181 philip                Jan 28  2010 1.4.x/
 904182 philip                Jan 28  2010 1.5.x/
 875595 stylesen              Jan 28  2009 1.5.x-issue2489/
 877232 pburba                Apr 10  2009 1.5.x-issue3392/
 876852 pburba                Mar 25  2009 1.5.x-r36775/
 877215 cmpilato              Apr 09  2009 1.5.x-r37137/
 877733 stylesen              May 09  2009 1.5.x-r37646/
 877856 pburba                May 19  2009 1.5.x-r37779/
 879745 pburba                Sep 29  2009 1.5.x-r39109/
 880457 stsp                  Nov 05  2009 1.5.x-r40200/
 984934 danielsh              Aug 12 21:54 1.6.x/
 956644 pburba                Jun 21 19:16 1.6.x-issue3242-reintegrate/
 958108 pburba                Jun 25 22:42 1.6.x-issue3646/
 964472 pburba                Jul 15 17:47 1.6.x-issue3648/
 966852 pburba                Jul 22 22:43 1.6.x-issue3657/
 966542 stylesen              Jul 22 10:45 1.6.x-issue3683/
 879771 stylesen              Sep 30  2009 1.6.x-r39692/
 981459 stsp                  Aug 02 13:25 1.6.x-r980811/
 981926 danielsh              Aug 03 17:23 1.6.x-r981921/
 929382 peters                Mar 31 07:13 1.6.x-wc-ng-error/
 863880 djames                Mar 14  2007 artem-soc-work/
 984264 danielsh              Aug 11 01:26 atomic-revprop/
 881688 cmpilato              Nov 18  2009 authz-overhaul/
 858217 brane                 Jan 18  2006 bdb-fixes/
 869334 kfogel                Feb 10  2008 capabilities-abstraction/
 929295 pburba                Mar 30 23:22 fs-successor-ids/
 984925 hwright               Aug 12 21:26 ignore-mergeinfo/
 863182 dlr                   Jan 19  2007 issue-2699-dev/
 869309 kameshj               Feb 08  2008 issue-2897/
 875276 kameshj               Jan 13  2009 issue-2897-take2/
 869126 kfogel                Jan 26  2008 issue-3081/
 892311 cmpilato              Dec 18  2009 issue-3550-dev/
 858153 pmarek                Jan 12  2006 meta-data-versioning/
 889314 philip                Dec 10  2009 obliterate-like-deltify/
 986608 stefan2               Aug 18 11:29 performance/
 867175 jpeacock              Oct 11  2007 perl-bindings-improvements/
 956582 hwright               Jun 21 15:38 py-tests-as-modules/
 929295 pburba                Mar 30 23:22 python-3-compatibility/
 868556 kameshj               Dec 14  2007 record_exact_merge_and_commit_revs/
 869778  ?                    Mar 05  2008 scheme-bindings/
 862146 danderso              Oct 21  2006 scons-build-system/
 857339 dlr                   Nov 09  2005 server-l10n/
 867402 epg                   Oct 23  2007 status--filter/
 859467 mbk                   Apr 16  2006 svnserve-ssl/
 867405 cmpilato              Oct 23  2007 youngest-common-ancestor/

> Could folks take a look at these branches and justify their continued
> existence?  It would also be nice to include plans to continue working
> on them, or issues which keep them from being merged to trunk.

The two that belong to me (1.5.x-r40200 and 1.6.x-r980811) should stay.
They both have nominations sitting in their release branch's STATUS files.

Stefan

Reply via email to