lp://staging/~frankban/juju-core/logging-suite-path

Created by Francesco Banconi and last modified
Get this branch:
bzr branch lp://staging/~frankban/juju-core/logging-suite-path
Only Francesco Banconi can upload to this branch. If you are Francesco Banconi please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Francesco Banconi
Project:
juju-core
Status:
Development

Recent revisions

2805. By Francesco Banconi

Fix dependencies.

2804. By Francesco Banconi

Update dependencies.

2803. By Francesco Banconi

Rename the logging suite.

2802. By Tim Penhey

[r=thumper],[bug=1323937] Set version back to 1.19.3

The old clients need to be able to parse the new version, which means we can't move to builds where we use tags until after 1.20.0 release.

https://codereview.appspot.com/93570046/

2801. By Curtis Hovey

[r=sinzui],[bug=1323774] Make the win version match the go version.

The juju version was updated without also updating the win intaller rules;
The win installer was broken.

https://codereview.appspot.com/98630044/

2800. By Michael Foord

[r=mfoord] environs: make rsyslog port immutable

2799. By Dave Cheney

[r=dave-cheney] audit: new package

This is a preliminary proposal for a new package which enables logging of auditable events.

The specific logging mechanism is via loggo and there are a few minor issues to resolve.

More importantly is the debate around is the interface provided by this package sufficient for our auditing use cases.

2798. By Wayne Witzel III

[r=mfoord] rsyslog: ensure logs accumulate on state machines

Added a WatchForRsyslogChanges watcher and extended the API with
GetRsyslogConfig. Changed the rsyslog worker to use these additions.

2797. By Ian Booth

[r=wallyworld] Attempt to make replicaset tests robust

The repliaset tests were creating a mongo instance
for the suite and cleaning up replicas etc between
tests. This branch changes that to set up a new
instance for each test. A bunch of cleanup code can
then be removed and there will be better isolation
between tests. This may hopefully help with some
of the intermittent replicaset test failures.

https://codereview.appspot.com/101780043/

2796. By Tim Penhey

[r=thumper] Make versions aware of alpha, beta, dev tags.

Update the version number structure to have a tag.
A development version is an odd minor before 1.19.3
or anything with a tag after that (or a non-zero
build number).

Using the following format:
  {major}.{minor}.{patch} # if tag empty and build 0
  {major}.{minor}.{patch}.{build} # if tag empty
  {major}.{minor}-{tag}{patch} # if build 0
  {major}.{minor}-{tag}{patch}.{build}

This way any tag gets sorted before a release
using deb version sort.

I don't care and the code doesn't check about
alpha/beta vs. dev tags, but sorts them lexically.

https://codereview.appspot.com/100700044/

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp://staging/~go-bot/juju-core/trunk
This branch contains Public information 
Everyone can see this information.