Shouldn't "bzr update" pull tags in checkouted wt?

[Jesper Ribbe]

Martin Pool wrote:
> 2009/7/16 INADA Naoki <songofacandy at gmail.com>:
>   
>> Hi all.
>>
>> "Central Style" in User Guide
>> <http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#team-collaboration-central-style>
>> tells about bzr update but not bzr pull.
>>
>> I find that 'bzr update' pulls new revisions but doesn't pul new tags.
>> Is this bzr's feature? I think 'bzr update' should pull tags.
>>     
>
> I think you're right, it's a bug.  You can file one if you like.  It
> may not get fixed in itself (though you can certainly put up a patch)
> but maybe it will be done in a broader look at how tags work and
> propagate.
>
>   
Hi All,

On a related issue, I have another problem too with propagating tags: We 
have a setup with 2 master repositories (servers), because we have two 
offices with bad connections between them. In each office, the users 
work according to "Centralized workflow" towards the local server. On 
the servers, we have special scripts that try their best to synchronize 
the repositories.
The scripts use the "post_change_branch_tip" to push the changes.
Unfortunately for us, post_change_branch_tip is not triggered by only a 
tag change. So when someone only adds a tag, it doesn't get propagated 
to the other server.

Before I add bugs in launchpad, is there anywhere some documentation 
about the plan for tag support? I read "between the lines" that there 
have been a change how tags work (from repositories to branches?), and 
that there are thoughts about tags having version history.
And finally, is this something anyone is working on - I believe the 
focus is on 2.0 right now and this is not a prioritized area for that?

Best Regards,
Jesper