Page Comparison

[13:10:51 CDT(-0500)] <serac> Guess I'm the only server committer here today.
[13:11:12 CDT(-0500)] <serac> Looks like https://issues.jasig.org/browse/CAS-987 is moving forward.
[13:12:30 CDT(-0500)] <serac> 3.2.1 client due soon.
[13:12:44 CDT(-0500)] <serac> Think that's it for updates.
[13:13:05 CDT(-0500)] <serac> Post your updates if you have any.
[13:22:59 CDT(-0500)] <serac> Hey battags.
[13:29:39 CDT(-0500)] <battags> hey
[13:29:40 CDT(-0500)] <battags> how
[13:29:45 CDT(-0500)] <battags> how's it going?
[13:29:56 CDT(-0500)] <serac> Good.
[13:30:11 CDT(-0500)] <serac> Sorry I haven't done a re-review of 3.2.1 client.
[13:30:27 CDT(-0500)] <serac> You want to cut that this weekend?
[13:30:57 CDT(-0500)] <battags> I can
[13:31:05 CDT(-0500)] <battags> its like a 1 line diff
[13:31:06 CDT(-0500)] <battags> there was only one minor change
[13:31:18 CDT(-0500)] <serac> That's why I haven't gotten to it.
[13:31:41 CDT(-0500)] <serac> Seems a poor use of time. But it's good practice I guess to do a pre-release review.
[13:32:12 CDT(-0500)] <serac> Where are we on 3.4.9 server release?
[13:33:33 CDT(-0500)] <battags> only remaining item is the issue we both commented on like 10 minutes ago
[13:33:51 CDT(-0500)] <serac> haha
[13:33:56 CDT(-0500)] <serac> Good deal.
[13:34:10 CDT(-0500)] <battags> in theory they could both make it out this weekend
[13:34:22 CDT(-0500)] <serac> Figured.
[13:34:26 CDT(-0500)] <battags> though that would leave clearpass undone
[13:34:30 CDT(-0500)] <battags> and not up to date
[13:35:15 CDT(-0500)] <serac> There's an issue in CAS jira for inclusion, right?
[13:38:27 CDT(-0500)] <serac> I can't find it.
[13:38:40 CDT(-0500)] <serac> This needs to be tracked as an issue with an assigned version.
[13:39:26 CDT(-0500)] <serac> And since there's no open issue affecting 3.4.9, then we're justified in proceeding. I also vaguely recall we discussed it was for 3.5.x anyway with some other stuff going in. Have to review casst notes.
[13:39:55 CDT(-0500)] <serac> Or #jasig-cas logs, rather.
[13:45:16 CDT(-0500)] <battags> I meant that ClearPass would be behind
[13:45:26 CDT(-0500)] <battags> i.e. there would be a ClearPass release that supported 3.4.6 or whatever
[13:45:34 CDT(-0500)] <battags> and not 3.4.9
[13:45:42 CDT(-0500)] <battags> not about its inclusion in the server
[13:45:46 CDT(-0500)] <serac> Do we have a history of synchronizing releases?
[13:45:57 CDT(-0500)] <serac> Sounds like a drag.
[13:46:05 CDT(-0500)] <battags> cooperative support usually keeps them in sync
[13:47:08 CDT(-0500)] <serac> But before the fact or after?
[13:47:19 CDT(-0500)] <serac> Or coordinated release?
[13:49:13 CDT(-0500)] <battags> usually close to or at the same time depending on who is doing the work
[13:50:35 CDT(-0500)] <serac> So what happened for past two releases?
[13:51:41 CDT(-0500)] <battags> I don't know.
[13:51:46 CDT(-0500)] <battags> well 3.4.8 we kind of snuck out
[13:52:22 CDT(-0500)] <serac> I'm just looking for a precedent, I guess.
[13:52:41 CDT(-0500)] <serac> Sounds like we have both, to coordinate releases and to release and let them catch up.
[13:52:58 CDT(-0500)] <battags> our releases aren't driven by cooperative support
[13:53:32 CDT(-0500)] <battags> we can give them a heads up
[13:53:39 CDT(-0500)] <serac> Sounds like the polite thing to do.
[13:53:43 CDT(-0500)] <serac> You got that?
[13:54:38 CDT(-0500)] <battags> if we're going to do that then let's not release over the weekend
[13:54:43 CDT(-0500)] <battags> I doubt any of them will be working
[13:55:05 CDT(-0500)] <serac> What I'm thinking. Need 48-72h business hours in this case.
[13:55:37 CDT(-0500)] <battags> let's target release for Thursday then
[13:56:13 CDT(-0500)] <serac> Sounds good.
[14:09:55 CDT(-0500)] <serac> Anything else, then?