Dennis,

If someone is willing to take the lead, sure. taking into account
Glen's 3 points here. Could you please do a bit of research to
identify JIRA's to get us started?

thanks,
dims

On 5/24/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Hi Dennis:

I for one am totally behind a 1.2.1 release, off the branch, as long as:

1) There is a CLEAR RELEASE PLAN (i.e. which JIRAs are going to be fixed
exactly)

2) No major new work happens on the branch, just bug fixes (and those
bug fixes must be reflected on the trunk so the JIRA can really be closed)

3) We do it SOON.

If we can easily fix the "badly broken" parts with a process like that,
let's do it!  Otherwise, let's push forward and get 1.3 into shape,
which will take a little longer but is essentially the same idea -
figure out what we want in the release, slowly coalesce the work on
trunk into shape, and then follow the release guidelines we agreed upon
(and which I still need to get up on the website!!).  And yes, then
there's 1.4 to look forward to! :)  Release early and often.

So let me ask you - do you think the current stuff on the 1.2 branch has
already resolved the "badly broken" parts enough to release it?  And if
not what particular JIRAs would you fix there?

--Glen

Dennis Sosnoski wrote:
> Hi dims,
>
> I think it's been clear for some time that the 1.2 release is badly
> broken. If you really think the solution is a 1.3 release, and that that
> wouldn't break as many things as it fixes, then we should push to get
> one out quickly. And if 1.3 *does* break a bunch of things, well then
> there's always 1.4, isn't there? :-)
>
>  - Dennis
>
> --
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Axis2 Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
> Davanum Srinivas wrote:
>> Sorry, am a bit frustrated today. See this for example:
>> https://issues.apache.org/jira/browse/AXIS2-2706
>>
>> We can't stop at 80%, last 20% is harder than the first 80 :(
>>
>> -- dims
>>
>> On 5/24/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Davanum Srinivas wrote:
>>> > Dear Dev team,
>>> >
>>> > The recent thread on setting defaults via yet another properties file
>>> > reminds me that we are *NOT* keeping our eye on the ball. All of us
>>> > want to do cool stuff, but can we please get our existing stuff
>>> > working right first? See the following thread for example:
>>> >
>>> > http://marc.info/?l=axis-user&m=117997437104760&w=2
>>>
>>> Yes I agree this is a cool things and also a result of hanging around in
>>> axis-user list.
>>> Please see : http://marc.info/?l=axis-user&m=117993610523772&w=2.
>>>
>>> I hope not allowing user to change the SOAP version, within a SOAP
>>> engine is detrimental to Axis2. Having a property file to do it just an
>>> extension of it. I know we have tons of stuff in Axis2, which are either
>>> not documented nor exposed. I take a part of that blame too :)
>>>
>>> Thanks,
>>> Chinthaka
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.3 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>>
>>> iD8DBQFGVbIBjON2uBzUhh8RAm3rAJ99TBqzaVhWCyDZgdolbG9CepX1lACeIA4v
>>> vWdnxRUW8WQDmXX/dNLIccQ=
>>> =MqCL
>>> -----END PGP SIGNATURE-----
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to