fluid-work IRC Logs-2010-05-27

[10:44:50 EDT(-0400)] <sgithens> ok
[10:44:57 EDT(-0400)] <sgithens> maybe a few hours or half a day then?
[10:45:38 EDT(-0400)] <jamon> not sure sgithens, its an upstream isp problem from what i gather
[10:46:20 EDT(-0400)] <sgithens> cool, thanks for the update
[10:47:10 EDT(-0400)] * clown (~clown@142.150.154.156) has joined #fluid-work
[11:03:28 EDT(-0400)] * athena (~athena@c-24-16-144-164.hsd1.wa.comcast.net) has joined #fluid-work
[11:05:13 EDT(-0400)] <kasper> justin_o: got a question about testing, if you have time
[11:12:34 EDT(-0400)] <Justin_o> kasper: hello... sure
[11:14:22 EDT(-0400)] <kasper> ok, so the situation is: we have an upcomming release on cspace. By the end of today we have a partial code-freeze for some of the new features, and are planning to do testing on that, while the remaining features get integrated. So I guess I'm unsure of how much we can rely on the tests we are doing in this first QA round.. Theoretically, the integration of the remaining features should be fairly isolated codewise
[11:14:48 EDT(-0400)] <kasper> colinclark: you might have an opinion on this too ^
[11:15:38 EDT(-0400)] <Justin_o> kasper: it would depend on how isolated they are
[11:16:06 EDT(-0400)] * joost (~joost@dfki-119.dfki.uni-kl.de) has left #fluid-work
[11:16:12 EDT(-0400)] <kasper> justin_o: yeah :S
[11:16:29 EDT(-0400)] <Justin_o> kasper: if you for example you code freeze on feature "a", but part of feature "a" uses feature "b" which isn't frozen. Then at the very least you will have to retest that part of feature "a" that uses feature "b"
[11:16:41 EDT(-0400)] <Justin_o> sorry that's pretty abstracty
[11:16:50 EDT(-0400)] <kasper> justin_o: hehe, no that actually made great sense
[11:17:22 EDT(-0400)] * jhung (~U230@142.150.154.128) has joined #fluid-work
[11:18:09 EDT(-0400)] * clown (~clown@142.150.154.156) has joined #fluid-work
[11:18:23 EDT(-0400)] <kasper> justin_o: so, i was considering going ahead, full speed, on testing.. And when the new features are implemented (second test-phase), making sure that all the tests are re-run for at least one environment
[11:19:15 EDT(-0400)] <colinclark> hey, just catching up
[11:19:29 EDT(-0400)] <Justin_o> kasper: that should be okay.. sometimes you do get specific issues on specific configurations... I think you had a set of browsers that you blocked on, so you should probably try to retest on all of those
[11:21:00 EDT(-0400)] <kasper> justin_o: yeah ... or we could just retest on IE .. that should catch every single possible bug
[11:21:05 EDT(-0400)] <colinclark> kasper: Can you elaborate on why we're doing a partial freeze?
[11:21:20 EDT(-0400)] <colinclark> Is it a partial feature freeze, or a partial code freeze?
[11:21:42 EDT(-0400)] <colinclark> Where feature freeze in our case really just means a shift toward bug fixes and stabilization
[11:21:49 EDT(-0400)] <Justin_o> kasper: that's an option
[11:24:32 EDT(-0400)] <kasper> colinclark: the reason for the partial freeze is to allow the app layer to do integration. Chris is dependent on the UI and service layer to be done before she can do the final integration, so we decided it might be an idea to freeze UI/service on some features, and then have chris integrate, while the UI/service worked on the next set of features
[11:24:44 EDT(-0400)] <colinclark> ok
[11:24:50 EDT(-0400)] <kasper> colinclark: sort of an out-of-sync freeze
[11:25:07 EDT(-0400)] <colinclark> That approach makes some sense, but it does make QA much harder
[11:25:08 EDT(-0400)] <kasper> and it would be codefreeze
[11:25:17 EDT(-0400)] <colinclark> This is where hopefully we'll get some wicked automated tests and it will be no big deal
[11:25:22 EDT(-0400)] <colinclark> But that's still a twinkle in our eyes
[11:25:37 EDT(-0400)] <colinclark> So what are the particular features that are being frozen?
[11:26:30 EDT(-0400)] <kasper> colinclark: yeah, in some ways it makes .. on the other hand it allows us to do preliminary testing on some fully integrated features earlier, which in turn will allow us to catch/fix bugs earlier.. making my life a lot less stressful close to deadline
[11:26:45 EDT(-0400)] <colinclark> yeah
[11:26:59 EDT(-0400)] <kasper> yeah, in some ways it makes (QA harder)*
[11:27:54 EDT(-0400)] <kasper> currently we have loans in and out and object tab edit frozen
[11:28:51 EDT(-0400)] <kasper> by the end of today, the above will freeze for app-layer too, while UI/service will freeze for assigning roles to users, repeatable fields, roles and permissions
[11:34:46 EDT(-0400)] <jamon> Justin_o: so turns out that the infusion checkout with testswarm uses localhost for every url.. having to convert all those
[11:53:25 EDT(-0400)] <Justin_o> jamon: i think you might be able to do it in just one spot
[11:53:29 EDT(-0400)] <Justin_o> i'll come over
[12:03:45 EDT(-0400)] * kasper_ (~kasper@189.130.73.162) has joined #fluid-work
[12:18:31 EDT(-0400)] <jamon> sgithens: think you should be able to get through now
[12:20:45 EDT(-0400)] <jessm> kasper_: i know I for one have some confusion when it comes to these mid-cycle freezes
[12:21:07 EDT(-0400)] <jessm> kasper_: probably not warranted – i'm sure others have a much clearer understanding of what needs to be prepped for freezing?
[12:21:43 EDT(-0400)] <jessm> kasper_: looking with my 1/2 eyeball at the list and at the calendar it isn't apparent to me what is on deck for freezability
[12:22:12 EDT(-0400)] * jessm notes this should probably be typed in the cspace channel
[12:22:40 EDT(-0400)] <kasper_> jessm: ok, thanks for letting me know .. I will try to figure out a way to make it more clear
[12:23:03 EDT(-0400)] <jessm> kasper_: for us 1/2 eyers at least
[12:23:29 EDT(-0400)] <kasper_> hehe ... i think that's most of us
[12:24:53 EDT(-0400)] <sgithens> jamon: cheers
[12:44:50 EDT(-0400)] * kasper (~kasper@189.130.73.162) has joined #fluid-work
[12:55:12 EDT(-0400)] <colinclark> jhung: hey, how's it going?
[13:01:29 EDT(-0400)] * jmartin (~jmartin@wsip-72-215-204-133.ph.ph.cox.net) has joined #fluid-work
[13:04:58 EDT(-0400)] <Justin_o> colinclark: just saw your message to jhung, he has stepped out for lunch
[13:05:45 EDT(-0400)] <colinclark> ah ok
[14:09:24 EDT(-0400)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[14:14:03 EDT(-0400)] * athena7 (~athena@c-76-121-97-221.hsd1.wa.comcast.net) has joined #fluid-work
[14:31:25 EDT(-0400)] * colinclark_ (~colin@142.150.154.101) has joined #fluid-work
[14:34:20 EDT(-0400)] <Justin_o> colinclark: i've attached a patch for the changes we needed to get testswarm working
[14:34:21 EDT(-0400)] <Justin_o> http://issues.fluidproject.org/secure/ManageAttachments.jspa?id=14491
[14:43:41 EDT(-0400)] * athena (~athena@dsl231-038-096.sea1.dsl.speakeasy.net) has joined #fluid-work
[15:34:27 EDT(-0400)] * michelled (~michelled@142.150.154.141) has joined #fluid-work
[16:41:28 EDT(-0400)] * elicochran (~elicochra@dhcp-169-229-212-68.LIPS.Berkeley.EDU) has joined #fluid-work
[17:08:24 EDT(-0400)] * jhung (~U230@142.150.154.128) has left #fluid-work
[17:09:52 EDT(-0400)] * Justin_o (~Justin@142.150.154.171) has left #fluid-work
[17:13:19 EDT(-0400)] * athena (~athena@c-76-121-97-221.hsd1.wa.comcast.net) has joined #fluid-work
[17:40:09 EDT(-0400)] * clown (~clown@142.150.154.156) has left #fluid-work
[17:40:31 EDT(-0400)] * anastasiac (~team@142.150.154.193) has left #fluid-work
[20:58:10 EDT(-0400)] * jmartin (~jmartin@wsip-72-215-204-133.ph.ph.cox.net) has left #fluid-work