Hello folks,
This is a call for a vote on the Apache Atlas 0.5 incubating release.
A vote was held on developer mailing list and it passed with 9 +1's.
Vote thread: http://s.apache.org/RyM
Results thread: http://s.apache.org/f8S
The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5,
For HTTPd I was referring to the assertion from Justin earlier in this thread "
FWIW, httpd always had nightly tarballs available for consumption and testing."
(though reading that now I wonder if he meant source tarballs - which is an
easy way of resolving this whole issue)
Ross
-Original
Le 24/06/15 22:28, David Nalley a écrit :
> On Wed, Jun 24, 2015 at 12:01 PM, Ross Gardler (MS OPEN TECH)
> wrote:
>> +1 (to this and Jochen's response)
>>
>> Roman was explicit in his question about "clearly identifiable non-release
>> artifacts available to the general public". We can debate wo
Le 24/06/15 22:14, David Nalley a écrit :
>
>>> Going back to the example of libraries published as Maven artifacts
>>> for those projects already publishing SNAPSHOTs these only get
>>> published to the Apache Nexus server (repository.apache.org) and are
>>> not synced to Maven central.
>> So ? SN
On Wed, Jun 24, 2015 at 12:01 PM, Ross Gardler (MS OPEN TECH)
wrote:
> +1 (to this and Jochen's response)
>
> Roman was explicit in his question about "clearly identifiable non-release
> artifacts available to the general public". We can debate words on a page
> forever, or we can work with the
On Wed, Jun 24, 2015 at 3:22 PM, Emmanuel Lécharny wrote:
> Le 24/06/15 09:19, Rob Vesse a écrit :
>> Personally I think the policy should be clarified such that nightly
>> builds MUST only live on ASF infrastructure
>
> Non sense. Nightly built can stay wherever is suitable. It's not The ASF
> bu
Le 24/06/15 09:19, Rob Vesse a écrit :
> Personally I think the policy should be clarified such that nightly
> builds MUST only live on ASF infrastructure
Non sense. Nightly built can stay wherever is suitable. It's not The ASF
business anyway, The ASF does not endorse nighly build or non-release
Le 24/06/15 19:21, Marvin Humphrey a écrit :
> On Wed, Jun 24, 2015 at 9:01 AM, Ross Gardler (MS OPEN TECH)
> wrote:
>
>> We can debate words on a page forever, or we can work with the intent and
>> get on with producing software.
> Amen. So when's that Geode release coming?
Ask the Geode fellos
On Wed, Jun 24, 2015 at 9:01 AM, Ross Gardler (MS OPEN TECH)
wrote:
> We can debate words on a page forever, or we can work with the intent and
> get on with producing software.
Amen. So when's that Geode release coming?
> My summary of the intent: Don't advertise automated "non-release" artif
People wanting to use snapshot releases can be expected to jump through hoops
to install those snapshots. NuGet, like all package management solutions, is a
convenience not a requirement. People can still manually download and install
libraries manually. Putting snapshots in public repositories,
Good point.
Furthermore, for users of those project, it might be more painful to get
binaries in an usual Apache place compared to a community / blessed
approach.
Le mercredi 24 juin 2015, Markus Weimer a écrit :
> > Personally I think the policy should be clarified such that nightly
> builds
>
> Personally I think the policy should be clarified such that nightly builds
> MUST only live on ASF infrastructure (whether that be the Nexus SNAPSHOTs
> repo, committer web space etc). As soon as you start putting them on
> external services like DockerHub then they are potentially widely visibl
+1 (to this and Jochen's response)
Roman was explicit in his question about "clearly identifiable non-release
artifacts available to the general public". We can debate words on a page
forever, or we can work with the intent and get on with producing software.
There is plenty of precedent here (
Am 24.06.2015 14:04, schrieb Marvin Humphrey:
[...]
What differentiates the "general public" from "developers" is whether they are
aware of the conditions placed on the artifacts and thus exercising informed
consent.
What I don't understand is, why I am "exercising informed consent" if I
read
Le 24/06/15 14:04, Marvin Humphrey a écrit :
> On Tue, Jun 23, 2015 at 3:20 PM, Ross Gardler (MS OPEN TECH)
> wrote:
>> There is nothing preventing "clearly identifiable non-release artifacts
>> available to the general public".
> The Releases Policy page forbids it explicitly:
>
> During the
On Tue, Jun 23, 2015 at 3:20 PM, Ross Gardler (MS OPEN TECH)
wrote:
> There is nothing preventing "clearly identifiable non-release artifacts
> available to the general public".
The Releases Policy page forbids it explicitly:
During the process of developing software and preparing a release,
>
> +1
>
> Personally I think the policy should be clarified such that nightly builds
> MUST only live on ASF infrastructure (whether that be the Nexus SNAPSHOTs
> repo, committer web space etc). As soon as you start putting them on
> external services like DockerHub then they are potentially wide
On 24/06/2015 04:12, "Justin Erenkrantz" wrote:
>On Tue, Jun 23, 2015 at 10:48 PM, Roman Shaposhnik
>wrote:
>> On Tue, Jun 23, 2015 at 3:20 PM, Ross Gardler (MS OPEN TECH)
>> wrote:
>>> There is nothing preventing "clearly identifiable non-release artifacts
>>> available to the general public
18 matches
Mail list logo
