Linaro Dashboard Bundle utilities 2011.09

Milestone information

Project:
Linaro Dashboard Bundle utilities
Series:
linaro-11.11
Version:
2011.09
Released:
 
Registrant:
Paul Larson
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon linaro-python-dashboard-bundle-1.6-2011.09.tar.gz (md5, sig) Source code release 47
last downloaded 44 weeks ago
Total downloads: 47

Release notes 

* Added support for tags in 1.3 bundle format

Changelog 

View the full changelog

2011-09-28 Paul Larson <email address hidden>

 Release 1.6.0

2011-09-19 Zygmunt Krynicki <email address hidden>

 Add support for format 1.3.

 This simply adds support for tagging test runs

2011-09-19 Zygmunt Krynicki <email address hidden>

 Fix tests to actually check 1.2 format

2011-07-05 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5.3

2011-07-05 Zygmunt Krynicki <email address hidden>

 Drop dependency on distribute

2011-06-28 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5.2

2011-06-28 Zygmunt Krynicki <email address hidden>

 Do not require versiontools for installation

2011-06-23 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5.1

2011-06-23 Zygmunt Krynicki <email address hidden>

 Update author and description

2011-06-23 Zygmunt Krynicki <email address hidden>

 Fix some pep8 issues

2011-06-23 Zygmunt Krynicki <email address hidden>

 Fix pyflakes issue (harmless)

2011-06-23 Zygmunt Krynicki <email address hidden>

 Be pip friendly

2011-06-13 Zygmunt Krynicki <email address hidden>

 Move stuff around so that it's safe to import __init__ from setup.
 Update documentation to match.

2011-04-01 Zygmunt Krynicki <email address hidden>

 Fix for broken backwards compatibility in future versions of simplejson

2011-04-01 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5c3

2011-03-18 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5c2

2011-03-18 Zygmunt Krynicki <email address hidden>

 Allow subversion branches in source references

2011-03-18 Zygmunt Krynicki <email address hidden>

 Add changelog entry for 1.5

2011-03-18 Zygmunt Krynicki <email address hidden>

 Bump version to 1.5c1

2011-03-18 Zygmunt Krynicki <email address hidden>

 Add support for format 1.2

 This format allows to store public URL of an attachment and to omit the content.

2011-03-02 Zygmunt Krynicki <email address hidden>

 Improved DocumentIO support

 * Bump version to 1.4
 * Update changelog
 * Fix example usage of DocumentIO.load()
 * Remove get_version from __all__
 * Add tests for new IO features
 * Add an ability to sort keys in DocumentIO.dump() and dumps()
 * Add more document evolution tests.
 * Add sources to software context of "everything in one bundle 1.1"
 * Improve load/dump customization.

2011-03-02 Zygmunt Krynicki <email address hidden>

 Fix example usage of DocumentIO.load()

2011-03-02 Zygmunt Krynicki <email address hidden>

 Update changelog

2011-03-02 Zygmunt Krynicki <email address hidden>

 Remove get_version from __all__

 This function was removed some time ago.

2011-03-02 Zygmunt Krynicki <email address hidden>

 Add tests for new IO features

 Tests check for proper behavior of load, loads, dump and dumps with all the
 combination of new options (retain_order, sort_keys, human_readable)

2011-03-02 Zygmunt Krynicki <email address hidden>

 Add an ability to sort keys in DocumentIO.dump() and dumps()

 This allows to create predictable documents from plain python dictionaries.
 The default is off to preserve existing behavior. The default is also useful
 in load-modify-save cycle as it minimises the delta in the document (load by
 default preserves the order of keys)

2011-03-02 Zygmunt Krynicki <email address hidden>

 Bump version to 1.4

2011-03-02 Zygmunt Krynicki <email address hidden>

 Add more document evolution tests.

 New tests show how a document in 1.0 format is migrated to 1.0.1 and finally to
 1.1 without loosing any data. Evolved documents are available as plain text
 form manual inspection.

2011-03-02 Zygmunt Krynicki <email address hidden>

 Add sources to software context of "everything in one bundle 1.1"

 Software sources are a new feature of the 1.1 format and should be included
 in the reference document to illustrate all possible features and improve
 test coverage.

2011-03-02 Zygmunt Krynicki <email address hidden>

 Improve load/dump customization.

 DocumentIO.dump() and dumps() now supports human readable output (default) but has an option to switch to compact representation.
 DocumentIO.load() and loads() now supports ordered dictionaries (default) that retain key order in JSON objects.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Bump version to 1.3 final

2011-03-01 Zygmunt Krynicki <email address hidden>

 Add support for binary attachments.

 This merges several patches that alter the schema layout for attachments.
 There is a new mime type field. The contents are base64 encoded for safe
 transport. Threre is a minor specification upgrade to the way attachments
 used to work in earlier releases. In particular the old format designated
 that attachments are stored as an array of lines but it was not explicitly
 stated that the line terminators are _preserved_ and should not be added
 anywhere afterwards. This branch contains the usual unit tests required
 to ensure document evolution to the new format works correctly.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Update changelog

2011-03-01 Zygmunt Krynicki <email address hidden>

 Add tests for 1.1 evolution correctness.

 The tests check each aspect of the new conversion. In particular they validate
 that attachments are correctly converted without loosing any data.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Add test document in 1.1 format.

 This document is used in 1.1 evolution tests.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Fix failing tests for DocumentEvolution.is_latest()

 Those tests were failing because new evolution path added another step.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Add newlines to each array item in 1.0.1 and 1.0 attachments.

 The spec never formally declared this but the pre-1.1 attachment format was
 preserving newlines. This is how launch-control implemented the import process.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Add document evolution from 1.0.1 to 1.1.

 This adds a hidden function of DocumentEvolution class and registers a new step
 in the EVOLITION_PATH. The step evolition changes attachments (significant
 changes, have a look at the schema change in earlier patch and the code to know
 more), and software context's software image (two attributes were renamed to
 make their intent more clear).

2011-03-01 Zygmunt Krynicki <email address hidden>

 Update attachment schema for 1.1 format.

 Attachment schema was never finished before. There was a general desire to
 support storage of arbitrary binary files. The schema was not defined though.
 This change rewrites attachments from a
 dictionary-of-file-names-mapping-to-arrays-of-lines to a proper array of
 attachment objects. Each attachment object has three mandatory properties,
 pathname of the original file, mime type of the contents and the base64-encoded
 string with the actual data.

2011-03-01 Zygmunt Krynicki <email address hidden>

 Bump version to 1.3 alpha 1

2011-02-28 Zygmunt Krynicki <email address hidden>

 Bump version to 1.2 final

2011-02-28 Zygmunt Krynicki <email address hidden>

 Bump requirements for simplejson to 2.1, we really need the features present there

2011-02-28 Zygmunt Krynicki <email address hidden>

 Refresh installation instructions

2011-02-28 Zygmunt Krynicki <email address hidden>

 Fix build_sphinx by not using older api (now gone) to query for package version

2011-02-25 Zygmunt Krynicki <email address hidden>

 Use released versions of versiontools and linaro-json

2011-01-26 Zygmunt Krynicki <email address hidden>

 Update to latest versiontools and linaro-json, remove experimental templates, add initial 1.2 changelog, bump version to 1.2a1

2011-01-20 Zygmunt Krynicki <email address hidden>

 More robust test suite, some minor formatting changes to generated documents

2011-01-20 Zygmunt Krynicki <email address hidden>

 Minor import changes to work with linaro-json 2.0

2011-01-11 Zygmunt Krynicki <email address hidden>

 Drop schemas declared in python

2011-01-11 Zygmunt Krynicki <email address hidden>

 Bump version to 1.2 dev

2011-01-11 Zygmunt Krynicki <email address hidden>

 Explicitly version templates for particular schema versions

2011-01-11 Zygmunt Krynicki <email address hidden>

 Move 1.1 document schema to format1.1.py

2011-01-11 Zygmunt Krynicki <email address hidden>

 Fix SoftwareSource.branch_revision types from "int" to "integer"

2011-01-11 Zygmunt Krynicki <email address hidden>

 Rename SoftwareImage.desc to .name

2011-01-11 Zygmunt Krynicki <email address hidden>

 Add first draft of 1.1 schema

2011-01-03 Zygmunt Krynicki <email address hidden>

 Release 1.1.1

2011-01-03 Zygmunt Krynicki <email address hidden>

 Fix chicken-and-egg problem with versiontools

2011-01-03 Zygmunt Krynicki <email address hidden>

 Sign packages on upload to pypi

2011-01-03 Zygmunt Krynicki <email address hidden>

 Fix typo in MANIFEST.in

2011-01-03 Zygmunt Krynicki <email address hidden>

 Change version to 1.1 and release

2011-01-03 Zygmunt Krynicki <email address hidden>

 Merge class-based partial schema description.

 The partial schema can be used to generate documents using linaro_json.DocumentBuilder

2010-12-16 Zygmunt Krynicki <email address hidden>

 Add initial python schemas and templates

2011-01-03 Zygmunt Krynicki <email address hidden>

 Fix several missing newlines in docs and bump copyright date

2011-01-03 Zygmunt Krynicki <email address hidden>

 Rename project to linaro-dashboard-bundle

2011-01-03 Zygmunt Krynicki <email address hidden>

 Configure proper upload dir for upload_docs

2011-01-03 Zygmunt Krynicki <email address hidden>

 Use versiontools, fix linaro-json dependency to work with pip

2011-01-03 Zygmunt Krynicki <email address hidden>

 Merge ReST documentation

2010-12-28 Zygmunt Krynicki <email address hidden>

 Include documentation in packaging

2010-12-28 Zygmunt Krynicki <email address hidden>

 Remove unused _templates directory

2010-12-28 Zygmunt Krynicki <email address hidden>

 Get documentation source version directly from the module

2010-12-28 Zygmunt Krynicki <email address hidden>

 Improve installation documentation

2010-12-28 Zygmunt Krynicki <email address hidden>

 Document installation options

2010-12-28 Zygmunt Krynicki <email address hidden>

 Document missing usage patterns

2010-12-28 Zygmunt Krynicki <email address hidden>

 Describe possible failure conditions when loading document

2010-12-27 Zygmunt Krynicki <email address hidden>

 Update bzrignore

2010-12-27 Zygmunt Krynicki <email address hidden>

 Add ReST documentation

2010-12-27 Zygmunt Krynicki <email address hidden>

 Improve API documentation

2010-11-25 Zygmunt Krynicki <email address hidden>

 Change release to 1.0.0 final

2010-11-25 Zygmunt Krynicki <email address hidden>

 Drop DEP-5 copyright file (moved to debian)

2010-11-25 Zygmunt Krynicki <email address hidden>

 Change python classifier to 4 - Beta

2010-11-25 Zygmunt Krynicki <email address hidden>

 Change copyright to refer to project name

2010-11-25 Zygmunt Krynicki <email address hidden>

 Merge DocumentEvolutio API and 1.0.1 schema version

2010-11-21 Zygmunt Krynicki <email address hidden>

 Discard load quirks and create DocumentEvolution API

 The previous attempt at fixing existing bundles "out in the wild" that declare
 themselves as 1.0 but fail to be either 1.0 (in the original broken schema) nor
 the fixed 1.0 schema was not a good idea.

 The following semantical changes were made:
 * The 1.0 schema was made to reflect the current data out there as generated
 by abrek. It is different from the schema that was originally designed as
 1.0. The differences are minor and are only in attribute names of software
 and hardware context.
 * There is a new schema 1.0.1 that essentially means "I'm not playing tricks
 anymore" (expect full JSON validation compliance) and is a very small and
 backwards compatible change. Some would argue that it does not make sense to
 introduce such change for no good reason. The reason is to have a
 well defined state, if a document is in 1.0.1 then it _must_ validate.
 * The new DocumetEvolution API allows for conversions upwards towards the most
 recent format. The API is the same regardless of future document format
 changes.

 Other changes:
 * setup.py version bumped to 1.0 beta
 * Unit tests for all new features

2010-11-20 Zygmunt Krynicki <email address hidden>

 Add load quirks to deal with 1.0 format issues out in the wild

 Two format issues that are specified differently in the spec and
 implementations are:
 * TestRun software context is encoded as 'sw_context' while the spec
 mandates 'software_context'
 * TestRun hardware context is encoded as 'hw_context' while the spec
 mandates 'hardware_context'

 The new code adds a _load_ quirk (that can be disabled optionally) so that
 those old bundles are silently fixed. The quirk is only active for bundles
 that indicate the format is 'Dashboard Bundle Format 1.0'. In the future
 abrek and other tools should generated data with format '1.0.1' to indicate
 they expect full spec compliance.

2010-11-16 Zygmunt Krynicki <email address hidden>

 Update setup.py metadata

2010-11-15 Zygmunt Krynicki <email address hidden>

 Alpha release of linaro_dashboard_bundle

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.