This is a collection of papers/discussions on Distributed Systems Theory
that seems to be a pretty good starting point for understanding.
http://the-paper-trail.org/blog/distributed-systems-theory-for-the-distributed-systems-engineer/
It focuses on bridge material to help people get a general
There's also the papers we love project
https://github.com/papers-we-love/papers-we-love
They have loads of papers about various topics. Here's the distributed
systems section:
https://github.com/papers-we-love/papers-we-love/tree/master/distributed_systems
Matty
On Tue, Sep 23, 2014 at 9:05
AFAIK I created v4 because of a breaking change to testing importing
gocheck from its new location, but we have to update the world before we
can land the dependencies.tsv changes.
John
=:-
On Sep 23, 2014 4:24 PM, Dimiter Naydenov dimiter.nayde...@canonical.com
wrote:
-BEGIN PGP SIGNED
On 23 September 2014 13:23, Dimiter Naydenov
dimiter.nayde...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I noticed a recent change in juju/juju bumping the revision of a
sub-repo (in this case juju/charms), which should be fine if the
sub-repo wasn't
Disclaimer: one of the commits mentioned here is mine.
I think I agree with Roger on this - as long as the changes to a package
are backwards compatible, incrementing the version number seems a bit over
the top. To begin with, it would mean quickly incrementing versioned
package versions (would
There are packaging nuances to versioning
On Tue, Sep 23, 2014 at 9:57 AM, Nate Finch nate.fi...@canonical.com wrote:
...
That's not quite how it works. For versioned import paths, the version
is about the API, not the exact implementation. It's entirely
OK to add new (backwardly compatible)
Hi folks,
I have been going through much of the code in the state package looking
at the work to migrate all the collection keys to handle multiple
environments.
In the long and distant past (earlier this year), the Tag() method
returned a string. There is a second tag like thing in the state
