civilinfrastructureplatform:ciptesting:management
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:ciptesting:management [2017/10/12 11:28] Agustin Benito Bethencourt [Release process howto] |
civilinfrastructureplatform:ciptesting:management [2018/04/03 08:09] (current) Agustin Benito Bethencourt [Project journal] |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| The current goal is to present at ELCE the testing environment working, leaving refinements and non-critical tasks for the weeks after the event. Please take **dates as estimations and early plans, not commitments**. | The current goal is to present at ELCE the testing environment working, leaving refinements and non-critical tasks for the weeks after the event. Please take **dates as estimations and early plans, not commitments**. | ||
| - | You can follow closely the CIP testing project status through the [[https://gitlab.com/cip-project/cip-testing/testing/boards|kanban board]] and the [[:civilinfrastructureplatform/ciptesting/journal|project journal]]. | + | ==== CIP journal ==== |
| + | You can follow closely the CIP testing project status through the [[https://gitlab.com/cip-project/cip-testing/testing/boards|kanban board]] but for those who are working on the project, the kanban board might not be enough. At CIP Testing project we complement it with the [[:civilinfrastructureplatform/journal|project journal]], that later on were adopted for other activities. | ||
| + | |||
| + | The [[:civilinfrastructureplatform/journal|project journal]] is a diary of what those involved in the project do on daily basis. The current team at CIP is geographically distributed and works in an asynchronous mode so the journal becomes a good tool to tell your team mates what are you up to while keeping overview of your own effort daily and weekly. This is the main tool used to create the reports sent regularly to the mailing list about the activity done by the team. | ||
| + | |||
| + | Check the [[/civilinfrastructureplatform/journal#journal-ground-rules|CIP project journal ground rules]] to understand how it works. | ||
| + | |||
| + | ==== CIP Testing Project Team ==== | ||
| + | |||
| + | The current team behind the CIP Testing project are: | ||
| + | * Robert Marshall - Codethink Ltd Lead engineer | ||
| + | * Agustín Benito Bethencourt - Codethink Ltd. Sometimes management but most of the time housekeeper and or butler. Very soon also gardeining (watering the seeds). | ||
| + | * Collaborators: | ||
| + | * Tom Pollard - Codethink Ltd. | ||
| + | * Ben Hutchings - Codethink Ltd. | ||
| + | Obviously there are other CIP developers involved in this effort like Daniel Sangorrin (Toshiba), Chris Paterson (Renesas) that help this team when required. | ||
| + | |||
| + | Other past members and collaborators: | ||
| + | * Don Brown - Codethink Ltd. | ||
| + | * Christos Karamitsos - Codethink Ltd. | ||
| + | * Lachlan Mackenzie - Codethink Ltd. | ||
| + | |||
| + | You can contact them all through the [[https://lists.cip-project.org/mailman/listinfo/cip-dev|cip-dev mailing list]]. | ||
| ===== Board at Desk Delivery processes and practices ===== | ===== Board at Desk Delivery processes and practices ===== | ||
| Line 30: | Line 52: | ||
| === Bugs management === | === Bugs management === | ||
| - | * Check the CIP testing project [[https://gitlab.com/cip-project/cip-testing/testing/boards/322796?&label_name[]=bug|bugs board]] | + | * Check the CIP testing project [[https://gitlab.com/cip-project/cip-testing/testing/boards/322796?&label_name[]=bug|bugs board]] |
| ==== Release process howto ==== | ==== Release process howto ==== | ||
| Line 38: | Line 60: | ||
| * [[https://gitlab.com/cip-project/cip-testing/testing/issues/141|#141]] Release B@D v1.0. This is the task that track the whole process so it is the one to follow by those interested in a higher level view of the process. It includes the most relevant tasks. | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/141|#141]] Release B@D v1.0. This is the task that track the whole process so it is the one to follow by those interested in a higher level view of the process. It includes the most relevant tasks. | ||
| * Each phase of the process is detailed in a single task: | * Each phase of the process is detailed in a single task: | ||
| - | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/142|#142]] B@D v1.0 release: Gold Master declaration. | + | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/142|#142]] B@D v1.0 release: Gold Master declaration. |
| - | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/143|#143]] B@D v1.0 release: deployment. | + | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/143|#143]] B@D v1.0 release: deployment. |
| - | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/144|#144]] B@D v1.0 release: documentation. If the project grows, the recommendation is to split this tasks in several. The task is structured so that splt is easy to do. | + | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/144|#144]] B@D v1.0 release: documentation. If the project grows, the recommendation is to split this tasks in several. The task is structured so that splt is easy to do. |
| - | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/146|#146]] B@D v1.0 release: marketing material preparation. This task heavily depedsn on the type of project you work on and in the possibility or not to have a marketing team. In our current process, our marketing effort is very limited and we heavily rely on the Linux Foundation effort. | + | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/146|#146]] B@D v1.0 release: marketing material preparation. This task heavily depedsn on the type of project you work on and in the possibility or not to have a marketing team. In our current process, our marketing effort is very limited and we heavily rely on the Linux Foundation effort. |
| - | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/147|#147]] B@D v1.0 release: publishing | + | * [[https://gitlab.com/cip-project/cip-testing/testing/issues/147|#147]] B@D v1.0 release: publishing |
| ==== CIP Releases ==== | ==== CIP Releases ==== | ||
| - | Please check the [[:civilinfrastructureplatform/ciptesting/releases|CIP testing releases]] wiki page to find out about previous releases of projects/products delivered by CIP testing project. | + | Please check the [[:civilinfrastructureplatform/ciptesting/releases|CIP testing releases]] wiki page to find out about previous releases of projects/products delivered by CIP testing project. If you are interested in the current version of B@D please start from the [[/civilinfrastructureplatform/ciptesting|Board At Desk landing page]]. |
| ==== Marketing material and plan ==== | ==== Marketing material and plan ==== | ||
civilinfrastructureplatform/ciptesting/management.1507807708.txt.gz · Last modified: 2017/10/12 11:28 by Agustin Benito Bethencourt
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
