Iain Lane 6db05720f3 Conditional LP API usage & better p-l-s errors
* lpapicache: Do not immediately bail out if we have no credentials to
  login. Clients are now expected to handle the lack of credentials
  themselves.
* pull-lp-source: Make LP API use optional - fall back to a hardcoded
  default release if we aren't using it. (LP: #477670)
* pull-lp-source: Detect more failure conditions and give a nice error
  instead of a trace
* buildd, requestsync: Detect & bail if we don't have credentials and need
  them. These scripts cannot continue under those circumstances.
2009-11-07 19:20:46 +00:00
2009-04-27 14:02:53 +01:00
2009-04-27 13:59:29 +01:00
2009-04-15 22:56:07 -04:00
2008-12-30 10:23:00 +00:00
2009-01-19 22:37:27 +00:00
2009-01-19 22:37:27 +00:00
2009-04-27 21:39:11 +01:00
2009-04-27 14:01:06 +01:00
2009-04-27 13:58:54 +01:00

Updating the ubuntu-dev-tools package in Ubuntu
-----------------------------------------------

Here are the steps that are recommended to take when updating the
ubuntu-dev-tools package in Ubuntu.

1) Make sure that there are no new revisions to the package's trunk in Bazaar:

    bzr pull lp:ubuntu-dev-tools

2) Check to make sure that all approved merges have been merged:

    https://code.launchpad.net/ubuntu-dev-tools/+approvedmerges

3) Make sure that there is no low lying fruit that can be fixed at:

    https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools

4) Before uploading the package change the UNRELEASED field in the
   debian/changelog file to the current development release.

   If there is no UNRELEASED entry, make sure that the version for the current
   one has not been uploaded by someone else already:

    https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/+publishinghistory

   Using: dch -r UNRELEASED - will also set the release to the development
   version.

5) Once the target release has been changed, commit it to Bazaar (where X.YY is
   the new package version):

    bzr commit -m "Uploaded X.YY to RELEASE."

6) Tag the new release in Bazaar:

    bzr tag X.YY

   For a full list of tags, please see: 'bzr tags'. This is so we can track
   which Bazaar revision is in which release and makes bug triaging easier.

7) Create the new source package, without the .bzr directory (this is to
   reduce the size of the tarball):

    debuild -S -sa -I.bzr

8) Upload the package to Ubuntu with dput as normal:

    dput ubuntu ubuntu-dev-tools_X.YY_source.changes

9) Create a new blank entry with dch -i and mark it as UNRELEASED.
Description
No description provided
Readme 15 MiB
Languages
Python 89%
Shell 9.9%
Perl 1.1%