On 05.08.2013 16:48, Daan Hoogland wrote:
the 4.1 build for rhel63 says:
Apache Cloudstack RHEL 6.3 packages
This project is currently disabled
this one didn't happen to be the one you where looking for? Anyway
look at http://jenkins.cloudstack.org and browse around. I thought you
would find the
the 4.1 build for rhel63 says:
Apache Cloudstack RHEL 6.3 packages
This project is currently disabled
this one didn't happen to be the one you where looking for? Anyway
look at http://jenkins.cloudstack.org and browse around. I thought you
would find them there.
On Mon, Aug 5, 2013 at 5:40 PM, D
think was the keyword there, ... but I am looking for ya. moment
On Mon, Aug 5, 2013 at 5:21 PM, Nux! wrote:
> On 05.08.2013 16:09, Daan Hoogland wrote:
>>
>> For this the jenkins builds might be suitable. I think if those are
>> running on all active release branches.
>
>
> Some URLs could be re
On 05.08.2013 16:09, Daan Hoogland wrote:
For this the jenkins builds might be suitable. I think if those are
running on all active release branches.
Some URLs could be real handy now. :)
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
For this the jenkins builds might be suitable. I think if those are
running on all active release branches.
On Mon, Aug 5, 2013 at 4:42 PM, Nux! wrote:
> On 31.07.2013 16:30, Chip Childers wrote:
>>
>> On Wed, Jul 31, 2013 at 12:04:50AM +0100, Nux! wrote:
>>>
>>> On 14.05.2013 15:41, Chip Childer
On 31.07.2013 16:30, Chip Childers wrote:
On Wed, Jul 31, 2013 at 12:04:50AM +0100, Nux! wrote:
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
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
>>
stack. 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,
&g
: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
> wrote:
> > The reason why CloudSand was created, was to bring in urgently needed
&
On Thu, Aug 1, 2013 at 12:46 AM, Musayev, Ilya 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.
-
> From: Daan Hoogland [mailto:daan.hoogl...@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 so
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 thi
t; Thanks
> Ilya
>
>
>
> > -Original Message-
> > From: Nux! [mailto:n...@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
: 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 thin
On Wed, Jul 31, 2013 at 12:04:50AM +0100, Nux! wrote:
> 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?
>
> Hi,
>
> What has been
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?
Hi,
What has been decided? Will we see any 4.2 betas?
Lucian
--
Sent from the Delta q
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
On Tue, May 28, 2013 at 10:43:46PM +0100, Noah Slater wrote:
> Users are *by definition* people who do not vote. The minute a user votes
> they become a developer. ;)
>
> I agree with you that interaction with the user@ list should use inclusive
> language, and should call for participation in the
Yep! Welcome!
On 28 May 2013 22:56, Daan Hoogland wrote:
> wow,
> I obtained voting right by subscribing. Beats Verhoeven's view on the
> matter, the starship troopers way ;)
>
>
> On Tue, May 28, 2013 at 11:43 PM, Noah Slater wrote:
>
> > Users are *by definition* people who do not vote. The
wow,
I obtained voting right by subscribing. Beats Verhoeven's view on the
matter, the starship troopers way ;)
On Tue, May 28, 2013 at 11:43 PM, Noah Slater wrote:
> Users are *by definition* people who do not vote. The minute a user votes
> they become a developer. ;)
>
> I agree with you tha
Users are *by definition* people who do not vote. The minute a user votes
they become a developer. ;)
I agree with you that interaction with the user@ list should use inclusive
language, and should call for participation in the decision-making process
that happens on dev@.
Daan, monitor this list
I am not a commiter and did not know there where things at all that I could
vote on. Nice to hear. What things? How to recognise them?
regards,
Daan
On Tue, May 28, 2013 at 11:14 PM, Sebastien Goasguen wrote:
>
> On May 28, 2013, at 2:36 PM, Noah Slater wrote:
>
> > Sebastien,
> >
> > Nope, we
On May 28, 2013, at 2:36 PM, Noah Slater wrote:
> Sebastien,
>
> Nope, we don't do votes on the users@ list. That list is just for user
> support.
>
> Decision making happens on dev@*, and if users want to take part in that,
> they can subscribe.
This needs to be made clearer then, otherwise
Sebastien,
Nope, we don't do votes on the users@ list. That list is just for user
support.
Decision making happens on dev@*, and if users want to take part in that,
they can subscribe.
* Or marketing@, private@, and security@
On 27 May 2013 08:53, Sebastien Goasguen wrote:
>
> On May 24, 201
On May 24, 2013, at 12:26 PM, Chip Childers wrote:
> On Tue, May 14, 2013 at 10:41:30AM -0400, 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?
>>
>>
On Tue, May 14, 2013 at 10:41:30AM -0400, 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 abo
On Tue, May 14, 2013, at 10:59 AM, David Nalley wrote:
> Are you going to support upgrades from your Betas to release (and
> betaN to betaN+1)?
> If the answer is no, then there is no interest on my part. It's not
> better than us producing nightly builds, or highlighting jenkins
> builds.
The pro
On Sat, May 18, 2013 at 06:51:30PM -0700, Ahmad Emneina wrote:
> I agree, there need's to be a caveat the nightly builds are convenience
> builds, that shouldnt be used for any type of production environment. Only
> for testing.
>
>
> On Sat, May 18, 2013 at 4:43 PM, Marcus Sorensen wrote:
>
> >
e beta especially because folks would want to test early and
> > >> crossing the last mile can take a bit of time.
> > >> But hopefully its not too much of an overhead.
> > >>
> > >> Thanks,
> > >> -Nitin
> > >>
> > >> On
e.
> >> But hopefully its not too much of an overhead.
> >>
> >> Thanks,
> >> -Nitin
> >>
> >> On 16/05/13 7:27 AM, "Musayev, Ilya" wrote:
> >>
> >> >+1, perhaps I'm late to this thread, but this makes
f time.
>> But hopefully its not too much of an overhead.
>>
>> Thanks,
>> -Nitin
>>
>> On 16/05/13 7:27 AM, "Musayev, Ilya" wrote:
>>
>> >+1, perhaps I'm late to this thread, but this makes lot of sense.
>> >
&g
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?
Good idea! It would be great to get a feel of how things will look and
work ahead of re
much of an overhead.
>
> Thanks,
> -Nitin
>
> On 16/05/13 7:27 AM, "Musayev, Ilya" wrote:
>
> >+1, perhaps I'm late to this thread, but this makes lot of sense.
> >
> >
> > Original message ----
> >From: Pranav Saxena
makes lot of sense.
>
>
> Original message
>From: Pranav Saxena
>Date:
>To: dev@cloudstack.apache.org,aemne...@gmail.com
>Subject: RE: [DISCUSS] Should we be releasing -beta releases?
>
>
>+1 to what Ahmad says here . Perfect reasoning .
>
>
+1, perhaps I'm late to this thread, but this makes lot of sense.
Original message
From: Pranav Saxena
Date:
To: dev@cloudstack.apache.org,aemne...@gmail.com
Subject: RE: [DISCUSS] Should we be releasing -beta releases?
+1 to what Ahmad says here . Perfect reas
On May 14, 2013, at 12:34 PM, Chip Childers wrote:
> On Tue, May 14, 2013 at 11:59:14AM -0400, David Nalley wrote:
>> Are you going to support upgrades from your Betas to release (and
>> betaN to betaN+1)?
>> If the answer is no, then there is no interest on my part. It's not
>> better than us p
lp to further refine any new feature further when actually tested in a
production environment .
-Original Message-
From: Ahmad Emneina [mailto:aemne...@gmail.com]
Sent: Wednesday, May 15, 2013 12:07 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Should we be releasing -beta releases?
+1
I feel this allows for users who are chomping at the bit to get a hold of
feature X. Tinker with feature X, expose bugs or use case issues well
before an official release. Saves on the disappointment as well. ;)
On Tue, May 14, 2013 at 9:34 AM, Chip Childers wrote:
> On Tue, May 14, 2013 at 1
On Tue, May 14, 2013 at 11:59:14AM -0400, David Nalley wrote:
> Are you going to support upgrades from your Betas to release (and
> betaN to betaN+1)?
> If the answer is no, then there is no interest on my part. It's not
> better than us producing nightly builds, or highlighting jenkins
> builds.
Are you going to support upgrades from your Betas to release (and
betaN to betaN+1)?
If the answer is no, then there is no interest on my part. It's not
better than us producing nightly builds, or highlighting jenkins
builds.
On Tue, May 14, 2013 at 11:03 AM, Chip Childers
wrote:
> On Tue, May 14
upgrades are a valid point. No one tests those as a user does.
On Tue, May 14, 2013 at 4:03 PM, Chip Childers wrote:
> On Tue, May 14, 2013 at 03:56:36PM +0100, Daan Hoogland wrote:
> > As a relative outsider;
> >
> > any branch that is not released yet is a beta release. Why make it more
> > ex
On Tue, May 14, 2013 at 03:56:36PM +0100, Daan Hoogland wrote:
> As a relative outsider;
>
> any branch that is not released yet is a beta release. Why make it more
> explicit. Wouldn't this add support burdon? Make a branch 'in beta' and
> appoint a guard to make sure no new feartures but only fi
zonker.net]
Sent: 14 May 2013 15:49
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Should we be releasing -beta releases?
On Tue, May 14, 2013, at 09:41 AM, Chip Childers wrote:
> As a way to get more user feedback on our major feature releases, what
> does everyone think about relea
: Tuesday, May 14, 2013 4:49 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Should we be releasing -beta releases?
>
> On Tue, May 14, 2013, at 09:41 AM, Chip Childers wrote:
> > As a way to get more user feedback on our major feature releases, what
> > does eve
As a relative outsider;
any branch that is not released yet is a beta release. Why make it more
explicit. Wouldn't this add support burdon? Make a branch 'in beta' and
appoint a guard to make sure no new feartures but only fixes go in (kind of
how you are working right now)
Daan
On Tue, May 14,
On Tue, May 14, 2013, at 09:41 AM, 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?
Yes to beta releases. I know that users could test at any time, but we
46 matches
Mail list logo
