Jump to: navigation, search

Difference between revisions of "StarlingX"

(Story and Bug Tracking)
(Story and Bug Tracking)
Line 28: Line 28:
  
 
== Story and Bug Tracking ==
 
== Story and Bug Tracking ==
Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description.    See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.
+
Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description.    See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.
  
** Sample Queries:
+
'''IMPORTANT:''' If you create a new Story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release.
*** Active Features: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature
 
*** Active Bugs: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug
 
  
* '''Tags''': Tags can also be used to facilitate searches. Proposed StarlingX tags: TBD
+
Sample queries:
 +
* To find the newly created stories use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new| this query]
 +
* To find all of the active bugs use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug| this query]
 +
* To find all of the active bugs assigned to the stx.2018.08 release use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.08| this query]
 +
* To find all of the active bugs assigned to the stx.2018.11 release use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.11| this query]
 +
 
 +
Queries for the Sub-projects will be defined on each Sub-project's page
 +
 
 +
You can also use Prefixes to search for Stories but we consider Prefixes optional so these searches might not show the same results as searching for Tags.
 +
* Sample Prefix queries:
 +
** To find all Stories with the [Features] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature| this query]
 +
** To find all Stories with the [Bug] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug| this query]
  
 
* [https://storyboard.openstack.org/#!/worklist/354 StarlingX Bug List]
 
* [https://storyboard.openstack.org/#!/worklist/354 StarlingX Bug List]
** This list is sorted manually by drag and drop. 
+
** This list will be removed.
** Please create bugs for any issues found in Storyboard, against one of the stx-* projects.  If you can't find the right project, use stx-integ
 
** After you create the bug, please add it to the Bug Worklist (link above). 
 
** If you don't see the "add a card" button on the Worklist, you need to be added as a user of the Worklist.  Please contact bruce.e.jones@intel.com to be added.
 
  
 
== References ==
 
== References ==

Revision as of 18:35, 20 July 2018

Welcome to the StarlingX Project

StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the Wind River® Titanium Cloud R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.

Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.

The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.


Documentation

These three documents will help get you started building, installing, and validating your installation of StarlingX:

Code

The StarlingX project uses Gerrit as its web-based code change management and review tool.

Story and Bug Tracking

Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description. See Tags and Prefixes for a description of how we use them.

IMPORTANT: If you create a new Story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release.

Sample queries:

  • To find the newly created stories use: this query
  • To find all of the active bugs use: this query
  • To find all of the active bugs assigned to the stx.2018.08 release use this query
  • To find all of the active bugs assigned to the stx.2018.11 release use this query

Queries for the Sub-projects will be defined on each Sub-project's page

You can also use Prefixes to search for Stories but we consider Prefixes optional so these searches might not show the same results as searching for Tags.

  • Sample Prefix queries:
    • To find all Stories with the [Features] prefix use: this query
    • To find all Stories with the [Bug] prefix use: this query

References

OpenStack Documentation

These are references to general OpenStack material:

Culture

We are proud to be an OpenStack Foundation project!

Meetings

Weekly calls

  • We host a weekly call for the project every Wednesday at 7am PDT / 1400 UTC. All are welcome.
  • We also host a Core team call every Thursday at 7AM PDT / 1400 UTC. This is for the Core team but other project participants are welcome to join.

Call details

Agenda and meeting minutes

The agenda and notes for each call are kept in Etherpads:

Please feel free to add items to the agendas for these meetings.

PTG Meetings

We are preparing for the Denver OpenStack PTG meeting. Draft agenda items can be found here:

Status and Planning

Upstream Status

The StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities.

TODO: Add a link to our Dashboard showing the status of upstream submissions