Package branch merges not automatically detected

I'm not sure how this is /meant/ to work... Tim / Aaron - do you know ?

After it's merged, a branch is supposed to become "Merged" in the listings: https://code.launchpad.net/people/+me. I've stumbled upon this bug yesterday. Setting the status to "Confirmed" to keep it from closing automatically.

On Tue, Mar 1, 2011 at 3:10 PM, Артём Попов <email address hidden> wrote:
> After it's merged, a branch is supposed to become "Merged" in the
> listings: https://code.launchpad.net/people/+me. I've stumbled upon this
> bug yesterday. Setting the status to "Confirmed" to keep it from closing
> automatically.

If they don't commit the merge to the target branch - and uploading is
not the same as committing - then its not clear that this is what
should happen.

OK... found the issue, and it is hanging over from the package branch original days.

The scanner detects merges of proposals, and will mark the branch as merged if the target of the proposal is a series branch.

However, is_series_branch currently says (in lib/lp/codehosting/scanner/mergedetection.py):
def is_series_branch(branch):
    """Is 'branch' associated with a series?"""
    # XXX: JonathanLange 2009-05-07 spec=package-branches: This assumes that
    # we only care about whether a branch is a product series. What about poor
    # old distroseries?
    return branch.associatedProductSeries().count() > 0

The method should be updated to also check the branch.associatedSuiteSourcePackages()