what if tracker url changes?

[Harry Flink]

On Wed, November 17, 2010 15:29, Frits Jalvingh wrote:
> I think this is all pretty horribly wrong. Using URLs to store that bug
> means that any *other* function you want to apply to that solved bug
> needs to decode that URL (been there, needed to do that 8-/). For
> instance if I want to notify a tracker that a bug is solved I have to
> "decode" that URL into it's parts, then send a SOAP request to handle
> that. That is a bad interface. If URLs change over time it becomes worse
> because I now have to decode more than one.
>
> I think the proper way to do it is to use (immutable) aliases for
> trackers, and specifying alias-to-tracker URL/interface mappings /inside
> the repository/. That way you have zero-configuration URLs which are
> easily changeable.
>
> This looks like another thing that is badly solved because there are not
> versioned properties in Bazaar, like the rules file etc...
>

I'm there with you that storing the URL only
with --fixes is a design flaw. I kind of hoped
that Bzr would store the tracker shortcut and
bug ID only but then again I also was wrong
thinking Bzr would keep the tracker mapping
information in repository too.

Now if we'd want to use this --fixes I
understood that we had to manually add mapping
information to branch.conf to every user's every
local branch.

We use branching for every bug fix/feature add
and modifying branch.conf just feels too much
extra work so we just dont use it at the moment.

Later we added more bug trackers and changed
the old tracker URL a bit so even if we had used
the --fixes, all the URLs would have been wrong
there after.

I really like bzr but this feature is not really
usable yet. I have high hopes that maybe one day.


-- 
Best Regards,
Harry Flink