Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-17 Thread Scott McCrory
Ben Alex wrote: > Could other developers please finalize their 1.0.2-related tasks (see > http://opensource.atlassian.com/projects/spring/secure/BrowseProject.jspa). > Ben, I'd like to get the Siteminder improvements noted in SEC-319 in with the 1.0.2 release if permissible. The fix version w

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-17 Thread Ben Alex
Scott McCrory wrote: > Ben Alex wrote: >> Could other developers please finalize their 1.0.2-related tasks (see >> http://opensource.atlassian.com/projects/spring/secure/BrowseProject.jspa). >> > > Ben, I'd like to get the Siteminder improvements noted in SEC-319 in > with the 1.0.2 release if

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-17 Thread Scott McCrory
Ben Alex wrote: > Hi Scott > > As we're now post-1.0.0, it's important that we follow the APR > versioning guidelines which state that patch releases (ie 1.0.x) should > be binary and source compatible with previous releases in that series. > In other words, people should be able to simply "drop in

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-17 Thread Carlos Sanchez
I suggest copying trunk to branches/1.0.x and roll it back from there Work keeps going in trunk merging all bugfixes to 1.0.x branch as soon as they are committed. New features go to trunk only. That way we can release new features in 1.1 while still porting bugfixes to 1.0.x On 9/17/06, Scott

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-17 Thread Scott Battaglia
I'll take a look at the CAS-related JIRA issues tomorrow morning. I was out of the country for the past week which is why I didn't get a chance yet. -Scott Ben Alex wrote: > Carlos Sanchez wrote: > >> Will it be possible to make a 1.0.2 bug release in the next two weeks? >> I can go thorugh