Include expanded content from the webclient About page to explain the
motivation for the creation of Storyboard.
Change-Id: Idd06b19ff141720b0a22f8dd29098c9520c54f1b
The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.
Change-Id: Iafea53786d72faa19087c16a05b52e064fb21aa9
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: If30c90a9f843baf6a7cfba338b846fa5bbb2a695
Add instructions on how to run this program and also mention that
there is a webclient in another repo.
Change-Id: I610715249b1466c63507e9e428ea3833ac295309
The goal of this patch is to setup infrastructure and organization
of docs in the project.
Changes:
* Modified README to be similar to other OS projects
* Added project description to the index page
* Added install and run guide
Note(1):
These docs will be auto-published to http://ci.openstack.org/storyboard
after each merge very soon.
Note(2):
To build docs locally run in console:
$ tox -e docs
and open doc/build/html/index.html
Change-Id: I08b57117f90f3e4614bfa5c47020e40a6c26ff65
Project groups are convenient ways to display tasks that matter to you.
All views support listing per-project or per-projectgroup, so you can
create a "Nova program" group that will include nova and
python-novaclient, so that the Nova team can do all its bug triaging
in a single view.
Change-Id: Iaa32ab2c528033bcd4917fc5df5ab30839c5d3d7
Make tasks related to milestones, and associate milestones to the
actual *branches*. That's an elegant way to solve our need to track
"backport to milestone-proposed" tasks, solving an old issue we had
in Launchpad (and for which we were abusing "Fixreleased").
Each milestone is associated to a branch. There are three types of
branches: master (the future), release (the milestone-proposed branch,
when it's around), and stable/*. Milestones are mandatory, there is a
default 'undefined' milestone for when we don't really know when that
work will hit in the master branch.
In normal times we'd have the following unreleased milestones:
master branch -> undefined, havana-1, havana-2, havana-3
stable/grizzly branch -> 2013.1.3
When the milestone-proposed branch is created just before havana-1, we
move the havana-1 milestone from master to release branch:
master branch -> undefined, havana-2, havana-3
release branch -> havana-1
stable/grizzly branch -> 2013.1.3
That lets us track release-backporting tasks (targeted to
release/havana-1) separately from normal work (targeted to master/*).
At the final release, the release branch is just renamed to stable/* and
a new release branch is created for the new cycle.
Change-Id: Ia212ae9c40549fe484362cbd5b3f323a467edb76
Added a pbr-based build system and a tox file and some requirements
files. Also moved the apps to all be under storyboard so that a
publication to PyPI won't do evil things from an install perspective.
François Magimel