+1. Please move the graduated code under this structure. It should have
versions, just like in the case of our branches.

Azeez

On Mon, Jan 10, 2011 at 11:05 AM, Pradeep Fernando <[email protected]> wrote:

> Hi devs,
>
> During an off-line discussion with Afkham Azeez, we (me , Sameera)
> noted that, it is hard to locate the source of the artifacts that have
> being graduated during an older release.
>
> For an example during the last AS release Charith had to dig in to a
> old carbon release to get the source of the xfer component. (to fix a
> bug). We thought of maintaining a separate source structure for the
> graduated component under the name "graduated" . this is similar to
> the attic directory structure, but the only difference is that a
> developer may bring back the graduated component to fix a bug. (means
> we have to maintain versions).
>
>
> if you have any other views regarding this effort please reply to this
> mail thread.
>
> thanks,
> --Pradeep.
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; 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*
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to