+1 If it's due to company specific issues (licensing or company secret). Maybe we can propose a plugin interface for it and see if you can keep just that code private.
Just look at how much master have changed from 4.2. If we can we should try not to fork on the core code in cloudstack. Maintaining will be tough. --Alex > -----Original Message----- > From: Musayev, Ilya [mailto:imusa...@webmd.net] > Sent: Thursday, August 1, 2013 9:51 AM > To: dev@cloudstack.apache.org > Subject: RE: [DISCUSS] Should we be releasing -beta releases? > > Daan and Hugo, > > This is just my opinion, you should consider merging this feature into master > when time allows - this way you don't have to maintain a private branch of > ACS in the future. Just my two cents :) > > Regards > ilya > > > -----Original Message----- > > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > Sent: Thursday, August 01, 2013 4:13 AM > > To: dev > > Subject: Re: [DISCUSS] Should we be releasing -beta releases? > > > > On Thu, Aug 1, 2013 at 12:46 AM, Musayev, Ilya <imusa...@webmd.net> > > wrote: > > > The reason why CloudSand was created, was to bring in urgently > > > needed > > features into stable version, such that on the next major upgrade to > > ACS, all features work as expected and nothing should break. > > This is the same that we have done. Except that we have put work into > > CLOUDSTACK-1532 that was urgently needed internally at Schuberg > > Philis. It is implemented in 4.1.1-SBP a private release. I have > > ported it to master several times but testing and paralel development > > on other network features have prevented it from being merged in master. > > > > > What features are we talking about? > > > > I gues our focus is hastening our own development and not backporting. > > > > regards, > > Daan >
