[NCBC-13] generating shippable artifacts Created: 12/Jan/12  Updated: 07/Feb/14

Status: In Progress
Project: Couchbase .NET client library
Component/s: process
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Matt Ingenthron Assignee: Jeff Morris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by Jeff Morris [ 29/Oct/13 ]
Matt -

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

Thanks,

Jeff
Comment by Matt Ingenthron [ 04/Dec/13 ]
(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.
 
Generated at Tue Jul 29 20:17:32 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.