Opened at 2013-03-18T18:18:32Z

Last modified at 2013-05-01T21:02:23Z

#1932 closed defect

release 1.10.0 — at Version 3

Reported by: davidsarah Owned by: warner
Priority: major Milestone: 1.10.0
Component: packaging Version: 1.9.2
Keywords: release blocker Cc:
Launchpad Bug:

Description (last modified by warner)

Things to do:

  • fix blockers (#1525, #1732, #1767)
  • re-enable upload from tarball builders
  • make an alpha1 tag to get the tarball versions right
  • smoke-testing
  • NEWS changelog
  • any other documentation?
  • confirm builders pass
  • tag release candidate

Change History (3)

comment:2 Changed at 2013-03-19T07:35:59Z by warner

  • Owner set to warner
  • Status changed from new to assigned

comment:3 Changed at 2013-03-19T18:47:14Z by warner

  • Description modified (diff)

I need to look at the tarball builders and figure out how/whether to re-enable tarball uploads. I vaguely remember turning them off for a good reason, so I must figure that out before turning them back on.

They're currently creating tarballs with names like "allmydata-tahoe-1.9.0.post131.tar.gz", because 1.9.0 is the most recent tag in the git repo's master branch (1.9.1 was made on a separate branch, not trunk, and 1.9.2 was made from darcs). I think creating a 1.10a1 tag should fix that, but I'd like to confirm before allowing those tarballs to upload.

Note: See TracTickets for help on using tickets.