incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kanak Biscuitwala <kana...@hotmail.com>
Subject RE: [VOTE] helix-0.6.2-incubating
Date Sun, 24 Nov 2013 01:51:22 GMT
> Date: Sun, 24 Nov 2013 00:53:13 +0000
> Subject: Re: [VOTE] helix-0.6.2-incubating
> From: sebbaz@gmail.com
> To: general@incubator.apache.org
>
> On 23 November 2013 23:47, Kanak Biscuitwala <kanak.b@hotmail.com> wrote:
>> Oh, interesting. I believe it generates this automatically with the license-maven-plugin
in the build/package stage. In that case, is this an acceptable solution, or is an explicit
NOTICE file still required?
>
> Every ASF distribution must have LICENSE and NOTICE files (and
> DISCLAIMER for podlings)
> This includes releases and SCM.

Given this requirement, which of the following is the correct course of action?

1. Update master with a NOTICE file which is a copy of the generated NOTICE file (it looks
correct) and take no further action with the releases since the released packages contain
NOTICE files.
2. Update master and both tags with NOTICE files. Take no further action since the distributed
packages have 1:1 correspondence with all files in source control.
3. Update master and both tags with NOTICE files, skip the vote, and just update the already-pushed
packages.
4. Update master and both tags with NOTICE files, go through the entire voting process again,
re-release.

Really what I want to get out of all this is what is required to bring current and future
Helix releases to full compliance with ASF standards.

>
> The NOTICE file must not contain any unnecessary content - in
> particular it must only contain references to bits that are actually
> included in the distribution. I'm not sure whether the plugin handles
> this properly yet (early versions were not good in this regard).

It seems to do it correctly. The top level project is just the website for this project, which
has no dependencies other than ASF projects, and this is reflected in the generated NOTICE
file. Or does the top level NOTICE file need to be the union of all of its subprojects' NOTICE
files?

>
>> Olivier, can you provide some context?
>>
>> ----------------------------------------
>>> Date: Sat, 23 Nov 2013 23:01:14 +0000
>>> Subject: Re: [VOTE] helix-0.6.2-incubating
>>> From: sebbaz@gmail.com
>>> To: general@incubator.apache.org
>>>
>>> On 23 November 2013 22:07, Kanak Biscuitwala <kanak.b@hotmail.com> wrote:
>>>> No, the current release doesn't have a NOTICE file at the top level.
>>>
>>> Are you sure about that?
>>>
>>> I checked the file helix-0.6.2-incubating-src.zip and it seems to have
>>> NOTICE and LICENSE files in the correct place.
>>>
>>> Are you referring to something else?
>>>
>>>> The subcomponents we intended for release (i.e. helix-core, helix-agent,
helix-examples, and helix-admin-webapp) all have LICENSE, DISCLAIMER, and NOTICE files. If
we need a NOTICE file in the top level, then we'll have to re-run the release tools.
>>>>
>>>> If we re-run the release tools, is it required to start a new vote internally,
as well as a new vote on this list?
>>>>
>>>> Also, what do we do with the artifacts that have already been released?
>>>>
>>>> Thanks,
>>>> Kanak
>>>>
>>>> ----------------------------------------
>>>>> Date: Sat, 23 Nov 2013 21:28:25 +0000
>>>>> Subject: Re: [VOTE] helix-0.6.2-incubating
>>>>> From: sebbaz@gmail.com
>>>>> To: general@incubator.apache.org
>>>>>
>>>>> On 23 November 2013 19:57, Kanak Biscuitwala <kanak.b@hotmail.com>
wrote:
>>>>>> sebb, I fixed the tag to include NOTICE here: https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=d12177168347c9253f3b37946c06a7175f8a1997
>>>>>>
>>>>>> The parent directory doesn't actually contain any artifacts that
we package as binaries.
>>>>>
>>>>> Not really relevant.
>>>>> The NOTICE file must relate to the contents of the collection it
>>>>> relates to: e.g. the tag or the source archive or the binary archive
>>>>> etc.
>>>>> Likewise the LICENSE file.
>>>>>
>>>>>> Do we need to go through the entire release process again?
>>>>>
>>>>> Does the release have the correct NOTICE and LICENSE files?
>>>>>
>>>>>>
>>>>>>> From: kanak.b@hotmail.com
>>>>>>> To: general@incubator.apache.org
>>>>>>> Subject: [VOTE] helix-0.6.2-incubating
>>>>>>> Date: Mon, 18 Nov 2013 18:50:31 -0800
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> This is to call for a vote on releasing the following candidate
as Apache
>>>>>>> Helix 0.6.2-incubating. This is the first release candidate of
our third
>>>>>>> release at Apache.
>>>>>>>
>>>>>>> Apache Helix is a generic cluster management framework that makes
it easy
>>>>>>> to build partitioned and replicated, fault tolerant and scalable
>>>>>>> distributed systems.
>>>>>>>
>>>>>>> Release notes:
>>>>>>> http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html
>>>>>>>
>>>>>>> Our vote thread on helix-dev:
>>>>>>> http://markmail.org/message/f2odmc7ga2i5qqmh
>>>>>>>
>>>>>>> The following IPMC members have voted +1
>>>>>>> Patrick Hunt
>>>>>>> Olivier Lamy
>>>>>>>
>>>>>>> Release artifacts:
>>>>>>> https://repository.apache.org/content/repositories/orgapachehelix-138
>>>>>>>
>>>>>>> Distribution:
>>>>>>> * binaries:
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/
>>>>>>> * sources:
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/
>>>>>>>
>>>>>>> The 0.6.2-incubating release tag
>>>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340
>>>>>>>
>>>>>>> KEYS file available here:
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>>>>>>
>>>>>>> Please vote on the release. The vote will be open for 72 hours.
>>>>>>>
>>>>>>> [+1]
>>>>>>> [0]
>>>>>>> [-1]
>>>>>>>
>>>>>>> Thanks,
>>>>>>> The Apache Helix Team
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 		 	   		  
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message