-- in reply to --
From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
Sent: Tuesday, December 23, 2014 01:28
To: Incubator General
Subject: Re: Votes for git repos - commit id vs tag
On Tue, Dec 23, 2014 at 3:54 AM, Marvin Humphrey wrote:
> ...Although many consider it best pract
On 23 December 2014 at 09:27, Bertrand Delacretaz
wrote:
> On Tue, Dec 23, 2014 at 3:54 AM, Marvin Humphrey
> wrote:
>> ...Although many consider it best practice for release tarballs to be tied
>> back
>> to a specific version control identifier (including me), Apache release
>> policy
>> doe
On 12/23/2014 01:27 AM, Bertrand Delacretaz wrote:
On Tue, Dec 23, 2014 at 3:54 AM, Marvin Humphrey wrote:
...Although many consider it best practice for release tarballs to be tied back
to a specific version control identifier (including me), Apache release policy
does not require it
As
On Tue, Dec 23, 2014 at 3:54 AM, Marvin Humphrey wrote:
> ...Although many consider it best practice for release tarballs to be tied
> back
> to a specific version control identifier (including me), Apache release policy
> does not require it
As we tried to say above, the timeline gets into
On Mon, Dec 22, 2014 at 6:14 PM, Ryan Blue wrote:
> Given that there is confusion on this, I think we should decide whether it
> is required or not and update the docs to be more clear. Does that require a
> vote?
Although many consider it best practice for release tarballs to be tied back
to a
On 12/20/2014 04:07 AM, Bertrand Delacretaz wrote:
On Sat, Dec 20, 2014 at 7:16 AM, Niclas Hedhman wrote:
...Releases are the tarball(s) prepared by the release manager, not a pointer
into the source control system
Agreed. I also agree with Brane about the pointer into source code
control
On Sat, Dec 20, 2014 at 7:16 AM, Niclas Hedhman wrote:
> ...Releases are the tarball(s) prepared by the release manager, not a pointer
> into the source control system
Agreed. I also agree with Brane about the pointer into source code
control system being useful for PMC members to check that
On 20.12.2014 07:16, Niclas Hedhman wrote:
> Tags are at best a convenience, and nothing else. But so are commit id,
> since in the long-term, GIT may not prevail and the commit id is in effect
> an internal artifact of Git itself, not the concept of version control
> systems. Compare how commit nu
Tags are at best a convenience, and nothing else. But so are commit id,
since in the long-term, GIT may not prevail and the commit id is in effect
an internal artifact of Git itself, not the concept of version control
systems. Compare how commit numbers from Subversion are imported to Git
repositor
>
> I recently found this confusing with the first parquet-format release. I
> thought that both commit id and tag were optional, given that the actual
> release candidate is a signed tarball (actually, the "necessary source code
> to build the project" [1]).
>
Commit id is not optional. Tag is.
T
On 12/18/2014 05:58 AM, John D. Ament wrote:
All,
I was looking through the incubator site and I don't see anything definite.
Whenever a podling goes for a vote, and they include a git tag in their
vote message, it's typically asked to change to a commit id. It seems to
me this is done for the
Good point!
On Thu, Dec 18, 2014 at 01:58PM, John D. Ament wrote:
> All,
>
> I was looking through the incubator site and I don't see anything definite.
>
> Whenever a podling goes for a vote, and they include a git tag in their
> vote message, it's typically asked to change to a commit id. It
+1 on including commit ID (or SVN revision number) along with any tag (or SVN
tag/branch) for convenience.
-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Thursday, December 18, 2014 05:58
To: general@incubator.apache.org
Subject: Votes for git repos - commit
On Thursday, December 18, 2014, John D. Ament wrote:
> All,
>
> I was looking through the incubator site and I don't see anything definite.
>
> Whenever a podling goes for a vote, and they include a git tag in their
> vote message, it's typically asked to change to a commit id. It seems to
> me
All,
I was looking through the incubator site and I don't see anything definite.
Whenever a podling goes for a vote, and they include a git tag in their
vote message, it's typically asked to change to a commit id. It seems to
me this is done for the reproducible builds concept. Tags are mutable
15 matches
Mail list logo
