Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-11 Thread Amila Suriarachchi
On Wed, Jul 9, 2008 at 9:40 AM, Sanka Samaranayake [EMAIL PROTECTED] wrote: On Mon, Jul 7, 2008 at 7:39 PM, Nandana Mihindukulasooriya [EMAIL PROTECTED] wrote: Hi Glen, - Let's aim to get 1.4.1 out the door at the end of next week, i.e. July 18th (is that enough time, Nandana?). I

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-11 Thread Hans Guldager Knudsen
+1 for Nandana as the Release Manager I would also like to see the memory leak fixed for a 1.4.1 release : https://issues.apache.org/jira/browse/AXIS2-3870 How do we suggest bugs/fixes to be included in the 1.4.1 release ? In Jira ? /hans Amila Suriarachchi wrote: On Mon, Jul 7, 2008

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-10 Thread sumedha rubasinghe
+1 for Nandana as the release manager. /sumedha

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Deepal Jayasinghe
+1 Thank you! Deepal Davanum Srinivas wrote: Nandana, +1 from me for you to be the Release Manager for 1.4.1 IMHO, we should use 1.4 branch. The *ONLY* change should be the security change. Nothing more. thanks, dims On Mon, Jul 7, 2008 at 6:50 AM, Nandana Mihindukulasooriya [EMAIL

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Deepal Jayasinghe
Hehe :) I was wondering why did Glen tell that , I even went and read old mails :) Davanum Srinivas wrote: s/Deepal/Dims/ ? :) Glen Daniels wrote: | | Deepal, what are you so worried about, exactly? That it will take | forever to get the release out? | | IMHO, a point release is for fixing

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Saminda Abeyruwan
Guys, Axis2 module follow the version semantics of [major.minor] Thus, having addressing-1.4.1.mar will cause problem in version resolution. Am I making an absurd assumption here ? Saminda On Wed, Jul 9, 2008 at 12:26 PM, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hehe :) I was wondering

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Nandana Mihindukulasooriya
But it seems that we have done an Axis2 1.1.1 with adressing-1.1.1.mar and soapmonitor-1.1.1.mar modules. Will this be a problem ? thanks, nandana On Wed, Jul 9, 2008 at 3:33 PM, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Guys, Axis2 module follow the version semantics of [major.minor]

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Ruchith Fernando
IMHO when it comes to .mar files we should version them as x.yz In the case of 1.4.1 release the mar file versions can be: 1.41 This confirms to the module version constraints of Axis2. Thanks, Ruchith On Wed, Jul 9, 2008 at 3:33 PM, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Guys, Axis2

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Lahiru Sandakith
+1 for Nandana as the Release Manager Regards Lahiru Sandakith On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: Nandana, +1 from me for you to be the Release Manager for 1.4.1 IMHO, we should use 1.4 branch. The *ONLY* change should be the security change. Nothing

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-09 Thread Thilina Gunarathne
+1 for Nandana as the release manager.. thanks, Thilina On Wed, Jul 9, 2008 at 4:55 AM, Lahiru Sandakith [EMAIL PROTECTED] wrote: +1 for Nandana as the Release Manager Regards Lahiru Sandakith On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: Nandana, +1

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-08 Thread Asankha C. Perera
Nandana, +1 from me for you to be the Release Manager for 1.4.1 +1 for Nandana as the release manager Nandana I would also like to suggest https://issues.apache.org/jira/browse/AXIS2-3887 for inclusion, as this prevents Synapse from using the servlet transport effectively, since

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-08 Thread Sanka Samaranayake
On Mon, Jul 7, 2008 at 7:39 PM, Nandana Mihindukulasooriya [EMAIL PROTECTED] wrote: Hi Glen, - Let's aim to get 1.4.1 out the door at the end of next week, i.e. July 18th (is that enough time, Nandana?). I think we have to check Sanka's input on this. He will be fixing the major issue

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-08 Thread Ruchith Fernando
+1 for Nandana as the release manager. Thanks, Ruchith On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: Nandana, +1 from me for you to be the Release Manager for 1.4.1 IMHO, we should use 1.4 branch. The *ONLY* change should be the security change. Nothing more.

[Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Davanum Srinivas
Nandana, +1 from me for you to be the Release Manager for 1.4.1 IMHO, we should use 1.4 branch. The *ONLY* change should be the security change. Nothing more. thanks, dims On Mon, Jul 7, 2008 at 6:50 AM, Nandana Mihindukulasooriya [EMAIL PROTECTED] wrote: I would like to volunteer to be the

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Amila Suriarachchi
On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: Nandana, +1 from me for you to be the Release Manager for 1.4.1 + 1 from me. IMHO, we should use 1.4 branch. The *ONLY* change should be the security change. Nothing more. I think we need to fix any possible

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Davanum Srinivas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Exactly what i was afraid of :( Sigh! this is a *very* slippery slope. - -- dims Amila Suriarachchi wrote: | On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: | | Nandana, | | +1 from me for you to be the Release Manager for

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Glen Daniels
Deepal, what are you so worried about, exactly? That it will take forever to get the release out? IMHO, a point release is for fixing critical issues, and should not necessarily be limited to one particular issue. I think we should run this basically just like a regular release but with a

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Davanum Srinivas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 s/Deepal/Dims/ ? :) Glen Daniels wrote: | | Deepal, what are you so worried about, exactly? That it will take | forever to get the release out? | | IMHO, a point release is for fixing critical issues, and should not | necessarily be limited to one

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Glen Daniels
Davanum Srinivas wrote: s/Deepal/Dims/ ? :) Oh for crying out... sorry Dims!!! I was just reading a bunch of the JIRA edits from Deepal (and haven't had coffee yet today). *blush* --G - To unsubscribe, e-mail: [EMAIL

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Glen Daniels
Two more things. 1) Obviously +1 to Nandana as RM, which I forgot to say explicitly. :) 2) To be crystal clear, my suggestion is to time-bound the release and ONLY fix what can be finished in the allotted time, which should prevent the slippery slope problem. If people want we can also

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

2008-07-07 Thread Nandana Mihindukulasooriya
Hi Glen, - Let's aim to get 1.4.1 out the door at the end of next week, i.e. July 18th (is that enough time, Nandana?). I think we have to check Sanka's input on this. He will be fixing the major issue in policy. - As always it's good to go through at least one RC so people can kick the