[Gluster-infra] separating code analysis from download
mscherer at redhat.com
Thu Nov 5 12:19:28 UTC 2015
Le jeudi 05 novembre 2015 à 07:13 -0500, Kaleb KEITHLEY a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On 11/05/2015 07:08 AM, Michael Scherer wrote:
> > Le jeudi 05 novembre 2015 à 12:44 +0100, Niels de Vos a écrit :
> >> [fixed CC to gluster-devel at gluster.org]
> >> On Thu, Nov 05, 2015 at 06:13:52AM -0500, Kaleb KEITHLEY wrote:
> >>> <top post> How about devel.gluster.org? Or upload.gluster.org?
> >>> Either one would be reasonable for nightly coverity/clang/etc
> >>> reports as well as community uploads?
> >>> </top post>
> >> devel.gluster.org sounds good to me. We will use it for
> >> uploading, but also downloading, unless the uploads get
> >> replicated to download.gluster.org and we use that as the only
> >> public accessible download system.
> > I am ok with that, but there is a risk of confusion with
> > dev.gluster.org :)
> That's just another name for review.gluster.org, right? I'm not sure
> why we need two names.
I agree we don't, but I do not want to break too much people habits
and/or script somewhere (like, do gerrit use review in the config, or
dev.gluster.org ? ).
I would also start to have a naming scheme for servers, and a name for
the service ( see for example download.gluster.org, download.gluster.org
is the service and download01.rax.gluster.org is the server), as it will
ease future migration.
Sysadmin, Community Infrastructure and Platform, OSAS
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Gluster-infra