tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

release 1.10.0 #1932

New issue
Closed
opened 2013-03-18 18:18:32 +00:00 by davidsarah · 7 comments
davidsarah commented 2013-03-18 18:18:32 +00:00
Owner
Copy link

Things to do:

  • fix blockers (#1525, #1732, #1767)
  • update dependency tarballs, for SUMO bundle
  • update tarballs on tahoe-lafs.org/deps (especially "mock")
  • 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
Things to do: * fix blockers (#1525, #1732, #1767) * update dependency tarballs, for SUMO bundle * update tarballs on tahoe-lafs.org/deps (especially "mock") * ~~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
tahoe-lafs added the
packaging
major
defect
1.9.2
 labels 2013-03-18 18:18:32 +00:00
tahoe-lafs added this to the 1.10.0 milestone 2013-03-18 18:18:32 +00:00
davidsarah commented 2013-03-18 19:22:47 +00:00
Author
Owner
Copy link

Draft NEWS on this branch: https://github.com/tahoe-lafs/tahoe-lafs/commits/1932-news

Draft NEWS on this branch: <https://github.com/tahoe-lafs/tahoe-lafs/commits/1932-news>
warner commented 2013-03-19 18:47:14 +00:00
Author
Owner
Copy link

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.

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.
warner commented 2013-03-19 23:27:12 +00:00
Author
Owner
Copy link

tarball builders seem to be running and uploading properly

tarball builders seem to be running and uploading properly
David-Sarah Hopwood <david-sarah@jacaranda.org> commented 2013-03-20 22:20:56 +00:00
Author
Owner
Copy link

In changeset:97a7cac7d3263e82:

NEWS.rst: precautions when upgrading. refs #1932

Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org>
In changeset:97a7cac7d3263e82: ``` NEWS.rst: precautions when upgrading. refs #1932 Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org> ```
warner commented 2013-04-25 00:45:54 +00:00
Author
Owner
Copy link

1.10.0c1, the first release candidate, has been tagged. Barring any problems, this same code should be released on 01-May-2013 as 1.10.0

1.10.0c1, the first release candidate, has been tagged. Barring any problems, this same code should be released on 01-May-2013 as 1.10.0
warner commented 2013-05-01 18:10:39 +00:00
Author
Owner
Copy link

final tags made, tarballs signed and uploaded

PyPI updated, front-wiki-page updated.

Still to do: send out email, tweet, relink front-wiki-page to email, close this ticket, close the milestone. I'll do these in a couple of hours.

final tags made, tarballs signed and uploaded PyPI updated, front-wiki-page updated. Still to do: send out email, tweet, relink front-wiki-page to email, close this ticket, close the milestone. I'll do these in a couple of hours.
warner commented 2013-05-01 21:02:23 +00:00
Author
Owner
Copy link

mail sent, front-page wiki updated. When tweeting, please point your URLs at the tahoe-dev announcement email archive page:

https://tahoe-lafs.org/pipermail/tahoe-dev/2013-May/008232.html

Done!

mail sent, front-page wiki updated. When tweeting, please point your URLs at the tahoe-dev announcement email archive page: <https://tahoe-lafs.org/pipermail/tahoe-dev/2013-May/008232.html> Done!
tahoe-lafs added the
fixed
 label 2013-05-01 21:02:23 +00:00
warner closed this issue 2013-05-01 21:02:23 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
1.10.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1932
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?