On Wed, Jan 16, 2013 at 5:02 PM, Dileepa Jayakody <dile...@wso2.com> wrote:
> > > On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe <has...@wso2.com>wrote: > >> Hi all, >> >> FYI... >> - $subject was done for the products to be released with platform 4.0.7 >> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform >> 4.0.7 >> - I hope there wont be issues in having two non-released platform patch >> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know >> if there is any.. >> > > I think this can result in the 4.0.6 tag having 4.0.7 components, then it > will be not compliant to our previous releases isn't it? > How about we commit the changes to 4.0.6 until it gets released and soon > after copy the changes and create 4.0.7? > Yes, we have been doing that, but since products which are not released with 4.0.6 were removed from 4.0.6 patch release, went for the option of creating 4.0.7. We can add them back to 4.0.6 till it is released. However, kernel 4.0.6 will not be released with platform 4.0.6 since 4.0.6 products are using kernel 4.0.5. Therefore, even if we move 4.0.7 products and components to platform 4.0.6, we need to build kernel 4.0.6 with platform 4.0.6 if we go for the above option. Won't that add an additional overhead for 4.0.6 product release? Thanks, Hasini. > - When building the packs for QA from builder machine, we can build >> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7 >> - so that packs from both 4.0.6 and 4.0.7 will be available. >> >> Thanks, >> Hasini. >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
