on monday, I will commit the spec as 3.0 release as well.

Sent while mobile.

> Am 01.05.2014 um 09:54 schrieb Jérôme LELEU <[email protected]>:
> 
> Hi,
> 
> Misagh has just merged the last fix for 4.0 
> (https://github.com/Jasig/cas/pull/427).
> I will cut the release next week: on Monday (4/5/14) or Wednesday (4/7/14) if 
> everyone is ok.
> Thanks.
> Best regards,
> Jérôme
> 
> 
> 
> 2014-04-17 18:26 GMT+02:00 Misagh Moayyed <[email protected]>:
>> Yes that’s the thought. 28th would also be fine. There has been some 
>> discussion on #246, and so as soon as we are able to resolve that, we should 
>> be ok to proceed with GA, if the timing is acceptable.
>> 
>>  
>> 
>> From: Jérôme LELEU [mailto:[email protected]] 
>> Sent: Thursday, April 17, 2014 1:17 AM
>> To: [email protected]
>> Subject: Re: [cas-dev] [cas-user] Schedule for CAS 4.0
>> 
>>  
>> 
>> Hi,
>> 
>>  
>> 
>> Are you proposing to cut the final release (GA) on April, the 25th? I agree, 
>> it's time to release the 4.0, even if it could be done one or two weeks 
>> later...
>> 
>>  
>> 
>> BTW, I'm willing to do the release, but as I'm in holidays, I can only 
>> handle that from April, the 28th.
>> 
>>  
>> 
>> Thanks.
>> 
>> Best regards,
>> 
>> Jérôme
>> 
>>  
>> 
>>  
>> 
>> 2014-04-16 19:22 GMT+02:00 Misagh Moayyed <[email protected]>:
>> 
>> Team,
>> I suppose the last change that we need to review and take action on is the
>> following pull:
>> https://github.com/Jasig/cas/pull/426
>> 
>> May I suggest that once the fate of this pull is decided, we'd take action
>> to proceed with the GA? And with that, could we perhaps agree on a
>> timeline, or say, Friday the 25th? This would give us 3 weeks before the
>> last RC which should be enough time to weed out issues.
>> 
>> Misagh
>> 
>> > -----Original Message-----
>> > From: Misagh Moayyed [mailto:[email protected]]
>> > Sent: Wednesday, April 02, 2014 12:06 PM
>> > To: '[email protected]'
>> > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0
>> >
>> > Also, I realize now it makes better sense for the build to check for
>> commit
>> > messages and adherence to other conventions *after* it's been able to
>> > successfully build and test the pull. We would have been able to capture
>> the
>> > failure in advance.
>> >
>> > > -----Original Message-----
>> > > From: Misagh Moayyed [mailto:[email protected]]
>> > > Sent: Wednesday, April 02, 2014 12:02 PM
>> > > To: [email protected]
>> > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0
>> > >
>> > > Another issue; pull #415 [1] broke the following test in
>> cas-server-core:
>> > > MultifactorAuthenticationTests#testAllowsAccessToHighSecurityServiceWi
>> > > thPa
>> > > sswordAndOTPViaRenew()
>> > >
>> > > This is where the test failure comes from:
>> > >
>> > > if (!(current.getPrincipal().equals(original.getPrincipal())
>> > >        && current.getAttributes().equals(original.getAttributes()))) {
>> > >      throw new MixedPrincipalException(current,
>> > > current.getPrincipal(), original.getPrincipal()); }
>> > >
>> > > The comparison on authentication attribute fails. What is the
>> intention
>> > here?
>> > > Should the principal attributes be compared if we are checking for
>> > > mixed principal conditions? If so, should that just be captured inside
>> > > the
>> > > equals() of SimplePrincipal?
>> > >
>> > > [1] https://github.com/Jasig/cas/pull/415
>> > >
>> > > > -----Original Message-----
>> > > > From: Misagh Moayyed [mailto:[email protected]]
>> > > > Sent: Wednesday, April 02, 2014 10:10 AM
>> > > > To: '[email protected]'
>> > > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0
>> > > >
>> > > > Excellent. I'll get going.
>> > > >
>> > > > > -----Original Message-----
>> > > > > From: Marvin Addison [mailto:[email protected]]
>> > > > > Sent: Wednesday, April 02, 2014 10:04 AM
>> > > > > To: [email protected]
>> > > > > Subject: Re: [cas-dev] [cas-user] Schedule for CAS 4.0
>> > > > >
>> > > > > > Thanks. Keep us posted on the progress please.
>> > > > >
>> > > > > Ldaptive 1.0.3 has been released and is available in Maven Central
>> > > > > [1], so we should be good to bump the version and move forward.
>> > > > >
>> > > > > M
>> > > > >
>> > > > > http://search.maven.org/#artifactdetails%7Corg.ldaptive%7Cldaptive
>> > > > > %7
>> > > > > C1
>> > > > > .0.3%7C
>> > > > > jar
>> > > > >
>> > > > > --
>> > > > > You are currently subscribed to [email protected] as:
>> > > > > [email protected] To unsubscribe, change settings or access
>> > > > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
>> > >
>> > > --
>> > > You are currently subscribed to [email protected] as:
>> > > [email protected] To unsubscribe, change settings or access
>> > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
>> 
>> --
>> You are currently subscribed to [email protected] as: [email protected]
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-dev
>> 
>>  
>> 
>>  
>> -- 
>> You are currently subscribed to [email protected] as: 
>> [email protected]
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-dev
>>  -- 
>> You are currently subscribed to [email protected] as: [email protected]
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-dev
> 
> -- 
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-dev

Reply via email to