Return-Path: X-Original-To: apmail-synapse-dev-archive@www.apache.org Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37DC6BDE8 for ; Mon, 2 Jan 2012 06:36:45 +0000 (UTC) Received: (qmail 81909 invoked by uid 500); 2 Jan 2012 06:36:44 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 81701 invoked by uid 500); 2 Jan 2012 06:36:36 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 81692 invoked by uid 99); 2 Jan 2012 06:36:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 06:36:31 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kasun147@gmail.com designates 209.85.215.170 as permitted sender) Received: from [209.85.215.170] (HELO mail-ey0-f170.google.com) (209.85.215.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 06:36:23 +0000 Received: by eaa13 with SMTP id 13so4777865eaa.15 for ; Sun, 01 Jan 2012 22:36:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XiYkgfN1M5pp/+8Hjs9Hm0k9m4IrHXRawDFIxyklcLQ=; b=Y3y+QTkGuzmD68DzL8Jr/1ImXciXH9uauHkF2MHwuAugU+PpYaBiI8zbPMxNkxhvx8 3CAlbloW2fCR7b9ojwGL2WKXzZQCcwMctXBxoB10d6a8vzNHYoXmXGWlHmr98VTfjHjk 9hF3PmrTR7SdT9jy0VYts3XUaqVtaSnQ4C1cU= MIME-Version: 1.0 Received: by 10.204.152.216 with SMTP id h24mr8089293bkw.15.1325486161823; Sun, 01 Jan 2012 22:36:01 -0800 (PST) Received: by 10.204.57.67 with HTTP; Sun, 1 Jan 2012 22:36:01 -0800 (PST) In-Reply-To: References: Date: Mon, 2 Jan 2012 12:06:01 +0530 Message-ID: Subject: Re: [VOTE] Release Synapse 2.1.0 From: Kasun Indrasiri To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=0015175cdf38d486cd04b585cb3c X-Virus-Checked: Checked by ClamAV on apache.org --0015175cdf38d486cd04b585cb3c Content-Type: text/plain; charset=ISO-8859-1 Apparently, mvn release:prepare -DdryRun=true seems to fail with maven 2.2.1. I think we need to use maven 3.x to overcome that issue. On Thu, Dec 29, 2011 at 10:38 PM, Kasun Indrasiri wrote: > > > On Thu, Dec 29, 2011 at 7:02 PM, Andreas Veithen < > andreas.veithen@gmail.com> wrote: > >> Did you execute a dry-run as explained in [1]? >> >> Yeah. The dry-run was successful. > >> Andreas >> >> [1] >> http://www.apache.org/dev/publishing-maven-artifacts.html#prepare-poms >> >> On Thu, Dec 29, 2011 at 10:34, Kasun Indrasiri >> wrote: >> > We have published the 2.1.0-SNAPSHOT artifacts to the repository [1]. >> > So, if everything is ok, we can proceed with the staging of 2.1.0 >> release. >> > >> > [1] >> https://repository.apache.org/content/repositories/snapshots/org/apache/synapse/ >> > >> > >> > On Wed, Dec 28, 2011 at 2:27 AM, Andreas Veithen < >> andreas.veithen@gmail.com> >> > wrote: >> >> >> >> The Axis2 project had the same issue. The problem is that this tends >> >> to become a vicious circle: >> >> - Because releases are not very frequent, they are painful. >> >> - Because releases are painful, they are not very frequent. >> >> - Because releases are not very frequent, people tend to push all >> >> kinds of changes into the release, which creates new difficulties and >> >> further delays the release. >> >> >> >> Here are the ingredients that we used to break out of that vicious >> >> circle (except for the Axis2 Transports project, which is still caught >> >> in that vicious circle): >> >> - Use maven-release-plugin and Nexus to create branches and to perform >> >> releases. This makes the process easier and more reproducible. >> >> - Eliminate as many manual steps from the release procedure as >> possible. >> >> - Document the release process, in particular the manual steps that >> >> still need to be performed. >> >> - Use a strategy to maintain the release/maintenance branch(es) that >> >> ensures that all changes are always included in the trunk and that >> >> makes it easy to determine what changes have been merged to the >> >> branch. This avoids unpleasant surprises when doing a new major >> >> release and ensures that the branch created during a major release can >> >> be used later to produce maintenance releases. That in turn helps >> >> increasing the release frequency and allows to refine the release >> >> process. >> >> - Make sure that several people can act (and effectively do act) as >> >> release managers. E.g. since we switched to Nexus, every project >> >> (Axis2, Rampart and Sandesha2) has been released at least once by >> >> Sagara and at least once by myself. >> >> - A frequent problem is that when starting to plan a release, people >> >> wake up and try to put non-critical issues or feature requests on the >> >> critical path for the release (That's what happened with the Axis2 >> >> Transports release). Don't let that happen. Instead tell people that >> >> they should work on these issues after the release and then ask for a >> >> maintenance release once the changes are ready. >> >> >> >> Andreas >> >> >> >> On Tue, Dec 27, 2011 at 15:42, Hiranya Jayathilaka < >> hiranya911@gmail.com> >> >> wrote: >> >> > I believe that the main reason for this mess is our poor release >> >> > frequency. >> >> > If we can do a release at least once every 3-4 months, trunk and >> >> > everything >> >> > else will stabilize gradually. Part of my recent efforts with the new >> >> > documentation, integration tests and dependency cleanup was intended >> to >> >> > lay >> >> > a foundation on which we can do quick and frequent releases with >> small >> >> > incremental improvements. This release has been a great learning >> >> > experience >> >> > so far. We are learning where things have gone wrong and are actively >> >> > taking >> >> > action to fix them. >> >> > >> >> > Thanks, >> >> > Hiranya >> >> > >> >> > >> >> > On Tue, Dec 27, 2011 at 7:41 PM, Andreas Veithen >> >> > >> >> > wrote: >> >> >> >> >> >> On Tue, Dec 27, 2011 at 06:02, Hiranya Jayathilaka >> >> >> >> >> >> wrote: >> >> >> > >> >> >> > >> >> >> > On Tue, Dec 27, 2011 at 4:58 AM, Andreas Veithen >> >> >> > >> >> >> > wrote: >> >> >> >> >> >> >> >> -1 >> >> >> >> >> >> >> >> The Maven artifacts don't meet the requirements for publication >> to >> >> >> >> Maven Central (see [1] and in particular the link to [2]). In >> >> >> >> particular each artifact must be signed. Each artifact must also >> >> >> >> have >> >> >> >> an MD5 checksum (that is not explicitly mentioned in [2] because >> the >> >> >> >> maven-deploy-plugin normally takes care of this). >> >> >> >> >> >> >> >> I'm not even sure if releasing artifacts using the old >> >> >> >> m2-ibiblio-rsync-repository thing is still supported. What is >> sure >> >> >> >> is >> >> >> >> that the only documented way is via Nexus. >> >> >> > >> >> >> > >> >> >> > Can you please explain how that's done? Should we follow the >> >> >> > instructions >> >> >> > on http://www.apache.org/dev/publishing-maven-artifacts.html? >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> There is also a regression with respect to the project branding >> >> >> >> requirements. Apparently the change in r1051752 was never >> applied to >> >> >> >> the trunk and is missing in 2.1.0. >> >> >> > >> >> >> > >> >> >> > No it is available in 2.1. Take a look at the links available on >> the >> >> >> > Main >> >> >> > Menu of the site. It's not yet committed to the trunk. But we >> still >> >> >> > haven't >> >> >> > merged the new documentation into the trunk. That will be done >> pretty >> >> >> > soon. >> >> >> >> >> >> The change not only modifies the links, but also adds a disclaimer >> >> >> related to trademarks. It's not included in 2.1 and if you now >> replace >> >> >> the documentation on the trunk with the one from the 2.1 branch, it >> >> >> will be definitely lost. Obviously it is easy to add that again, but >> >> >> I'm pretty sure that this will not be the only change that is lost >> in >> >> >> the process. >> >> >> >> >> >> I would strongly recommend that before continuing with the effort to >> >> >> release 2.1 the project sorts this out and establishes a clear >> >> >> branching strategy to stop that mess. Otherwise the 2.2/3.0 release >> >> >> will be even worse. >> >> >> >> >> >> > Thanks, >> >> >> > Hiranya >> >> >> > >> >> >> >> >> >> >> >> That seems to be a general problem >> >> >> >> in the Synapse project, namely that there is no effective >> strategy >> >> >> >> to >> >> >> >> manage the release branch and to ensure that all relevant changes >> >> >> >> are >> >> >> >> in the trunk. In Axis2/Rampart/Sandesha2 we have eradicated that >> >> >> >> problem by using a consistent (yet simple) strategy to manage the >> >> >> >> release/maintenance branches. >> >> >> >> >> >> >> >> Andreas >> >> >> >> >> >> >> >> [1] http://www.apache.org/dev/publishing-maven-artifacts.html >> >> >> >> [2] >> >> >> >> >> >> >> >> >> https://docs.sonatype.org/display/Repository/Central+Sync+Requirements >> >> >> >> >> >> >> >> On Mon, Dec 26, 2011 at 16:30, Kasun Indrasiri < >> kasun147@gmail.com> >> >> >> >> wrote: >> >> >> >> > Hi Devs, >> >> >> >> > >> >> >> >> > This is the call for votes to release Apache Synapse-2.1.0. >> >> >> >> > >> >> >> >> > Please review the signed artifacts: >> >> >> >> > http://people.apache.org/~kasun/synapse/2.1-RC1/artifacts/ >> >> >> >> > >> >> >> >> > The m2 repository is available at: >> >> >> >> > http://people.apache.org/~kasun/synapse/2.1-RC1/m2_repo/ >> >> >> >> > >> >> >> >> > Revamped site for this release is available at: >> >> >> >> > http://people.apache.org/~kasun/synapse/2.1-RC1/site/ >> >> >> >> > >> >> >> >> > SVN Info: >> >> >> >> > revision is 1222784 on >> >> >> >> > https://svn.apache.org/repos/asf/synapse/branches/2.1 >> >> >> >> > >> >> >> >> > Here is my +1 to declaring the above dist as Synapse-2.1.0. >> >> >> >> > >> >> >> >> > Thanks, >> >> >> >> > -- >> >> >> >> > Kasun Indrasiri >> >> >> >> > Associate Technical Lead, >> >> >> >> > WSO2 Inc. - "Lean . Enterprise . Middleware" - >> >> >> >> > http://www.wso2.com/ >> >> >> >> > Blog : http://kasunpanorama.blogspot.com/ >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org >> >> >> >> For additional commands, e-mail: dev-help@synapse.apache.org >> >> >> >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Hiranya Jayathilaka >> >> >> > Associate Technical Lead; >> >> >> > WSO2 Inc.; http://wso2.org >> >> >> > E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491 >> >> >> > Blog: http://techfeast-hiranya.blogspot.com >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org >> >> >> For additional commands, e-mail: dev-help@synapse.apache.org >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Hiranya Jayathilaka >> >> > Associate Technical Lead; >> >> > WSO2 Inc.; http://wso2.org >> >> > E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491 >> >> > Blog: http://techfeast-hiranya.blogspot.com >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org >> >> For additional commands, e-mail: dev-help@synapse.apache.org >> >> >> > >> > >> > >> > -- >> > Kasun Indrasiri >> > Associate Technical Lead, >> > WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/ >> > Blog : http://kasunpanorama.blogspot.com/ >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org >> For additional commands, e-mail: dev-help@synapse.apache.org >> >> > > > -- > Kasun Indrasiri > Associate Technical Lead, > WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/ > Blog : http://kasunpanorama.blogspot.com/ > > -- Kasun Indrasiri Associate Technical Lead, WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/ Blog : http://kasunpanorama.blogspot.com/ --0015175cdf38d486cd04b585cb3c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Apparently, mvn release:prepare -DdryRun=3Dtrue seems to fail with maven 2.= 2.1. I think we need to use maven 3.x to overcome that issue.=A0=A0

=
On Thu, Dec 29, 2011 at 10:38 PM, Kasun Indrasir= i <kasun147@gmai= l.com> wrote:


On Thu, Dec 29, 2011 at 7:02 PM, Andreas Veithen <andreas= .veithen@gmail.com> wrote:
Did you execute a dry-run as explained in [1]?

Yeah. The dry-run was successful. =A0
Andreas

[1] http://www.apache.org/dev/publishing-maven-ar= tifacts.html#prepare-poms

On Thu, Dec 29, 2011 at 10:34, Kasun Indrasiri <kasun147@gmail.com> wrote:
> We have published the 2.1.0-SNAPSHOT artifacts to the repository [1].<= br> > So, if everything is ok, we can proceed with the staging of 2.1.0 rele= ase.
>
> [1]=A0https://repository.apache.or= g/content/repositories/snapshots/org/apache/synapse/
>
>
> On Wed, Dec 28, 2011 at 2:27 AM, Andreas Veithen <andreas.veithen@gmail.com= >
> wrote:
>>
>> The Axis2 project had the same issue. The problem is that this ten= ds
>> to become a vicious circle:
>> - Because releases are not very frequent, they are painful.
>> - Because releases are painful, they are not very frequent.
>> - Because releases are not very frequent, people tend to push all<= br> >> kinds of changes into the release, which creates new difficulties = and
>> further delays the release.
>>
>> Here are the ingredients that we used to break out of that vicious=
>> circle (except for the Axis2 Transports project, which is still ca= ught
>> in that vicious circle):
>> - Use maven-release-plugin and Nexus to create branches and to per= form
>> releases. This makes the process easier and more reproducible.
>> - Eliminate as many manual steps from the release procedure as pos= sible.
>> - Document the release process, in particular the manual steps tha= t
>> still need to be performed.
>> - Use a strategy to maintain the release/maintenance branch(es) th= at
>> ensures that all changes are always included in the trunk and that=
>> makes it easy to determine what changes have been merged to the >> branch. This avoids unpleasant surprises when doing a new major >> release and ensures that the branch created during a major release= can
>> be used later to produce maintenance releases. That in turn helps<= br> >> increasing the release frequency and allows to refine the release<= br> >> process.
>> - Make sure that several people can act (and effectively do act) a= s
>> release managers. E.g. since we switched to Nexus, every project >> (Axis2, Rampart and Sandesha2) has been released at least once by<= br> >> Sagara and at least once by myself.
>> - A frequent problem is that when starting to plan a release, peop= le
>> wake up and try to put non-critical issues or feature requests on = the
>> critical path for the release (That's what happened with the A= xis2
>> Transports release). Don't let that happen. Instead tell peopl= e that
>> they should work on these issues after the release and then ask fo= r a
>> maintenance release once the changes are ready.
>>
>> Andreas
>>
>> On Tue, Dec 27, 2011 at 15:42, Hiranya Jayathilaka <hiranya911@gmail.com>=
>> wrote:
>> > I believe that the main reason for this mess is our poor rele= ase
>> > frequency.
>> > If we can do a release at least once every 3-4 months, trunk = and
>> > everything
>> > else will stabilize gradually. Part of my recent efforts with= the new
>> > documentation, integration tests and dependency cleanup was i= ntended to
>> > lay
>> > a foundation on which we can do quick and frequent releases w= ith small
>> > incremental improvements. This release has been a great learn= ing
>> > experience
>> > so far. We are learning where things have gone wrong and are = actively
>> > taking
>> > action to fix them.
>> >
>> > Thanks,
>> > Hiranya
>> >
>> >
>> > On Tue, Dec 27, 2011 at 7:41 PM, Andreas Veithen
>> > <andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> On Tue, Dec 27, 2011 at 06:02, Hiranya Jayathilaka
>> >> <hiranya911@gmail.com>
>> >> wrote:
>> >> >
>> >> >
>> >> > On Tue, Dec 27, 2011 at 4:58 AM, Andreas Veithen
>> >> > <andreas.veithen@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> -1
>> >> >>
>> >> >> The Maven artifacts don't meet the requireme= nts for publication to
>> >> >> Maven Central (see [1] and in particular the lin= k to [2]). In
>> >> >> particular each artifact must be signed. Each ar= tifact must also
>> >> >> have
>> >> >> an MD5 checksum (that is not explicitly mentione= d in [2] because the
>> >> >> maven-deploy-plugin normally takes care of this)= .
>> >> >>
>> >> >> I'm not even sure if releasing artifacts usi= ng the old
>> >> >> m2-ibiblio-rsync-repository thing is still suppo= rted. What is sure
>> >> >> is
>> >> >> that the only documented way is via Nexus.
>> >> >
>> >> >
>> >> > Can you please explain how that's done? Should w= e follow the
>> >> > instructions
>> >> > on=A0http://www.apache.org/dev/publishi= ng-maven-artifacts.html?
>> >> >
>> >> >>
>> >> >>
>> >> >> There is also a regression with respect to the p= roject branding
>> >> >> requirements. Apparently the change in r1051752 = was never applied to
>> >> >> the trunk and is missing in 2.1.0.
>> >> >
>> >> >
>> >> > No it is available in 2.1. Take a look at the links = available on the
>> >> > Main
>> >> > Menu of the site. It's not yet committed to the = trunk. But we still
>> >> > haven't
>> >> > merged the new documentation into the trunk. That wi= ll be done pretty
>> >> > soon.
>> >>
>> >> The change not only modifies the links, but also adds a d= isclaimer
>> >> related to trademarks. It's not included in 2.1 and i= f you now replace
>> >> the documentation on the trunk with the one from the 2.1 = branch, it
>> >> will be definitely lost. Obviously it is easy to add that= again, but
>> >> I'm pretty sure that this will not be the only change= that is lost in
>> >> the process.
>> >>
>> >> I would strongly recommend that before continuing with th= e effort to
>> >> release 2.1 the project sorts this out and establishes a = clear
>> >> branching strategy to stop that mess. Otherwise the 2.2/3= .0 release
>> >> will be even worse.
>> >>
>> >> > Thanks,
>> >> > Hiranya
>> >> >
>> >> >>
>> >> >> That seems to be a general problem
>> >> >> in the Synapse project, namely that there is no = effective strategy
>> >> >> to
>> >> >> manage the release branch and to ensure that all= relevant changes
>> >> >> are
>> >> >> in the trunk. In Axis2/Rampart/Sandesha2 we have= eradicated that
>> >> >> problem by using a consistent (yet simple) strat= egy to manage the
>> >> >> release/maintenance branches.
>> >> >>
>> >> >> Andreas
>> >> >>
>> >> >> [1] http://www.apache.org/dev/publi= shing-maven-artifacts.html
>> >> >> [2]
>> >> >>
>> >> >> https://docs.sonatype.= org/display/Repository/Central+Sync+Requirements
>> >> >>
>> >> >> On Mon, Dec 26, 2011 at 16:30, Kasun Indrasiri &= lt;kasun147@gmail.c= om>
>> >> >> wrote:
>> >> >> > Hi Devs,
>> >> >> >
>> >> >> > This is the call for votes to release Apach= e Synapse-2.1.0.
>> >> >> >
>> >> >> > Please review the signed artifacts:
>> >> >> > http://people.apache.org/~kas= un/synapse/2.1-RC1/artifacts/
>> >> >> >
>> >> >> > The m2 repository is available at:
>> >> >> > http://people.apache.org/~kasun= /synapse/2.1-RC1/m2_repo/
>> >> >> >
>> >> >> > Revamped site for this release is available= at:
>> >> >> > http://people.apache.org/~kasun/sy= napse/2.1-RC1/site/
>> >> >> >
>> >> >> > SVN Info:
>> >> >> > revision is 1222784 on
>> >> >> > https://svn.apache.org/repos/asf/s= ynapse/branches/2.1
>> >> >> >
>> >> >> > Here is my +1 to declaring the above dist a= s Synapse-2.1.0.
>> >> >> >
>> >> >> > Thanks,
>> >> >> > --
>> >> >> > Kasun Indrasiri
>> >> >> > Associate Technical Lead,
>> >> >> > WSO2 Inc. - "Lean . Enterprise . Middl= eware" -
>> >> >> > http://www.wso2.com/
>> >> >> > Blog : http://kasunpanorama.blogspot.com/
>> >> >> >
>> >> >>
>> >> >>
>> >> >> ------------------------------------------------= ---------------------
>> >> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apa= che.org
>> >> >> For additional commands, e-mail: dev-help@synapse.apache.o= rg
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Hiranya Jayathilaka
>> >> > Associate Technical Lead;
>> >> > WSO2 Inc.;=A0 http://wso2.org
>> >> > E-mail: hiranya@wso2.com;=A0 Mobile: +94 77 633 3491
>> >> > Blog: http://techfeast-hiranya.blogspot.com
>> >>
>> >> ---------------------------------------------------------= ------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> >> For additional commands, e-mail: dev-help@synapse.apache.org >> >>
>> >
>> >
>> >
>> > --
>> > Hiranya Jayathilaka
>> > Associate Technical Lead;
>> > WSO2 Inc.;=A0 h= ttp://wso2.org
>> > E-mail: hiranya@wso2.com;=A0 Mobile: +94 77 633 3491
>> > Blog: http://techfeast-hiranya.blogspot.com
>>
>> ------------------------------------------------------------------= ---
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead,
> WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/
> Blog : http://kasunpanorama.blogspot.com/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org




--
Kasun Indrasiri
= Associate Technical Lead,
WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/
Blog : htt= p://kasunpanorama.blogspot.com/




--
= Kasun Indrasiri
Associate Technical Lead,
WSO2 Inc. = - "Lean . Enterprise . Middleware" - http://www.wso2.com/
Blog : htt= p://kasunpanorama.blogspot.com/

--0015175cdf38d486cd04b585cb3c--