Hi Samisa, As I understand, according to the resource allocations for release of G-Reg we need two more weeks of time. So I like to suggest 12th Oct. as the code freeze date.
thanks Eranda On Mon, Oct 1, 2012 at 10:44 AM, Samisa Abeysinghe <[email protected]> wrote: > PING!!! > > Release managers - please ACK, the longer the code freeze is delayed, the > longer it will take to release. We need to define a hard deadline, then do > or die on that line :-| > > > On Mon, Sep 24, 2012 at 5:49 PM, Samisa Abeysinghe <[email protected]>wrote: > >> Reminder - we are three days away - please focus on your L1s. >> >> >> On Sat, Sep 22, 2012 at 8:22 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> Please note $subject. >>> >>> Since this is a platform wide release, there needs to be a freeze of all >>> components and features. Anything issues known or found after that point >>> will be only committed in based on a RTC model, and we will only have >>> couple of release managers with commit rights. >>> >>> This is an advance notice, and please plan accordingly. >>> >>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
