launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

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

Hi Matthew,

Thanks for your changes.  It's much improved.  A few more ideas:

- - I think it's really odd that people have to specify "Code for this
project is published in Bazaar branches on Launchpad" after creating
their project.  Specifying *how* your project will use launchpad seems
like an important step in creating a project.

- - "and then log in to Launchpad from Bazaar by typing bzr
launchpad-login in your terminal.": launchpad-login doesn't log into
Launchpad.  It specifies your login (username) for launchpad.

- - I think "~" might be more understandable than "tilde" in the body text.
 - "Replace project-name with your project's Launchpad id. The id is the
final part of your project overview page's URL: e.g. bzr in
https://launchpad.net/bzr"; looks redundant with "project-id: the id of
the project in Launchpad, which you can find at the end of your
project's overview page URL", and uses different terminology.

- - For branch stacking, I think "stacked on" would be clearer than
"basis".  We use "stacked on" in the bzr UI and Launchpad web UI.
"basis" does not occur in the linked bzr documentation.

Aaron



Matthew Revell wrote:
> 2009/8/4 Aaron Bentley <aaron@xxxxxxxxxxxxx>:
> 
>>> https://help.launchpad.net/Code/QuickStart/Draft
>>>
>>> Do you think this covers enough to get a project up and running with
>>> LP code hosting?
>> It looks reasonable, but
>>
>> - - Checking "Code for this project is published in Bazaar branches on
>> Launchpad" does not enable pushing to launchpad.  That is always
>> enabled.  (I'm not sure whether you were confused or whether the text
>> was unclear.)
> 
> I've removed that section.
> 
>> - - I think that "Loggerhead" is not a clear description.  While we don't
>> disguise the fact that we use Loggerhead, we don't indicate it
>> prominently.  We should talk about the "source code" tab or "viewing
>> source code"-- feature, not implementation.
> 
> Good point, amended.
> 
>> - - The trunk branch is also used as the default location for stacking.
> 
> Thanks, I've noted that with a link to the bzr docs on stacking, which
> I think I'll replace, eventually, with our own guide to hosting
> stacked branches.
> 
>> I would leave out discussion of series.  It's not something you need to
>> know right away, and it can be very confusing.
> 
> Done.
> 

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

iEYEARECAAYFAkp8UXkACgkQ0F+nu1YWqI3EzACdFbHqVoXwC9b70Z8pnIxnpHHv
eqMAn2spsRkcTY2Iu9DHQVUYsRNZ4I7L
=YIsv
-----END PGP SIGNATURE-----