You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Musayev, Ilya" <im...@webmd.net> on 2013/08/01 00:46:54 UTC
RE: [DISCUSS] Should we be releasing -beta releases?
Daan,
Why can't the patch be committed to master?
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.
Example, if I have a feature in CloudSand 4.1 that was backported from ACS 4.2, when end user upgrades to stable release of ACS4.2 - it should all function as expected.
So backward compatibility is one of the main focuses for CloudSand release.
What features are we talking about?
Regards
ilya
> -----Original Message-----
> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
> Sent: Wednesday, July 31, 2013 3:20 PM
> To: dev
> Subject: Re: [DISCUSS] Should we be releasing -beta releases?
>
> H Ilya,
>
> I am working on a paralel track. At Schuberg Philis we have a version that
> contains some code from 4.2 and a patch that I cannot get committed to
> master. I don't want to release this in the open, but am interested in your
> considerations on the subject.
>
> regards,
> Daan
>
> On Wed, Jul 31, 2013 at 5:55 PM, Musayev, Ilya <im...@webmd.net>
> wrote:
> > Oops, wrong url for github, correct url is:
> >
> > http://www.guthub.com/serverchief/cloudsand
> >
> >> -----Original Message-----
> >> From: Musayev, Ilya [mailto:imusayev@webmd.net]
> >> Sent: Wednesday, July 31, 2013 11:52 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: RE: [DISCUSS] Should we be releasing -beta releases?
> >>
> >> I run my own hybrid version of 4.1 and with some features of 4.2 in
> >> production, since - I needed to backport some features of 4.2 into
> >> 4.1
> >>
> >> Since this version was not officially released under ACS, I branded
> >> it as CloudSand (powered by Apache CloudStack).
> >>
> >> You can see the code here:
> >> http://www.guthub.com/serverchief.com/cloudsand | www.
> >> Cloudsand.com
> >>
> >> At some point, I would like to release a "RC/beta" of CloudSand 4.2
> >> on my own, if anyone wants to join the effort, please ping me :)
> >>
> >> Thanks
> >> Ilya
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Nux! [mailto:nux@li.nux.ro]
> >> > Sent: Thursday, June 27, 2013 8:06 AM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: [DISCUSS] Should we be releasing -beta releases?
> >> >
> >> > On 14.05.2013 15:41, Chip Childers wrote:
> >> > > As a way to get more user feedback on our major feature releases,
> >> > > what does everyone think about releasing one or two -beta
> >> > > releases for each major feature release?
> >> > >
> >> > > This might fall in line with some of the stated concerns about
> >> > > our release schedule (see [1]). I've stated a desire to be
> >> > > quicker about our releases (my vote was 4 months). I've also
> >> > > been saying quite publicly that we should never release if we
> >> > > know about upgrade issues (that's the cost of having actual users
> >> > > of our project, which I'm more than willing for us to pay).
> >> > >
> >> > > Perhaps -betaX releases would be helpful to get attention from
> >> > > the users to test the release (including upgrade paths). The
> >> > > stated assumption could be: -beta releases are not releases that
> >> > > can be upgraded *from*, but are intended to help support testing
> >> > > by end users that want to check the upcoming release against
> >> > > their expected feature set and upgrade path.
> >> > >
> >> > > I would see the first -beta-1 being released about 1 month after
> >> > > feature freeze. For example, for 4.2.0, it would be on 2013-06-30.
> >> > > I would only do a -beta-2 (or later) beta release if required due
> >> > > to testing results. I would also suggest that the -beta-*
> >> > > releases would
> >> > > *not* have any particular quality criteria (well... perhaps
> >> > > minimal, like blocking on issues that fundamentally make the
> >> > > software unstable).
> >> > >
> >> > > I'm not sure about my own proposal here, but I wanted to throw it
> >> > > out and see if any of you have feedback / thoughts.
> >> > >
> >> > > -chip
> >> > >
> >> > > [1] http://markmail.org/message/3ctdwor5hfbpa3vx
> >> >
> >> > +1 for beta releases, I was actually thinking of building some RPMS
> >> > from source, want to get a flavour of 4.2 features, but not sure if
> >> > I can be bothered with that. If I had some nightlies or betas
> >> > available on cloudstack.apt-get.eu I'd definitely give it a go.
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
> >
Re: [DISCUSS] Should we be releasing -beta releases?
Posted by Daan Hoogland <da...@gmail.com>.
:} it is due to master moving faster then me being all over the code.
I have ported it once again to master and am busy testing again. but
we need it and have just moved to 4.1.1. I agree with you Alex. So we
will not release our fork just the patch via the earliest main
release. (I could publish a 4.1.1 patch however)
On Thu, Aug 1, 2013 at 7:00 PM, Alex Huang <Al...@citrix.com> wrote:
> +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:imusayev@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.hoogland@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 <im...@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
>>
>
RE: [DISCUSS] Should we be releasing -beta releases?
Posted by Alex Huang <Al...@citrix.com>.
+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:imusayev@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.hoogland@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 <im...@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
>
RE: [DISCUSS] Should we be releasing -beta releases?
Posted by "Musayev, Ilya" <im...@webmd.net>.
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.hoogland@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 <im...@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
Re: [DISCUSS] Should we be releasing -beta releases?
Posted by Daan Hoogland <da...@gmail.com>.
On Thu, Aug 1, 2013 at 12:46 AM, Musayev, Ilya <im...@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