On Sat, Mar 31, 2012 at 9:35 AM, Eugen Leitl <[email protected]> wrote:
> If it was just limited to tahoe-dev it definitely did not see wide > circulation. > I realize you don't want ephemeral nodes; maybe there should be a probation > period (demonstrated uptime, etc). > Hmm. That's a good suggestion. I wonder if there's a good way to implement it... > How are updates to new versions handled? > We ask members not to stay within a couple of versions of the current release version, but not to deploy a new release until 2-3 weeks after it comes out. -- Shawn
_______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
