Difference between revisions of "Staging feeds"

From WebOS-Ports
Jump to navigation Jump to search
(Created page with "=== Legend === || Y || tested and I can confirm it works as expected || || N || tested and I can confirm it doesn't work as expected (bug numbers will be in comments). || || 1...")
 
Line 1: Line 1:
=== Legend ===
+
{| class="wikitable"
|| Y || tested and I can confirm it works as expected ||
+
|+Legend
|| N || tested and I can confirm it doesn't work as expected (bug numbers will be in comments). ||
+
|-
|| 1/2 || tested and I can confirm it partially works, but there are some new issues (bug numbers will be in comments). ||
+
! Y
|| - || no tests performed ||
+
| tested and I can confirm it works as expected
|| ? || cannot say ||
+
|-
 +
! N
 +
| tested and I can confirm it doesn't work as expected (bug numbers will be in comments).
 +
|-
 +
! 1/2
 +
| tested and I can confirm it partially works, but there are some new issues (bug numbers will be in comments).
 +
|-
 +
! -
 +
| no tests performed
 +
|-
 +
! ?
 +
| cannot say
 +
|-
 +
|}
  
 
If you have reflashed the image, mark with Y which type did you use and you *have to* change feed url to corresponding staging feed and do opkg update && opkg upgrade too.  
 
If you have reflashed the image, mark with Y which type did you use and you *have to* change feed url to corresponding staging feed and do opkg update && opkg upgrade too.  
HOWTO: [http://www.shr-project.org/trac/wiki/Stabilizing]
+
HOWTO: TODO [Stabilizing]
  
 
If you have just opkg upgraded to this feed please mark all image types as N.
 
If you have just opkg upgraded to this feed please mark all image types as N.
Line 13: Line 26:
 
If you wonder why someone added Y as usable then it could be because the state is somehow better then what's in public feeds even with some major issues noted in Comments.
 
If you wonder why someone added Y as usable then it could be because the state is somehow better then what's in public feeds even with some major issues noted in Comments.
  
Link to downloads: [http://build.shr-project.org/]
+
Link to downloads: [http://build.webos-ports.org/]
  
''' Really create trac tickets for issues you want to see fixed! Your comments here are appreciated and very usefull for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue '''
+
''' Really create bug reports for issues you want to see fixed! Your comments here are appreciated and very useful for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue '''
1. sometimes we need more information (or just have no idea what could be wrong in "foo didn't work) and it's hard to contact "reporter" with just his wiki login (unless he has the same on IRC), but we can easily comment on ticket.
+
* sometimes we need more information (or just have no idea what could be wrong in "foo didn't work) and it's hard to contact "reporter" with just his wiki login (unless he has the same on IRC), but we can easily comment on ticket.
2. sometimes other users have additional information for that issue, but it's not easy to see it here when it's scattered across multiple staging feeds instead of one ticket per issue.
+
* sometimes other users have additional information for that issue, but it's not easy to see it here when it's scattered across multiple staging feeds instead of one ticket per issue.
3. I try to put what was fixed in Desc: field, but strikethrough ticket number is shorter, easier to read and also link can contain more info about how it was fixed.
+
* I try to put what was fixed in Desc: field, but strikethrough ticket number is shorter, easier to read and also link can contain more info about how it was fixed.
''' Really create trac tickets for issues you want to see fixed! Your comments here are appreciated and very usefull for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue '''
+
''' Really create bug reports for issues you want to see fixed! Your comments here are appreciated and very useful for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue '''
  
If you need help how you correctly report a bug take a look here [wiki:Bug-report].
+
If you need help how you correctly report a bug take a look here TODO [wiki:Bug-report].
  
== 125 ==
+
== 001 ==
'''Desc:''' ???
+
'''Desc:''' First feed for test, newer qt5 5.1.1
  
 
'''Status:''' Building, '''NOT''' ready for test
 
'''Status:''' Building, '''NOT''' ready for test
  
|| Tested |||||| Reflashed  ||||Image        |||||||||||||| Tested || Can be merged || || ||
+
{| class="wikitable"
|| Device || ubifs || jffs2 || uSD || SHR || Aurora ||  Telephony || Networking || WiFi || GPS || Bluetooth || Enlightenment || Music || to public feed || Tester    || Comments (ticket numbers)||
+
|-
 
+
! Device
== 124 ==
+
! ext2
'''Desc:''' FSO and libphoneui* fixes
+
! ext3
 
+
! vmdk
'''Status:''' Closed (Thu Sep 12 21:51:35 CEST 2013), ready for test
+
! Telephony
 
+
! Networking
|| Tested |||||| Reflashed  ||||Image        |||||||||||||| Tested || Can be merged || || ||
+
! WiFi
|| Device || ubifs || jffs2 || uSD || SHR || Aurora ||  Telephony || Networking || WiFi || GPS || Bluetooth || Enlightenment || Music || to public feed || Tester   || Comments (ticket numbers)||
+
! GPS
||gta02|| || ||x||x|| || y || usb || || || || y || || y || Thamos0815 || bug #2053 fixed :); if someone wants to use as daily phone i would recommend to update packages phoneuid/phonefsod(bug #2094/ #2095 and more) and fsogsmd-module-lowlevel-openmoko/fsogsmd-module-modem-ti-calypso/fsogsmd bug #1494
+
! Bluetooth
== 123 ==
+
! Music
'''Desc:''' Small updates.
+
! to public feed
 
+
! Tester
'''Status:''' Closed (Wed Sep 11 15:48:42 CEST 2013), ready for test
+
! Comments (ticket numbers)
 
+
|-
|| Tested |||||| Reflashed  ||||Image        |||||||||||||| Tested || Can be merged || || ||
+
| maguro
|| Device || ubifs || jffs2 || uSD || SHR || Aurora ||  Telephony || Networking || WiFi || GPS || Bluetooth || Enlightenment || Music || to public feed || Tester    || Comments (ticket numbers)||
+
| Y
 
+
| -
== 122 ==
+
| -
'''Desc:''' Small updates and rebuilt after disk failure on buildhost.
+
| -
 
+
| Y
'''Status:''' Closed (Thu Aug 22 22:58:19 CEST 2013), ready for test
+
| -
 
+
| -
|| Tested |||||| Reflashed  ||||Image        |||||||||||||| Tested || Can be merged || || ||
+
| -
|| Device || ubifs || jffs2 || uSD || SHR || Aurora ||  Telephony || Networking || WiFi || GPS || Bluetooth || Enlightenment || Music || to public feed || Tester    || Comments (ticket numbers)||
+
| -
 +
| Y
 +
| JaMa
 +
| First feed for test
 +
|}
  
 
== Information from older feeds which are already merged to public feed ==
 
== Information from older feeds which are already merged to public feed ==
 
[[StagingTestsMerged]]
 
[[StagingTestsMerged]]

Revision as of 00:14, 12 October 2013

Legend
Y tested and I can confirm it works as expected
N tested and I can confirm it doesn't work as expected (bug numbers will be in comments).
1/2 tested and I can confirm it partially works, but there are some new issues (bug numbers will be in comments).
- no tests performed
? cannot say

If you have reflashed the image, mark with Y which type did you use and you *have to* change feed url to corresponding staging feed and do opkg update && opkg upgrade too. HOWTO: TODO [Stabilizing]

If you have just opkg upgraded to this feed please mark all image types as N.

If you wonder why someone added Y as usable then it could be because the state is somehow better then what's in public feeds even with some major issues noted in Comments.

Link to downloads: [1]

Really create bug reports for issues you want to see fixed! Your comments here are appreciated and very useful for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue

  • sometimes we need more information (or just have no idea what could be wrong in "foo didn't work) and it's hard to contact "reporter" with just his wiki login (unless he has the same on IRC), but we can easily comment on ticket.
  • sometimes other users have additional information for that issue, but it's not easy to see it here when it's scattered across multiple staging feeds instead of one ticket per issue.
  • I try to put what was fixed in Desc: field, but strikethrough ticket number is shorter, easier to read and also link can contain more info about how it was fixed.

Really create bug reports for issues you want to see fixed! Your comments here are appreciated and very useful for me to know that some feed shouldn't be merged to public feed, but not very helpful to fix issue

If you need help how you correctly report a bug take a look here TODO [wiki:Bug-report].

001

Desc: First feed for test, newer qt5 5.1.1

Status: Building, NOT ready for test

Device ext2 ext3 vmdk Telephony Networking WiFi GPS Bluetooth Music to public feed Tester Comments (ticket numbers)
maguro Y - - - Y - - - - Y JaMa First feed for test

Information from older feeds which are already merged to public feed

StagingTestsMerged