Hi,

On Thu, Mar 22, 2012 at 8:05 PM, Afkham Azeez <[email protected]> wrote:

> Have the respective product teams started looking into this?
>

As others have raised concerns, maybe first a single product/service can be
used to test out the merging procedure. Then we would be able to find all
the fundamental and core issues that will arise with this undertaking. When
we get a single solution working perfectly, and sort out the basic issues,
then other individual products/services can look into their specific
problems. So I guess, in this way, all people won't be wasting time working
on similar kind of problems. And as Amila said also, if we straight away
jump into this, the immediate kernel stabilization and all can get
complicated and can delay everything. So how about we track the progress of
that single product/service and decide on when we are going to do it for
all others.

Cheers,
Anjana.


>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to