I was hoping to find some time this week to apply the ten patches, and run 2.0.8 against the new XW release, but yet another task has just been dropped in my lap, and time will be very short this month. If no one else has time to spend on a 2.0.8 release, I'll try to schedule some time in May.
After 2.0.8, we might want to push everything else to 2.1.0. AFAIK, the remaining 2.1.0 trigger is moving the portlet code to a plugin, and the blocker there is a resolution of the notion of a abstracting the URL handling. As to release management, we might not want to create tickets as subtasks of the omnibus ticket. If the ticket is not resolved within that milestone, then we have to go through a series of menus to change its parent. We will spend more time moving the ticket than it took to create it. Worse, there seems to be no way to promote a subtask to a task, so we limit our options. -Ted. On 4/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Is anyone else interest in volunteering as the Struts 2.0.8 release manager. I'll be spending some of my volunteer hours helping the Click framework join the ASF, as one of the podling mentors, and I don't want to stretch myself too thin. At this point, the release trigger would be a new XWork 2 release. The process is running smoothly now. The major bull work is applying contributor patches. -Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
