tahoe-lafs/trac-2024-07-25

what download shall we take those days #2371

New issue

Closed

opened 2015-02-01 09:42:51 +00:00 by xavierl · 1 comment

xavierl commented

2015-02-01 09:42:51 +00:00

Owner

it makes very long time no new relase were done.
but still it seems project is active

i would like to make a new try for tahoe lafs

what shall you recommend to use actually :

version 1.10 which is quite 2 years ago

master from github

master from trac ?

it makes very long time no new relase were done. but still it seems project is active i would like to make a new try for tahoe lafs what shall you recommend to use actually : version 1.10 which is quite 2 years ago master from github master from trac ?

tahoe-lafs added the

labels 2015-02-01 09:42:51 +00:00

tahoe-lafs added this to the 1.10.1 milestone 2015-02-01 09:42:51 +00:00

daira commented

2015-02-01 21:12:27 +00:00

Author

Owner

There's no real reason not to use master; we do all development on branches and keep master quite stable. If you do use master and need to report any problem, please give the full version info displayed by bin/tahoe --version-and-path.

master on trac is synchronized with master on github (in fact all branches are synchronized), but it's much easier to clone from github.

You're right that it's been far too long without a release. Hopefully 1.10.1 will be released this month.

There's no real reason not to use master; we do all development on branches and keep master quite stable. If you do use master and need to report any problem, please give the full version info displayed by `bin/tahoe --version-and-path`. master on trac is synchronized with master on github (in fact all branches are synchronized), but it's much easier to clone from github. You're right that it's been far too long without a release. Hopefully 1.10.1 will be released this month.

tahoe-lafs added

and removed

labels 2015-02-01 21:12:27 +00:00

daira closed this issue

2015-02-01 21:12:27 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

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#2371

No description provided.