<?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>10153</bug_id>
          
          <creation_ts>2016-08-16 20:00:00 +0000</creation_ts>
          <short_desc>patchwork: create new patchwork staging instance</short_desc>
          <delta_ts>2017-12-06 17:09:29 +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>All</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>normal</bug_severity>
          <target_milestone>2.3 M1</target_milestone>
          
          <blocked>9942</blocked>
    
    <blocked>10064</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Jose Lamego">jose.a.lamego</reporter>
          <assigned_to name="Michael Halstead">mhalstead</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>jku</cc>
    
    <cc>jose.a.lamego</cc>
    
    <cc>leonardo.sandoval.gonzalez</cc>
    
    <cc>sgw</cc>
          
          
          <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>65240</commentid>
    <comment_count>0</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2016-08-16 20:00:00 +0000</bug_when>
    <thetext>Critical fixes may need to be implemented in OE Patchwork much sooner than when they get merged to upstream. For this to safely take place, a staging instance is needed where the changes can be tested using production data/hardware before going live.

The new staging instance must use code from a repository alternate to upstream at:

https://github.com/joselamego/patchwork.git

using the branch &quot;oe-staging&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>65242</commentid>
    <comment_count>1</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2016-08-16 20:05:36 +0000</bug_when>
    <thetext>The new staging instance must also receive patches from the mailing list just the same as in production.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>65533</commentid>
    <comment_count>2</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2016-08-25 21:29:16 +0000</bug_when>
    <thetext>Michael, do you have an ETA for this?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>65569</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2016-08-27 00:37:20 +0000</bug_when>
    <thetext>Wednesday Aug 31st should be possible.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>66331</commentid>
    <comment_count>4</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2016-09-19 16:13:37 +0000</bug_when>
    <thetext>Any updates on this?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>67391</commentid>
    <comment_count>5</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2016-10-19 21:48:18 +0000</bug_when>
    <thetext>This will be ready tomorrow.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>67587</commentid>
    <comment_count>6</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2016-10-26 08:05:56 +0000</bug_when>
    <thetext>Separate Patchwork staging instance is up at https://patchwork-staging.openembedded.org/ synced with production as of this morning.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>67642</commentid>
    <comment_count>7</comment_count>
    <who name="Jussi Kukkonen">jku</who>
    <bug_when>2016-10-27 15:12:05 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; Separate Patchwork staging instance is up at
&gt; https://patchwork-staging.openembedded.org/ synced with production as of
&gt; this morning.

Wasn&apos;t it supposed to track &quot;oe-staging&quot; from joses repo -- or is that something Jose can do?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>67646</commentid>
    <comment_count>8</comment_count>
    <who name="Jose Lamego">jose.a.lamego</who>
    <bug_when>2016-10-27 15:34:53 +0000</bug_when>
    <thetext>(In reply to comment #7)
&gt; (In reply to comment #6)
&gt; &gt; Separate Patchwork staging instance is up at
&gt; &gt; https://patchwork-staging.openembedded.org/ synced with production as of
&gt; &gt; this morning.
&gt; 
&gt; Wasn&apos;t it supposed to track &quot;oe-staging&quot; from joses repo -- or is that
&gt; something Jose can do?

patchwork-staging is pointing to my repo and currently receiving patches from the mailing list only for Open Embedded Core Layer project.

I am verifying the implemented fixes, which seem to be working as expected, with one exception: I may have to reopen 9941 (most likely due to an OE server configuration since issue is not reproducible in other instances) and track work in that bug.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>