cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@tumbolia.org>
Subject Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, first round
Date Tue, 16 Oct 2012 09:14:39 GMT
On Fri, Oct 12, 2012 at 8:42 PM, Chip Childers <chip.childers@sungard.com>wrote:

>
> > Might be good to indicate the provenance of this image on the wiki, and
> > perhaps move it somewhere not on cloud.com, or am I misunderstanding
> what
> > that communicates?
>
> I think moving it's build process to an automated approach, and
> hosting it somewhere on ASF infra is a great step for us to take.  I
> tried to get things moving with the infra team on this, but then I got
> distracted doing other things.  Perhaps we pick this back up once we
> hear back from the @basho team on their DevCloud build process
> changes?


Okie dokie.


> > I would prefer it if the instructions used Homebrew where possible.
> > MacPorts is kinda lame and I would prefer not to have to install it.
> Having
> > said that, beggars can't be choosers I suppose.
> >
> > As for including them or not, the goal here is to hone this test
> procedure
> > so that people can be as thorough as I am without having to think about
> it.
> > The more we can get to just a list of commands to copy and paste into a
> > terminal, the better. Makes things super easy to follow.
>
> Totally fair to prefer Homebrew.  So here's what I'll say...  I edited
> the instructions in an attempt to help a Mac user.  If you wanted to
> run through the process and modify it to make it (1) more accurate and
> (2) work from Homebrew, that would be awesome.  My machine already has
> everything on it, so I was struggling to remember exactly how I got
> things the way they are!  I know I should have a better answer than
> that, but it's what I've got.
>

Yep, on it.


> > Okay, thanks. One file will make voting much less... Complicated.
>
> We're going to do 1 file in tar.bz2 format.


Sweet.


> > We need need to be sure our release artefacts are voted on. This isn't
> just
> > about checking boxes so the ASF will leave us alone, it is about ensuring
> > that we are producing the best possible releases for the community.
> (Hint:
> > We are the ASF, so this is a meaningless concept anyway. Though, I must
> > admit, when I was going through incubation I used to think of it in those
> > terms. "Bah, bloody ASF getting in my way again. Then one day, someone
> > kindly pointed out "ASF" included me.)
>
> I didn't imply that ASF if "getting in the way".  See my reply to Will
> on how I look at the delegation of authority for podlings, and it's
> implications on what it means to vote.
>

Understood. I think I was just feeling verbose. :)


> I understand the spirit of what you are saying, but I wasn't asking
> for permission.  I was asking for input, and John and David gave good
> feedback on the topic.
>
> That...  we DO want to develop as a community habit.


Yep, agreed. See above comment. ;)


> > Okay, I just wanted to make sure there's no "source format" we could ship
> > instead.
>
> Nope, those are keys.


Okay.


-- 
NS

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message