Hi, Still Following products have not followed the branching folder structure.
BAM2 BRS DSS GS LB Release Managers , Please follow the branching folder structure as soon as possible, since there can be problems when changing these at the last moment. We will add these products to bamboo once they moved to the correct structure. Thanks Shammi On Wed, Jul 25, 2012 at 2:36 PM, Amila Maha Arachchi <[email protected]>wrote: > Hi RMs, > > You need to branch your products with respective version numbers as we did > in 3.2.0 branch. Please note this and do the needful. Otherwise there will > be problems when you want are doing minor releases on this branch. > > Regards, > AmilaM. > > > On Wed, Jul 25, 2012 at 2:06 PM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi Pradeep, >> >> When branching the products, folder structure should be >> product-name/version/................. , right? But I dont see this in >> some/any products who are already building packs from the branch. For >> example ESB, G-Reg.. >> >> Regards, >> AmilaM. >> >> On Fri, Jul 20, 2012 at 3:57 PM, Pradeep Fernando <[email protected]>wrote: >> >>> >>> Hi, >>> >>> we are done with (i wont say done done. :) ) branching carbon for C4 >>> release. >>> >>> 1. Obit branch - >>> https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/ >>> All the obit jars been uploaded to dist.wso2.org/maven2. Ideally >>> you dont have to build orbit. Recently uploaded jars may take some time to >>> get cached. (one day). >>> >>> 2. Kernel branch - >>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 >>> >>> during the kernel branching we had the following changes in the >>> dependencies/orbit versions. (we had to increase versions of some project, >>> since some of them were released with carbon 3.2.0 release) >>> >>> h2-database 1.2.140-wso2v2 1.2.140-wso2v3 >>> jsrCache 1.1-wso2v1 1.1.0-wso2v2 >>> neethi 2.0.4-wso2v2 2.0.4-wso2v4 >>> securevault 1.0.0 1.0.0-wso2v2 >>> ciphertool 1.0.0 1.0.0-wso2v2 >>> wsdl4j 1.6.2-wso2v3 1.6.2-wso2v4 >>> xmlschema 1.4.7-wso2v1 1.4.7-wso2v2 >>> >>> >>> orbit >>> ------- >>> axis2-jaxbri 1.6.1.wso2v1 1.6.1.wso2v5 >>> axis2-jibx 1.6.1.wso2v1 1.6.1.wso2v5 >>> h2-database-engine 1.2.140.wso2v2 1.2.140.wso2v3 >>> jsr107cache 1.1.wso2v1 1.1.0.wso2v2 >>> neethi 2.0.4.wso2v3 2.0.4.wso2v4 >>> wsdl4j 1.6.2.wso2v3 1.6.2.wso2v4 >>> XmlSchema 1.4.7.wso2v1 1.4.7.wso2v2 >>> >>> >>> >>> 3. platform branch - >>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/ >>> >>> we had the following changes in the versions during the platform >>> branch. >>> >>> amber 0.22.1358727-wso2v1 same >>> andes 0.13-wso2v1 0.13.0-wso2v1 >>> cassandra 1.1.0-wso2v1 1.1.0-wso2v2 >>> closure-js-plugin 1.0-SNAPSHOT 1.0 (released) >>> datanucleus 3.0.1 3.0.1-wso2v1 >>> hadoop 0.20.203.1-wso2v1 0.20.203.1-wso2v1 >>> hector 0.7.0-23-wso2v1 0.7.0.23-wso2v1 >>> hive 0.8.1-wso2v2 0.8.1-wso2v3 >>> rampart 1.6.1-wso2v4 same >>> snappy 1.0.4.1-wso2v1 same >>> svn-client-adaptor 1.6.18.wso2v1 1.6.18.wso2v2 >>> synapse 2.1.0-wso2v6 same >>> thrift 0.5 >>> 0.5.0-wso2v2 >>> scm 1.7.wso2v1 1.7.0-wso2v1 >>> >>> >>> externals: >>> >>> commons-vfs 2.0-wso2v3 2.0-wso2v4 >>> shindig removed >>> sandesha 1.6.1-wso2v1 1.6.1-wso2v2 >>> qpid 0.12-wso2v1 same >>> httpcore-nio 4.1.3-wso2v2 same >>> siddhi 1.0.0-SNAPSHOT 1.0.0-wso2v1 >>> balana 1.0.0-SNAPSHOT 1.0.0-wso2v1 >>> xfer removed >>> xkms removed >>> ciphertool removed >>> pwprovider removed >>> oauth removed >>> charon 1.0.0-SNAPSHOT 1.0.0-wso2v1 >>> throttle2 removed >>> caching removed >>> eventing removed >>> wsdlvalidator 1.2.0-SNAPSHOT 1.2.0-wso2v1 >>> throttle 3.3.0 3.3.0-wso2v1 >>> ode 1.3.5-SNAPSHOT 1.3.5-wso2v5 >>> e4ximpl 2.0.1.SNAPSHOT 2.0.1.wso2v1 >>> webharvest 2.0.wso2v1 2.0-wso2v2 >>> >>> >>> >>> >>> >>> >>> Below are sevn revision numbers of the branched sources in the platform: >>> >>> platform version - 133225 >>> siddhi - 133379 >>> balana - 133391 >>> charon - 133397 >>> wsdl-validator - 133411 >>> throttle - 133416 >>> ode - 133426 >>> e4ximpl - 133436 >>> >>> >>> >>> the devs have to merge the changes of trunk versions of the above >>> projects, to platform branch. >>> >>> >>> >>> TODO: >>> >>> * compilation failure in siddhi/CEP : (removed from the build for the >>> moment) >>> * product branching - to be handled by the product teams >>> * Fixing test failures - we may need some help on this task. >>> * setting up build jobs in bamboo >>> >>> >>> Release managers please start building the branch >>> >>> >>> thanks, >>> --Pradeep >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Technical Lead >> Member, Management Committee - Cloud & Platform TG >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> > > > -- > *Amila Maharachchi* > Technical Lead > Member, Management Committee - Cloud & Platform TG > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
