On 2007-03-07 10:34:47 +0000, Dave Shield wrote:
> The recent conversion of the Net-SNMP source code repository
> to be under the control of Subversion has done an outstanding
> job of retaining the previous CVS development history.
>    However, I would suggest that the 'tags' and 'branches'
> trees contain a large amount of stuff that is redundant and/or
> confusing.   I propose that we should clean things up a bit,
> separating out the main releases and development lines from
> all the historical crud (which could either be moved aside,
> or deleted altogether).
> 
> In particular, I propose the following:
> 
> 1) branches:
>     a)  Retain V5-{2,3,4}-branches as currently

i would propose to change the names to:
net-snmp-5.{2,3,4}.x

>     b)  Move the following to a new directory ('closed')
>             V3-line
>             V4-0-line
>             V4-1-1-patches,
>             V4-2-patches,
>             V5-0-patches

just delete them. you can undo the deletion if needed in one svn merge
cmdline.

>             V5-1-patches

can we leave that open for a bit more time. i could at least put all the
our patches for 5.1 into it.

>     b') Move the following to either b) or c):
>             V-5-0-10-patches    (rename to V5-0-10-patches?)
>             V-5-2-1-patches      (rename to V5-2-1-patches?)
>             V5-1-3-patches
>             V5-3-0-patches

what makes those branches different to the branches in a) ?
shouldnt the content be in the branches from a) aswell?

>     c) Move all remaining branches to a new directory ('old')
>     d) Delete some/all branches from c)

just delete the unused branches. you can undo the deletion if needed in
one svn merge cmdline. i would only keep them directly visible if you
need them (to lookup stuff or so)

> 2) tags:
>     a) Retain all tags of the form
>             Ext-{3,4,5}-X
>             Ext-{3,4,5}-X-Y
>             Ext-{3,4,5}-X-Y-Z
>         as currently
>     b) Move all tags of the form
>             Ext-....-preN
>             Ext-...rcN
>          to a new directory ('pre-release')
>     b') Delete some/all pre-release tags
>     c)  Move all remaining tags to a new directory ('misc')
>     d)  Delete some/all tags from c)

many of those "tags" seems to be kind of release branches. i would just
delete them. I doubt anyone is interested in tags for some prerelease
stuff.

> That should end up with a much cleaner framework.

agreed. :)

> I'm unconvinced whether it's worth keeping most of
> the "temporary" tags and branches (which would be
> mostly the stuff under 1c) and 2c) above)
>
> I'm also inclined to drop all the pre-release tags
> once the corresponding full release has been made.
> But separating these out from the full releases
> would be a reasonable compromise, if it was felt
> worth keeping them.

what arguments do you have for keeping them?

    darix

-- 
          openSUSE - SUSE Linux is my linux
              openSUSE is good for you
                  www.opensuse.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to