On 16 Jan 2007, David Allouche <email address hidden> wrote:
> That's an intriguing suggestion.
>
> It would have to be done in a way compatible with bug 79493 (highlight
> important branches).
>
> My gut feeling is that branch which had no new revisions (per branch
> scanner) in "some time" could be marked with an extra attribute, to
> preserve the user-specified status. I am not sure how that should be
> displayed in the UI.
Yes. I talked briefly with Tim about this yesterday.
I think they could be displayed in any of these ways:
* pushed to the bottom of the list
* showed faded out (eg with text in 80% gray not black)
* hidden by default unless you choose a "show inactive branches" option
The first two would probably only be understandable if you have an
indication of when the branch was last modified.
I think for these purposes it would be ok to take the last change date
as either
* the date of the last revision
* or the date the branch was last seen to change
whichever is easier. The case of a branch which is updated by pulling
very old revisions is negligible.
On 16 Jan 2007, David Allouche <email address hidden> wrote:
> That's an intriguing suggestion.
>
> It would have to be done in a way compatible with bug 79493 (highlight
> important branches).
>
> My gut feeling is that branch which had no new revisions (per branch
> scanner) in "some time" could be marked with an extra attribute, to
> preserve the user-specified status. I am not sure how that should be
> displayed in the UI.
Yes. I talked briefly with Tim about this yesterday.
I think they could be displayed in any of these ways:
* pushed to the bottom of the list
* showed faded out (eg with text in 80% gray not black)
* hidden by default unless you choose a "show inactive branches" option
The first two would probably only be understandable if you have an
indication of when the branch was last modified.
I think for these purposes it would be ok to take the last change date
as either
* the date of the last revision
* or the date the branch was last seen to change
whichever is easier. The case of a branch which is updated by pulling
very old revisions is negligible.
--
Martin