Tickets :: [#3704] Re-write branch finding algorithm

6.0.0-alpha10

5/15/25

Summary	Re-write branch finding algorithm
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	selsky (at) columbia (dot) edu
Created	03/28/2006 (6988 days ago)
Due
Updated	11/09/2008 (6031 days ago)
Assigned	05/08/2006 (6947 days ago)
Resolved	11/09/2008 (6031 days ago)
Milestone
Patch	No

11/09/2008 02:42:10 AM	Chuck Hagenbuch	Comment #11 State ⇒ Resolved	Reply to this comment
Calling this done.

10/29/2007 03:05:29 AM	Chuck Hagenbuch	Comment #10 Taken from Horde Developers State ⇒ Stalled	Reply to this comment
I don't think this will happen anytime soon, and I'm not sure when it's going to be worth someone's time honestly.

05/18/2006 03:17:56 PM	Chuck Hagenbuch	Comment #9 Version ⇒ HEAD Queue ⇒ Horde Framework Packages	Reply to this comment
This is an issue for the VC:: package now.

05/18/2006 03:17:20 PM	Chuck Hagenbuch	Summary ⇒ Re-write branch finding algorithm

05/08/2006 03:34:31 PM	Jan Schneider	Assigned to Horde Developers State ⇒ Assigned

04/13/2006 09:00:26 PM	Jan Schneider	Comment #8	Reply to this comment
Finally there are several branch points shown for FW_3 which is not correct. I either don't understand correctly, or I don't see this. I don't see this anymore either. Well possible that I confused this with the different FW_3_RC* branches.

04/13/2006 05:39:57 PM	Chuck Hagenbuch	Comment #7	Reply to this comment
Yes, it should appear as a tag in the all-branches-view, like the branch point of FRAMEWORK_3. Our branch-finding relies on there being a branches: line in the log for the relevant revision, which the branch point for FRAMEWORK_3_0 does not have. I guess we need to change how we find branches? And in the branch view, it shouldn't show HEAD revisions after the FW_3 branch point, which is the branch we branched FW_3_0 off. This should be fixed now. Finally there are several branch points shown for FW_3 which is not correct. I either don't understand correctly, or I don't see this.

04/13/2006 08:12:40 AM	Jan Schneider	Comment #6	Reply to this comment
Yes, it should appear as a tag in the all-branches-view, like the branch point of FRAMEWORK_3. And in the branch view, it shouldn't show HEAD revisions after the FW_3 branch point, which is the branch we branched FW_3_0 off. Finally there are several branch points shown for FW_3 which is not correct.

04/13/2006 12:30:39 AM	Chuck Hagenbuch	Comment #5	Reply to this comment
Given that, is there actually any broken behavior here now?

04/12/2006 10:58:57 PM	Jan Schneider	Comment #4	Reply to this comment
There is nothing strange about it. The branch was created but there never was a change committed to that branch.

04/03/2006 06:38:30 PM	Chuck Hagenbuch	Comment #3 State ⇒ Feedback	Reply to this comment
Something is very odd in that file - looking directly at the ,v file in the repository, FRAMEWORK_3_0 shows up in the symbols section, but there's no revision in the file to match. Having just HEAD would be a seperate enhancement, guess it makes sense.

03/30/2006 05:23:10 AM	Matt Selsky	Comment #2	Reply to this comment
Not sure if it is related or not, but there's no option to choose just the HEAD branch...

03/28/2006 06:43:07 PM	Matt Selsky	Comment #1 Priority ⇒ 1. Low State ⇒ Queue ⇒ Chora Type ⇒ Bug Summary ⇒ Branch selector doesn't always work	Reply to this comment
On the file list page (eg: http://cvs.horde.org/ingo/docs/CHANGES): 1) Select the FRAMEWORK_3_0 branch in the drop-down 2) It shows the FRAMEWORK_3 branch instead