At this point I feel I have to ask why are we doing 1.2.1 from the
branch and *not* just moving ahead on the trunk?  It seems like about
the same amount of effort now... if 1.2.1 were just fixing a few
critical problems with 1.2 and then releasing ASAP, that would be fine,
but if it involves changing Axiom and Schema dependencies as well, why
not just take the time to get the fixes into trunk and do the release
from there (with another branch for 1.2.5 or whatever we end up calling it).

I'm OK with it either way but the more work that happens over on the
branch, the more likely it is that something will get dropped when we
move back to trunk....

Thoughts?

--Glen

Deepal Jayasinghe wrote:
> Hi Dennis,
>
> Now the release process is bit complex and we need to release dependent
> projects before Axis2 release (specially Axiom and XML Schema ) so I can
> not exactly tell the release date of Axis2 1.2.1. Any way let's try to
> do is as soon as we can.
>
> Thanks
> Deepal
>
> Dennis Sosnoski wrote:
>> I'd like to get this one fixed for 1.2.1, too:
>> https://issues.apache.org/jira/browse/AXIS2-2669
>>
>> Can anyone give a target date for the 1.2.1 release? I'm planning to
>> have this fixed within two days, but want to make sure I don't miss
>> the release window.
>>
>>  - Dennis
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.a...
> For additional commands, e-mail: axis-dev-help@ws.a...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.a...
For additional commands, e-mail: axis-dev-help@ws.a...