();
}
Sorry for the delay, I'm under pressure here.
Best Regards
MAG
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ben Alex
Sent: vendredi 15 septembre 2006 11:08
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer
SEC-346 is just definitely not urgent - I think it was originally raised
because of a misunderstanding - so I've assigned it to 1.1.
Ben Alex wrote:
Hi everyone
23 issues are now resolved, with 3 more still outstanding.
The outstanding issues are SEC-304, SEC-348 and SEC-346, assigned to
Hi everyone
23 issues are now resolved, with 3 more still outstanding.
The outstanding issues are SEC-304, SEC-348 and SEC-346, assigned to
Marc Antoine, Scott and Luke respectively.
Would Marc Antoine, Scott and Luke please comment on these tasks, close
them, or assign them to a later release
Although not listed below, I went ahead and reverted the Siteminder
filter to the 1.0.1 version so that backward compatibility could be
preserved. I'll resolve SEC-319 in 1.1.0.
Scott (McCrory)
Ben Alex wrote:
Hi everyone
23 issues are now resolved, with 3 more still outstanding.
The
Carlos Sanchez wrote:
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
Ben,
what are the Siteminder improvements?
- Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Scott McCrory
Sent: Sunday, September 17, 2006 3:01 PM
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer
Garvey, Paul M (GE Comm Fin) wrote:
Ben,
what are the Siteminder improvements?
- Paul
SEC-319:
http://opensource.atlassian.com/projects/spring/browse/SEC-319
Scott
-
Take Surveys. Earn Cash. Influence the Future
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 was
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
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 the
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 all
It's not automated. As soon as we decide to go for m2 we can automate that.
On 9/15/06, Ben Alex [EMAIL PROTECTED] wrote:
Carlos Sanchez wrote:
I've been deploying snapshot in the maven2 repo after changing stuff
http://acegisecurity.sourceforge.net/repository/snapshots/
Is this an
Carlos Sanchez wrote:
Will it be possible to make a 1.0.2 bug release in the next two weeks?
I can go thorugh all the release process, i just would like to know if
people agree in taking what it is curently in svn and tag it as 1.0.2.
Hi Carlos
You want to be release manager? I would
On 9/7/06, Ben Alex [EMAIL PROTECTED] 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 all the release process, i just would like to know if
people agree in taking what it is curently in svn and tag it as 1.0.2.
Hi Carlos
14 matches
Mail list logo
