= Bazaar-Perforce TODO =

== Introduction ==

See also the NEWS file in the same directory as this file.


== User Stories ==

The User Stories below appear in priority order.  The estimated relative
size of each story appears in square brackets ([]) following the story.

    * As a user, I want a command-line program that produces a fast-export
      representation of a Perforce depot directory. [13] [4 hours]

        * selftest seems to hang inside
          bzrlib.plugins.bzrp4.tests.test_git_p4.TestGitP4.test_git_p4__dogfood
          inside git after merging upstream changes

        * The hang seems to be triggered by revision 74 in my sync branch.
          The tests complete if I branch from revision 73, and hang if I
          branch from revision 74.  

        * Ideas: upgrade to latest git; upgrade to latest git_p4; upgrade
          to latest git-fast-export, git-fast-import; perhaps caused by
          revision id in log message for revision 74; perhaps
          git-fast-import chokes on the revision id in the log in the
          import stream.

    * As a user, I want documentation that describes the usage of
      "p4-fast-export". [1]

    * As a user, I want a command-line program that produces a Bazaar
      branch from a fast-export representation of a Perforce depot
      directory. (Does this already exist as bzr-fastimport?) [0.5]

    * As a developer, I want the application code not to depend on the p4
      command-line client. [8]

    * As a developer, I want all tests to pass on Linux. [2]

    * As a developer, I want continuous integration, automatically
      triggered, for Linux test execution. [2]

    * As a developer, I want continuous integration, automatically
      triggered, for Cygwin test execution. [3]

    * As a user, I want bzr2p4 to show only the progress I care about
      instead of logging verbosely to the console. [3]

    * As a developer, I want bzr2p4 to be silent during tests that exercise
      it. [2]

    * As a user, I want the line endings of my files not to change during
      migration, so that my data is exactly the same before and after
      migration. (I'm not sure Perforce can do this.) [13]

    * As a user, I want the author of each Bazaar revision migrated to
      Perforce, so that I can easily see who created revisions in
      Perforce. [3]

    * As a user, I want migration of revisions with Perforce keywords to
      work correctly, so that I can migrate projects that use Perforce
      keywords. (Does this just need tests that demonstrate it works?) [3]

    * As a user, I want a suite of tools that facilitate creating a Bazaar
      branch from a Perforce depot, and submitting to a Perforce depot from
      a Bazaar branch. [?]