[Architecture] Carbon platform branching issue for BPS 1.1 release

Ruwan Linton ruwan at wso2.com
Tue Sep 22 01:17:28 EDT 2009


Isuru Suriarachchi wrote:
> One more thing.. If there are no Carbon core changes needed for these
> releases, I think we can go with Carbon 2.0.1 and increase the version
> to 2.0.2 only in the needed components (For example data services
> component). Otherwise we need to deploy new artifacts for Carbon and
> Carbon components jars in the maven repo without any changes after 2.0.1.
Isuru, that model is not scalable, I recommend to change all the
component versions, otherwise we need to track all the changing
components which is hard and deploy each and every component, we cannot
do mvn deploy:deploy on the carbon components root if we only change a
set of components. This is because redeploying an already deployed jar
file is conceptually wrong and might cause issues, if we accidentally
changed those.

OTOH, we may not need to change the carbon version if we do not do any
changes to the core.

Thanks,
Ruwan
>
> Thanks,
> ~Isuru
>
> On Tue, Sep 22, 2009 at 10:29 AM, Isuru Suriarachchi <isuru at wso2.com
> <mailto:isuru at wso2.com>> wrote:
>
>     I think Data Services team is also planning to do their 2.1
>     release very soon. Sumedha is also going to create a branch for
>     that. I think we can do these two releases through 2.0.2 branch.
>
>     Thanks,
>     ~Isuru
>
>
>     On Tue, Sep 22, 2009 at 10:24 AM, Ruwan Linton <ruwan at wso2.com
>     <mailto:ruwan at wso2.com>> wrote:
>
>         +1
>
>         Please make sure to change the versions of the components as
>         soon as you
>         do the branch off.
>
>         Thanks,
>         Ruwan
>
>         Milinda Pathirage wrote:
>         > We did the work for BPS 1.1 release in the Carbon platform's
>         2.0.1
>         > branch. Because we couldn't find resources for BPS 1.1
>         release we had
>         > to postpone the release. Now 2.0.1 branch is freezed for
>         2.0.1 release
>         > and after release is done we can't work in 2.0.1 branch. So
>         that I am
>         > planning to create Carbon platform 2.0.2 and BPS 1.1 branch
>         for BPS
>         > 1.1 release. If there are any issues with 2.0.1 branch(in
>         case we
>         > found issues in recent release packs) we can ask to commit
>         those fixes
>         > to 2.0.2 branch as well.
>         >
>         > WDYT?
>         >
>         > Thanks
>         > Milinda
>         >
>         ------------------------------------------------------------------------
>         >
>         > _______________________________________________
>         > Architecture mailing list
>         > Architecture at wso2.org <mailto:Architecture at wso2.org>
>         > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>         >
>
>
>         --
>         Ruwan Linton
>         Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>         WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
>         email: ruwan at wso2.com <mailto:ruwan at wso2.com>; cell: +94 77
>         341 3097
>         blog: http://blog.ruwan.org
>
>
>
>         _______________________________________________
>         Architecture mailing list
>         Architecture at wso2.org <mailto:Architecture at wso2.org>
>         https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan at wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org






More information about the Architecture mailing list