wanted: Windows Packaging Master #781
Labels
No Label
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
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#781
Loading…
Reference in New Issue
Block a user
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?
Lots of people would like to have a binary installer for Windows. See e.g. this discussion on arstechnica.com: http://episteme.arstechnica.com/eve/forums/a/tpc/f/174096756/m/975001280041?r=556008280041#556008280041 . RobK implemented such a thing long ago, see tickets #195 and #242 . The Windows buildslave currently builds an installer on every revision control checkin and uploads it to a server owned by allmydata.com, see http://allmydata.org/pipermail/tahoe-dev/2009-July/002450.html .
This ticket is for someone to volunteer to be the Windows Packaging Master. Your job would be to configure a buildbot to upload the installer to a publicly reachable web page, to document the existence of the Windows package and how to use it, and to help write automated tests of Windows packaging so that future changes to Tahoe-LAFS don't unwittingly break it.
v1.5.1 could be the version of Tahoe-LAFS that is supported for installation on Windows using a normal GUI installer. If someone volunteers to be the Windows Packaging Master.
This ticket is getting really old. Did nobody ever do anything like this? :(
There are a LOT of people who REALLY want a binary release for windows... ideally configurable as a service, and maybe with a light admin gui.
I opened this ticket, hoping that someone would volunteer to take on a role. I think we should close this ticket now as not being an "issue" that we can track progress on. For a list of currently open tickets that someone could close by contributing an appropriate patch, see this query:
https://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~windows&order=priority
We could still benefit from someone volunteering to improve the Windows packaging! But we're not going to continue keeping a separate ticket open in the issue tracker to reflect that fact.