API requests from a qbzr dev

[Vincent Ladeuil]

>>>>> "Gary" == Gary van der Merwe <garyvdm at gmail.com> writes:

    Gary> On Fri, Sep 25, 2009 at 4:49 PM, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
    >> What would be very valuable for everybody involved is that you:
    >> - list every private API you're currently using,

    Gary> I know I should log bugs for these, but it's a start anyway...

Thanks, and for those who didn't follow the other discussion, I
think it makes it clear why Alexander feels bzrlib API is not
stable.

    Gary> bzrlib.config.GlobalConfig._get_parser
    Gary> bzrlib.config.BranchConfig._get_location_config
    Gary> bzrlib.config.BranchConfig._get_branch_data_config
    Gary> bzrlib.builtins.cmd_merge._do_preview  (Overridden to implement bzr
    Gary> merge --qpreview)
    Gary> bzrlib.transform._PreviewTree
    Gary> bzrlib.branch.Branch._format
    Gary> bzrlib.workingtree.WorkingTree._format
    Gary> bzrlib.repository.Repository._format
    Gary> bzrlib.repository.Repository._make_parents_provider
    Gary> bzrlib.workingtree.WorkingTree._comparison_data
    Gary> bzrlib.diff._get_trees_to_diff
    Gary> (https://code.edge.launchpad.net/~garyvdm/bzr/get_trees_and_branches_to_diff/+merge/12341)

    Gary> * Produced by hand, so might not be complete...

Now, we've got meat to talk about stability... just to be clear:
we *don't* guarantee that if *any* of the above change we will:
1) document it, 2) deprecate it properly (i.e. with warnings).

I think the above is enough to *start* the discussion and see
what should be made public, from there we can file bugs.

     Vincent