<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>8442</bug_id>
          
          <creation_ts>2015-10-05 16:05:32 +0000</creation_ts>
          <short_desc>patchwork: Publish patch update log information</short_desc>
          <delta_ts>2017-04-19 15:38:33 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Patchwork/Patchtest</product>
          <component>Patchwork</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>Future</target_milestone>
          <dependson>9130</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jose Lamego">jose.a.lamego</reporter>
          <assigned_to name="Jose Lamego">jose.a.lamego</assigned_to>
          <cc>benjamin.esquivel</cc>
    
    <cc>bluelightning</cc>
    
    <cc>damien.lespiau</cc>
    
    <cc>mhalstead</cc>
          
          <qa_contact name="Alexandru Georgescu">alexandru.c.georgescu</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>54967</commentid>
    <comment_count>0</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2015-10-05 16:05:32 +0000</bug_when>
    <thetext>Determine best way to publish Patchwork&apos;s patch update log on a per-project basis and make it available to project maintainers and users.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>55777</commentid>
    <comment_count>1</comment_count>
    <who name="Damien Lespiau">damien.lespiau</who>
    <bug_when>2015-10-26 16:55:31 +0000</bug_when>
    <thetext>Current idea is to use the Event API with a new &apos;patch-state-changed&apos; event to expose status changes.

https://github.com/dlespiau/patchwork/issues/40
http://patchwork-freedesktop.readthedocs.org/en/latest/rest.html#events</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>72662</commentid>
    <comment_count>2</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2017-04-19 15:38:33 +0000</bug_when>
    <thetext>This feature is already implemented in production, for example, the following query can be used to view a patch status history:

https://patchwork.openembedded.org/api/1.0/projects/5/events/?name=patch-state-change&amp;patch=135314</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>