Short, task-based bzr doclets for real-world use cases.

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karl Fogel wrote:
> Ian Clatworthy <ian.clatworthy at internode.on.net> writes:
>> As you and others have indicated in this thread, I don't believe
>> our "fix a bug on a project" model is simple enough yet. I'd like
>> it to be something more like:
>>
>>   bzr clone lp:XXX
>>   cd XXX
>>   bzr branch trunk fix
>>   cd fix
>>   (hack, hack, hack)
>>   bzr send
> 
> Agreed... but I guess we're not there yet?  (At least, the recipe I seem
> to have settled on is more complicated than that... but see below).
> 
> So, I've created this page:
> 
>    http://bazaar-vcs.org/Scenarios
> 
> And written the first listed scenario:
> 
>    http://bazaar-vcs.org/Scenarios/Bugfix

I think this is more complicated that needed.  All you really need is:

bzr branch http://qproject.org/bzr/qproject.dev/ qproject-NUMBER
# optionally --stacked
bzr commit
bzr send

You say "Suppose you want to make a bugfix in a project that is kept in
bzr", but you are describing a set-up that's more appropriate for
someone who wants to become a regular contributor, not someone doing a
one-off bugfix.

It's not worth it for a casual contributor to set up a shared repo, or
for them to create a local mirror of trunk.  By saying a casual
contributor should do those things, you make bzr look harder than it is.

Also, your use of "bundle" is inaccurate.  What "bzr send" emits is a
"merge directive".  It may or may not contain a bundle, depending on the
options you give it.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkl3t5cACgkQ0F+nu1YWqI3zOwCfenmPCSsXpJzfp0/jGbnets0L
GOYAn2DTzJFSBtOI8ridYyDzYGKAHM/7
=RHHt
-----END PGP SIGNATURE-----