Difference between revisions of "User:Afontquerni"
From IGEP - ISEE Wiki
Line 7: | Line 7: | ||
| style="width: 100%; font-size: 100%; padding-top: 2px;" | | | style="width: 100%; font-size: 100%; padding-top: 2px;" | | ||
− | {| style="background: rgb(247, 247, 255);font-size: | + | {| style="background: rgb(247, 247, 255);font-size:120%;" width="100%" |
|align="left" style="width: 70px;"|[[Image:Isee_logo.png|70px|left|link=Pre-installed software on IGEP Processor Boards]] | |align="left" style="width: 70px;"|[[Image:Isee_logo.png|70px|left|link=Pre-installed software on IGEP Processor Boards]] | ||
|align="left"|'''Firmware releases''' | |align="left"|'''Firmware releases''' | ||
Line 18: | Line 18: | ||
For '''IGEP AM335x processors boards''': | For '''IGEP AM335x processors boards''': | ||
* 2013.06.11 - '''[[IGEP firmware Yocto|IGEP Firmware 1.4]]''' - '''Version 1.4.1-0''' (doc)(bin) | * 2013.06.11 - '''[[IGEP firmware Yocto|IGEP Firmware 1.4]]''' - '''Version 1.4.1-0''' (doc)(bin) | ||
+ | * 2013.06.11 - '''[[IGEP firmware Yocto|IGEP Toolchain 1.4]]''' '''Version 1.4.1-0''' - (bin) | ||
+ | |||
|align="left"| | |align="left"| | ||
For '''IGEP OMAP3 processors boards''': | For '''IGEP OMAP3 processors boards''': | ||
* 2013.06.11 - '''[[IGEP firmware Yocto|IGEP Firmware 1.2]]''' '''Version 1.2.2-3''' - ([[Update the PRE-INSTALLED software image to a current release|doc]])([http://downloads.isee.biz/denzil/binary/igep_firmware-yocto-1.2.2-3.tar.bz2 bin]) | * 2013.06.11 - '''[[IGEP firmware Yocto|IGEP Firmware 1.2]]''' '''Version 1.2.2-3''' - ([[Update the PRE-INSTALLED software image to a current release|doc]])([http://downloads.isee.biz/denzil/binary/igep_firmware-yocto-1.2.2-3.tar.bz2 bin]) | ||
+ | * 2013.07.30 - '''[[IGEP firmware Yocto|IGEP Toolchain 1.2]]''' '''Version 1.2.2-3''' - ([http://downloads.isee.biz/denzil/binary/igep-sdk-yocto-toolchain-1.2.2-3.tar.bz2 bin]) | ||
|} | |} | ||
Line 46: | Line 49: | ||
* 2013.06.11 - '''[[Yocto_Project_1.4_-_Poky_9.0.y_dylan|Yocto 1.4 / Poky 9.0 - Dylan]]''' - '''Version 1.4.1-0''' ([[Yocto_Project_1.4_-_Poky_9.0.y_dylan|doc]])(git) | * 2013.06.11 - '''[[Yocto_Project_1.4_-_Poky_9.0.y_dylan|Yocto 1.4 / Poky 9.0 - Dylan]]''' - '''Version 1.4.1-0''' ([[Yocto_Project_1.4_-_Poky_9.0.y_dylan|doc]])(git) | ||
* 2013.06.11 - '''[[IGEP firmware Yocto|meta-isee Layer]]''' '''Version 1.4.1-0''' - ([[Yocto_Project_1.4_-_Poky_9.0.y_dylan|doc]])(git) | * 2013.06.11 - '''[[IGEP firmware Yocto|meta-isee Layer]]''' '''Version 1.4.1-0''' - ([[Yocto_Project_1.4_-_Poky_9.0.y_dylan|doc]])(git) | ||
− | |||
For '''IGEP OMAP3 processors boards''': | For '''IGEP OMAP3 processors boards''': | ||
Line 53: | Line 55: | ||
* 2013.07.30 - '''[[Yocto_Project_1.2_-_Poky_7.0.y_denzil|Yocto 1.2 / Poky 7.0 - Denzil]]''' '''Version 1.2.2-3''' - ([[Yocto_Project_1.2_-_Poky_7.0.y_denzil|doc]]) ([http://git.isee.biz/?p=pub/scm/poky.git;a=shortlog;h=refs/heads/denzil git]) | * 2013.07.30 - '''[[Yocto_Project_1.2_-_Poky_7.0.y_denzil|Yocto 1.2 / Poky 7.0 - Denzil]]''' '''Version 1.2.2-3''' - ([[Yocto_Project_1.2_-_Poky_7.0.y_denzil|doc]]) ([http://git.isee.biz/?p=pub/scm/poky.git;a=shortlog;h=refs/heads/denzil git]) | ||
* 2013.07.30 - '''[[IGEP firmware Yocto|meta-isee Layer]]''' '''Version 1.2.2-3''' - ([[Yocto_Project_1.2_-_Poky_7.0.y_denzil|doc]])([http://git.isee.biz/?p=pub/scm/meta-isee.git;a=shortlog;h=refs/heads/denzil git]) | * 2013.07.30 - '''[[IGEP firmware Yocto|meta-isee Layer]]''' '''Version 1.2.2-3''' - ([[Yocto_Project_1.2_-_Poky_7.0.y_denzil|doc]])([http://git.isee.biz/?p=pub/scm/meta-isee.git;a=shortlog;h=refs/heads/denzil git]) | ||
− | |||
Revision as of 17:00, 30 September 2013
|
|
|
|
|
|
|
Contents
- 1 IGEP Bug tracking
- 1.1 Overview
- 1.2 Introduction
- 1.3 Reporting Steps
- 1.3.1 Step 00: Search for already reported issue
- 1.3.2 Step 01: Report new issue
- 1.3.2.1 Step 01.01: Choose 'Project'
- 1.3.2.2 Step 01.02: Choose 'Category'
- 1.3.2.3 Step 01.03: Select 'Product Version' (OPTIONAL)
- 1.3.2.4 Step 01.04: 'Summary' - Write a complete and short title about issue
- 1.3.2.5 Step 01.05: Write detailed 'Description' about issue
- 1.3.2.6 Step 01.06: Describe 'Steps To Reproduce' that issue (OPTIONAL)
- 1.3.2.7 Step 01.07: Attach file with 'Upload file' (OPTIONAL)
- 1.3.2.8 Step 01.08: Press 'Submit Report' button
- 1.4 Workflow
- 1.5 Contribution & Support
IGEP Bug tracking
Overview
This article describe IGEP bug tracking system and workflow
Introduction
IGEP Bug tracking system (http://downloads.isee.biz/mantisbt/view.php) is based on MantisBT
Reporting Steps
Step 00: Search for already reported issue
Visit "View Issues webpage and use filters and search box to find it.
Step 01: Report new issue
If you don't already find issue about your question/feature/missing, you could open issue at "Report Issue"
Step 01.01: Choose 'Project'
On right and top it could be selected apropiated project (hardware board, software package, firmware)
Step 01.02: Choose 'Category'
When it is reported some issue, it could be selected these several types:
- bug: missing or wrong functionality
- change: change something or adjust configuration
- feature: add something or new feature
- remove: delete or remove something or feature
- request: costumer request or improvement. IGEP commumity will evaluate which changes will need to do.
Step 01.03: Select 'Product Version' (OPTIONAL)
Step 01.04: 'Summary' - Write a complete and short title about issue
Like a subject in e-mail, summary of an issue is a title of your message that will identify them about reason and theme of this issue
Step 01.05: Write detailed 'Description' about issue
Describe any information about issue. First paragraph should be an introduction and resume about that.
Step 01.06: Describe 'Steps To Reproduce' that issue (OPTIONAL)
It will make easy to analize issue if we could reproduce by ourselves
Step 01.07: Attach file with 'Upload file' (OPTIONAL)
Sometimes, an image or a source code patch are the best way to show issue
Step 01.08: Press 'Submit Report' button
Press 'Submit Report' button ends issue reporting.
After that it will assigned a number which is identificator of issue
See bellow captured screen example:
Workflow
Issues have several states:
- NEW: First state when issue is created
- ASSIGNED: Somebody has assigned and that person is responsible for resolving/response issue
- RESOLVED: Issue has been resolved
- CLOSED: Issue has been finished (tested OK and archived)
Issues have several participants:
- manager
- developer
- reporter
Workflow or states issue life and actions:
[anybody] NEW (start point) -> [manager] ASSIGNED (responsability) -> [developer] RESOLVED (solution) -> [manager] CLOSED (end point) \<-- (needs something) FEEDBACK [developer]<--/
Contribution & Support
Contributions to this project be welcome and you can send your patches to support@iseebcn.com or you can use the igep forum for it.
You can access to IGEP-x-Loader repository using our git at git.igep.es
IGEP IRC Channel: http://webchat.freenode.net/?channels=igep