Thorsten Scherler wrote:
Hi devs,
we all agree that we need a release. I would like to organize a release
in next month. I hope all our community will help to indicate which are
the issues that need to be attended for the release.
To get 2.0 out till 18.09.2007 we need to attend some issues. I am still
need to catch up with the latest ones but so far the following issues
need to be attended from the code base (I quote Jörn on all issues):
we still need to work on the PolicyAuthorizer issue (see
http://issues.apache.org/bugzilla/show_bug.cgi?id=42952), which i
consider a blocker. i'd like someone to review my suggestion, and then
we need to implement it.
if it turns out to be hairier than i thought, we should remove the
"session" role again, document this deficiency and get a release out
regardless. if it's reasonably easy to fix cleanly, we should fix it.
plus there is http://issues.apache.org/bugzilla/show_bug.cgi?id=40600,
which afaics is largely cosmetic since revisions work, but it should be
fixed nonetheless - plus i'm not sure there isn't a deeper problem
underneath...
I opened a bug to link the issues.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43160
Please add the issues that you think we need to attend before a release.
I do not hope there coming up much more but if so we as well can adapt
the time frame a wee bit but we need a release within the next couple of
month so let us all focus on fixing the remaining issues.
salu2
Good plan. I would love to see a release soon. I've added two bugs to
it. Both Kupu and BXE are broken (43157). Plus we have to figure out a
way to be able to allow users to create a page while other sitetree
modifications are taking place (43136).
From what I can tell, isn't 40600 a 1.2 issue?
I'll have 31 users pounding away on the latest trunk on Monday.
Hopefully it will be just fine, except for the page creation bug. I
think the memory leak I've seen in the older version I was running was
fixed at some point.
If the testing on Monday goes well, I should be able to get in and fix
up some of the bugs that I know how to handle next week. I should also
be able to go through and clear up the coding issues that FindBugs detects.
We should also get it so all of our tests pass.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
