cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@tumbolia.org>
Subject Re: [WEBSITE] Download page for review on staging
Date Fri, 12 Oct 2012 10:18:26 GMT
On Thu, Oct 11, 2012 at 5:57 PM, Chip Childers <chip.childers@sungard.com>wrote:

> Hi all,
>
> I've committed some changes to the incubator.a.o/cloudstack downloads
> page, which can be seen here on the staging site:
>
> http://cloudstack.staging.apache.org/cloudstack/downloads.html
>
> Any comments / concerns with the new structure of the page?
>

Looks great, Chip.

You should probably link to the http and https versions of the Git
repository.

You can check out the code using the git command:



git clone http://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git



Committers should use the secure repository:



git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git


Also, I would not link to the Citrix CloudStack Github repos. This page has
various issues with it, as I have addressed in a previous thread that is
still not resolved. Linking to it from this section only compounds those
issues IMO.

Two thoughts from me:
>
> 1 - Once we do a second ASF release, we'll add a link to the Apache
> release archives in the "Older CloudStack Releases" section.
>

Remember that we'll probably end up with various active release lines, so
the page has to support those. You could have a 5.0.x section, and a 4.0.x
section, for example. If they are active (i.e. we're still releasing minor
updates, bugfixes, then they both need to be prominantly displayed on this
page.) When we make them inactive, we simply remove them from this page,
and from the dist dir. At that point, we can add a link that takes you to
the archived dist dir, but it should be a low key text link at the bottom.


> 2 - Should we include the URLs (and instructions for how to configure)
> for Wido's DEB repo?  And also the yet to be made RPM repo?  Wido,
> obviously you get a veto on this.
>

Yep! But clearly marked out, for obvious reasons.

-- 
NS

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