[EMAIL PROTECTED] wrote:
Didn't you fix this one? If so, why is this not included in the 1.1.1 distribution?
Yes, in fact both bugs are fixed in svn, however, 1.1.1 was cut PRIOR to the fix and we will not recut it.
The Portals PMC is currently trying to flush out our release processes so that they are common across the projects. One of the criteria that seems like it will be included is that test builds are numbered and voted on to be a release. Once a test build is cut, it will not be recut. If a new build is required, the version number will incremented and a new vote started.
In this case, I do not think that the current issues are significant enough to terminate the vote on 1.1.1. I propose moving forward with 1.1.1 and releasing 1.1.2 with in a couple of weeks (currently there are 5 jira tickets addressed in it, and there are a couple more I htink that can be knocked off in the time).
One of the great advantages of release early, release often is that we don't have to have PERFECT builds. We want them to meet quality standards, but we also want to push them out. The reality is that 1.1.1 has several improvements over 1.1.0 and only this one regression.
David
