Page Comparison

[08:51:59 EDT(-0400)] * anastasiac (n=team@142.150.154.160) has joined #fluid-work
[09:03:02 EDT(-0400)] * michelled (n=team@142.150.154.197) has joined #fluid-work
[10:18:25 EDT(-0400)] * theclown (n=theclown@142.150.154.101) has joined #fluid-work
[10:24:22 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[10:36:16 EDT(-0400)] * colinclark (n=colin@ginger.caret.cam.ac.uk) has joined #fluid-work
[10:36:45 EDT(-0400)] <colinclark> michelled: Having weird problems with IM today. I saw your message about using expect() in our unit tests.
[10:36:49 EDT(-0400)] <colinclark> I think it's a great idea.
[10:37:27 EDT(-0400)] <michelled> great
[10:37:55 EDT(-0400)] <michelled> My only concern with using 'expect' is that it may get annoying if it's breaking because people are working on the test
[10:38:14 EDT(-0400)] <michelled> What I've been doing is writing the test and once I'm happy with it adding the expect statement.
[10:46:44 EDT(-0400)] <colinclark> michelled: Makes sense. I think it's a nice tool for sanity checking. The only problem I've encountered is if you're running tests in separate functions, such that the main test doesn't actually know how many tests will be run. This is probably a sign of a poorly written test, anyway.
[10:48:21 EDT(-0400)] <michelled> colinclark: true, unless there was a way to break up the expects. I'm not sure how it works - I've only been putting in a single expect at the top of a test.
[10:48:53 EDT(-0400)] <colinclark> michelled: I tried once to break up the expects, but it didn't work the way I hoped. Worth looking at more closely when we're not all so focussed on the release and conference prep.
[10:49:22 EDT(-0400)] <michelled> ya
[11:10:46 EDT(-0400)] <anastasiac> Hey, colinclark (and anyone else, I guess)
[11:11:00 EDT(-0400)] <anastasiac> I have a question about how we're supposed to set the 'affects' version in JIRA bugs
[11:11:04 EDT(-0400)] <colinclark> anastasiac: shoot
[11:11:47 EDT(-0400)] <anastasiac> I've just found a bug in Uploader trunk. I don't think it's present in the release 0.3, and I imagine it will be fixed before the actual 0.4 release
[11:11:53 EDT(-0400)] <anastasiac> so what version does it affect?
[11:12:27 EDT(-0400)] <colinclark> anastasiac: Good question.
[11:12:54 EDT(-0400)] <colinclark> Is it present in the beta?
[11:13:03 EDT(-0400)] <anastasiac> it will be, yes
[11:13:40 EDT(-0400)] <colinclark> anastasiac: It wouldn't hurt, since we're releasing it, to create a version for 0.4 beta
[11:13:49 EDT(-0400)] <anastasiac> that makes sense.
[11:14:04 EDT(-0400)] <anastasiac> but for future refernece, suppose we weren't releasing anything? what would we use?
[11:14:15 EDT(-0400)] <anastasiac> should we create a version called "trunk" for these cases?
[11:16:08 EDT(-0400)] <colinclark> anastasiac: We could. I wonder what EricDalquist does for this in uPortal.
[11:16:22 EDT(-0400)] <EricDalquist> huh?
[11:16:26 EDT(-0400)] <michelled> anastasiac, colinclark: I've been putting the affects version to the next release and the fix to the same value
[11:16:58 EDT(-0400)] <EricDalquist> I guess I need to read the log here ...
[11:17:02 EDT(-0400)] <colinclark> EricDalquist: Anastasiac was wondering what to do about the JIRA "affects" field for bugs that affect unreleased code.
[11:17:24 EDT(-0400)] <EricDalquist> we don't usually bother with an affects version then
[11:17:30 EDT(-0400)] <colinclark> Just leave it blank?
[11:17:32 EDT(-0400)] <EricDalquist> just set the fixfor
[11:17:35 EDT(-0400)] <EricDalquist> yup
[11:17:40 EDT(-0400)] <colinclark> Good to know, thatnks.
[11:17:48 EDT(-0400)] <EricDalquist> same thing for enhancements
[11:17:56 EDT(-0400)] <EricDalquist> since they don't really 'affect' any version
[11:18:09 EDT(-0400)] <michelled> that would be fine as long as when we release we go through the open bugs and set the affects version for stuff we didn't get to
[11:18:17 EDT(-0400)] <EricDalquist> yup
[11:18:24 EDT(-0400)] <colinclark> michelled: I've been doing the same as you. Affects and fixed as the same version.
[11:18:35 EDT(-0400)] <EricDalquist> let me look up our up release steps
[11:18:38 EDT(-0400)] <colinclark> It seems easiest in terms of JIRA gardening, but arguably could be confusing.
[11:18:54 EDT(-0400)] <EricDalquist> http://www.ja-sig.org/wiki/display/UPC/Cutting+a+uPortal+Release
[11:19:06 EDT(-0400)] <colinclark> EricDalquist: Thanks!
[11:19:11 EDT(-0400)] <anastasiac> cool, thanks EricDalquist
[11:19:20 EDT(-0400)] <EricDalquist> #4 there has some notes about updating jira
[12:57:42 EDT(-0400)] * colinclark (n=colin@ginger.caret.cam.ac.uk) has joined #fluid-work
[13:55:35 EDT(-0400)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[14:40:53 EDT(-0400)] * ecochran (n=ecochran@dhcp-169-229-212-6.LIPS.Berkeley.EDU) has joined #fluid-work
[15:31:15 EDT(-0400)] * michelled (n=team@142.150.154.197) has left #fluid-work
[16:56:52 EDT(-0400)] * ecochran (n=ecochran@dhcp-169-229-212-6.LIPS.Berkeley.EDU) has joined #fluid-work
[18:26:28 EDT(-0400)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[22:12:17 EDT(-0400)] * KevBurnsJr (n=kev@c-69-181-222-236.hsd1.ca.comcast.net) has joined #fluid-work
[22:21:20 EDT(-0400)] * KevBurnsJr is checking out the OSDPL ( http://uidesignpatterns.org/ )
[22:31:51 EDT(-0400)] * KevBurnsJr is moodling over Moodle