Details

    • Type: Task
    • Status: In Progress
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: process
    • Labels:
      None
    • Sprint:
      Sprint 2 - Feb 5-26 2014
    No reviews matched the request. Check your Options in the drop-down menu of this sections header.

      Activity

      ingenthr Matt Ingenthron created issue -
      john John Zablocki (Inactive) made changes -
      Field Original Value New Value
      Fix Version/s 1.3 [ 10396 ]
      ingenthr Matt Ingenthron made changes -
      Assignee John Zablocki [ john ] Matt Ingenthron [ ingenthr ]
      ingenthr Matt Ingenthron made changes -
      Assignee Matt Ingenthron [ ingenthr ] Jeff Morris [ jmorris ]
      jmorris Jeff Morris made changes -
      Component/s process [ 10916 ]
      Hide
      jmorris Jeff Morris added a comment -

      Matt -

      Can you provide more detailed expectations regarding what exactly should be delivered for this ticket?

      Thanks,

      Jeff

      Show
      jmorris Jeff Morris added a comment - Matt - Can you provide more detailed expectations regarding what exactly should be delivered for this ticket? Thanks, Jeff
      jmorris Jeff Morris made changes -
      Fix Version/s 1.3.1 [ 11318 ]
      Fix Version/s 1.3.0 [ 10396 ]
      Hide
      ingenthr Matt Ingenthron added a comment -

      (replied via email long ago, just copying the comment here)

      This was meant to mean that we have CI generating shippable artifacts. I still think this should be done, but I'll leave it to your judgement.

      I know it's less important with something like .Net versus say C code, but toolchain matters. Meaning, there can be subtle differences based on versions of the software that builds the artifacts we ship. We don't want to accidentally have your product change because a patch was applied, for instance.

      We should have a documented, change-controlled toolchain and use it to generate shippable artifacts under CI.

      Show
      ingenthr Matt Ingenthron added a comment - (replied via email long ago, just copying the comment here) This was meant to mean that we have CI generating shippable artifacts. I still think this should be done, but I'll leave it to your judgement. I know it's less important with something like .Net versus say C code, but toolchain matters. Meaning, there can be subtle differences based on versions of the software that builds the artifacts we ship. We don't want to accidentally have your product change because a patch was applied, for instance. We should have a documented, change-controlled toolchain and use it to generate shippable artifacts under CI.
      jmorris Jeff Morris made changes -
      Fix Version/s 1.3.2 [ 11321 ]
      Fix Version/s 1.3.1 [ 11318 ]
      jmorris Jeff Morris made changes -
      Status Open [ 1 ] In Progress [ 3 ]
      jmorris Jeff Morris made changes -
      Fix Version/s 1.3.3 [ 11400 ]
      Fix Version/s 1.3.2 [ 11321 ]
      jmorris Jeff Morris made changes -
      Sprint Sprint 2 - Feb 5-26 2014 [ 111 ]
      jmorris Jeff Morris made changes -
      Rank Ranked higher
      jmorris Jeff Morris made changes -
      Fix Version/s 1.3.3 [ 11400 ]
      brett19 Brett Lawson made changes -
      Workflow jira [ 15836 ] Couchbase SDK Workflow [ 43357 ]

        People

        • Assignee:
          jmorris Jeff Morris
          Reporter:
          ingenthr Matt Ingenthron
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:

            Agile

              Gerrit Reviews

              There are no open Gerrit changes