Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Justin Mclean]

Hi.,

For those not wanting to download the release and unpack it, here's the current 
NOTICE file [1]

You’ll note it contains permissive license information (which should be in the 
license file), links to web sites rather than pointers to license text (license 
information can change over time and again should be in license) and mentions 
non bundled items (only bundled items need to be mentioned in license and 
notice).

Take for instance the license link to Font Awesome. It points to version 5 
which isn’t in any release, 4.7 is in a binary release but not the source 
release.

Thanks,
Justin

1. https://github.com/apache/incubator-servicecomb-website/blob/asf-site/NOTICE
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Justin Mclean]

Hi,

> "* We can do a minor improvement on the NOTICE formating”

IMO It needs more than minor improvements/changes, it's not just a formatting 
issue.

That being said no -1 vote is a veto if you get 3 +1 votes from other IPMC 
members then it’s a release.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Jean-Baptiste Onofré]

Hi Justin,

I mentioned this in my vote:

"* We can do a minor improvement on the NOTICE formating"

The content looks OK to me, but not in the right place/formating. I didn't
consider this as blocker (as it's there, even if not super accurate) and we can
fix in the next cycle, but I got your point.

Regards
JB

On 03/02/2018 09:26 AM, Justin Mclean wrote:
> Hi,
> 
> -1 (binding) as there is incorrect and far too much information in NOTICE. 
> License information goes in LICENSE not NOTICE. [1] Also only things that are 
> actually bundled need to be mentioned not dependancies. [2]
> 
> BTW it's not entirely clear which of the releases artefacts are source 
> release and what aren’t without carefully looking at them.
> 
> I checked:
> - signatures and hash correct
> - disclaimer exists
> - LICENSE is missing things
> - NOTICE is not correct
> - no unexpected binaries
> - source code have ASF headers
> 
> Thanks,
> Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3

[Makoto Yui]

Justin,

Thank you for verification!

Will certainly fix `font-awesome.css` issue in the next release.

Makoto

2018-03-03 12:40 GMT+09:00 Justin Mclean :
> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - disclaimer exists
> - LICENSE and NOTICE good
> - all source files have ASF headers
> - no unexpected binary files
>
> I noticed a minor issue is that LICENSE is missing the MIT license for this 
> file [1]
>
> Thanks,
> Justin
>
> 1. hivemall-0.5.0-incubating/src/site/resources/css/font-awesome.css
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name
- signatures and hashes correct
- disclaimer exists
- LICENSE and NOTICE good
- all source files have ASF headers
- no unexpected binary files

I noticed a minor issue is that LICENSE is missing the MIT license for this 
file [1]

Thanks,
Justin

1. hivemall-0.5.0-incubating/src/site/resources/css/font-awesome.css
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2

[Justin Mclean]

Hi,

-1 (binding) as there’s BSD and other license information in the NOTICE file. 
Also in general only relocated copyright lines need to be included in NOTICE 
[1] not the copyright of permissive bundled software. [2] The full license text 
is not included in the license file.

I checked:
- incubating in name
- signature and hashes fine
- DISCLAIMER exists
- LICENSE is missing full text of the licenses (BSD license text for instance 
includes the copyright line)
- NOTICE contain unneeded information
- No unexpected binary files
- Source file have ASF headers

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#mod-notice 

2. http://www.apache.org/dev/licensing-howto.html#permissive-deps 

Re: Two issues with license and notice auditing

[Carlos Santana]

As always Sebb thank you for your advice and quick response.


On Fri, Mar 2, 2018 at 10:27 AM sebb  wrote:

> On 2 March 2018 at 11:41, Carlos Santana  wrote:
> > Thanks sebb
> >
> > What do we do with “Apache Tentacles cannot support tar.gz”
>
> Never used it, but here are some suggestions:
>
> Provide a patch to the project.
>
> Unpack the archive and check it manually
>
> Unpack the archive and repack as zip, then use tentacles again.
>
> If there is a zip archive as well as a tar.gz, then use Tentacles to
> check the zip, and a diff program to check that the contents of the
> two archives are the same.
> (which they should be, barring any EOL considerations).
>
> > How are others dealing with this? Are you using Tentacles or another tool
> > in your releases?
> >
> > — Carlks
> >
> > On Fri, Mar 2, 2018 at 5:07 AM sebb  wrote:
> >
> >> On 2 March 2018 at 04:28, Carlos Santana  wrote:
> >> > Forwarding to Incubator mailing list to see if they any guidance.
> >> >
> >> > -- Forwarded message -
> >> > From: Ying Chun Guo 
> >> > Date: Thu, Mar 1, 2018 at 10:27 PM
> >> > Subject: Two issues with license and notice auditing
> >> > To: 
> >> >
> >> >
> >> > Hi, team
> >> >
> >> > When we are using Apache Creadur to audit licensing and notice files,
> we
> >> > met with two problems. I'm looking for any people who have
> experiences on
> >> > that.
> >> >
> >> > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
> >> format
> >> > of Apache license header, which we plan to use in the small test
> files.
> >>
> >> Please raise a JIRA against RAT so the license can be added to the list.
> >>
> >> Meanwhile, you can add your own licenses:
> >>
> >>
> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
> >>
> >> > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
> >> >
> >> > We have solutions to bypass these two questions. For the first issue,
> we
> >> > can put those files with mini headers in the Rat exclusion list.
> >>
> >> Please don't do that; see above.
> >>
> >> > For the
> >> > second issue, we can use bash script to check LICENSE and NOTICE or we
> >> can
> >> > use zip format instead, other than tar.gz. But I would like to check
> if
> >> > there are any other suggestions to these issues. Thanks.
> >> >
> >> > Best regards
> >> > Ying Chun Guo (Daisy)
> >>
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Justin Mclean]

Hi,

> I just checked some projects Notice file, it looks like some projects[1][2]
> list the License information about the third party dependencies in the
> Notice file

Which would be incorrect to do so. What you are seeing here in the Hadoop case 
is an upstream project have extra information in  NOTICE files and if you 
bundle code from an ALv2 licensed project you need to propagate the NOTICE file 
into your NOTICE file. That different from listing the 3rd party dependancies 
in NOTICE. The Space NOTICE file is IMO a poor one to copy from. There may be 
other historical reasons for why these NOTICE files are the way they are.

This I also point out the not the first time that Hadoop and Sparks NOTICE file 
have cases some confusion for incubating projects.

> and some of them[3] just list bundled NOTICE files.

Which would be correct.

> I guess spark and hadoop are trying they best to list all the legal
> statements of third party dependencies in the NOTICE file to avoid the
> violation of the Open Source License.

No NOTICE is not for that, only required notices [1] and relocated copyrights 
need to be put in NOTICE. The NOTICE file is for informational purposes only 
and doesn't modify any of the license terms. [2] License information should be 
listed in LICENSE.

> Could you give us some guide about how to keep the NOTICE file simple and
> without introducing any legal issues?

Remove all mention Apache, BSD and MIT software [3] and remove all mention any 
anything that is not bundled. [4] See also [7]

> As you may know the Service Center project is developed with Go language.
> Go language need to compile the source code to build whole exe binary. So
> we list all the third party dependencies code copyrights in the Notice
> file.

In  that case the binary would have a different LICENCE and NOTICE content than 
the source release. [5]

> As the lot of Go codes just put the License in the root directory, the
> source code doesn't have the License header, it could be a challenge for us
> to do the explicit statement without adding the copyright to NOTICE file.

They don’t need to be put in NOTICE they should be listed in LICENSE either 
with the full text or preferably with a pointer to the full text of the license 
in question. [6]

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#required-third-party-notices 

2. https://www.apache.org/licenses/LICENSE-2.0#redistribution 

3. http://www.apache.org/dev/licensing-howto.html#permissive-deps 

4. http://www.apache.org/dev/licensing-howto.html#guiding-principle 

5. http://www.apache.org/dev/licensing-howto.html#binary 

6. http://www.apache.org/dev/licensing-howto.html#permissive-deps 

7.http://www.apache.org/dev/licensing-howto.html#mod-notice 

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Jai Asher]

 Hi,

The vote for releasing Apache Pulsar 1.22.0-incubating is now closed.

With a total of +5 binding votes and no -1 votes, the vote passes.

+1s (binding):
Sijie
Justin
Stian
Andrews
Jim

Thanks a lot to all the reviewers for taking the time to validate this
release!

Regards,
Jai



On Fri, Mar 2, 2018 at 5:39 AM, Jim Jagielski  wrote:

> +1 (binding)
>
> > On Mar 2, 2018, at 3:17 AM, Andrews Sahaya Albert
>  wrote:
> >
> > +1
> >
> > - Verified signatures
> > - Ran simple producer & consumer against the binary distribution
> > - Compiled the src distribution, ran unit tests and ran sample
> > producer/consumer test against it
> > - OS version: MacOS 10.12.6
> >
> >
> > - I had to update "advertisedAddress=" to localhost in
> > conf/standalone.conf to get the producer and consumer connect to the
> > broker, which I didn't have to do in previous releases. It could be
> > due to my laptop upgrade. Can't we set "localhost" as the default
> > value instead of empty?
> >
> > 2018-03-01 23:24:51,640 - WARN  -
> > [pulsar-client-io-1-1:ConnectionPool@200] - Failed to open connection
> > to MYHOSTNAME:6650 : CompletionException
> > 2018-03-01 23:24:51,640 - WARN  -
> > [pulsar-client-io-1-1:HandlerBase@85] -
> > [persistent://sample/standalone/test1/t1-51] [sub1] Error connecting
> > to broker: org.apache.pulsar.client.api.PulsarClientException:
> > java.util.concurrent.CompletionException:
> > java.net.UnknownHostException: failed to resolve 'MYHOSTNAME' after 4
> > queries
> >
> > Thanks,
> > Andrews.
> >
> > On Thu, Mar 1, 2018 at 12:40 AM, Sijie Guo  wrote:
> >> +1
> >>
> >> * the distributions looks good (checked md5, sha, asc)
> >> * test the binary distribution: standalone, run examples
> >> * src distribution looks good: compile, unit tests, run standalone and
> >> examples.
> >>
> >> Verified at MacOS 10.13.1
> >>
> >> - Sijie
> >>
> >>
> >> On Sun, Feb 25, 2018 at 3:42 PM, Jai Asher 
> wrote:
> >>
> >>> Kindly ignore the previous message sent on the same subject since it
> >>> contained the wrong dates.
> >>> ==
> >>>
> >>> This is the fourth release candidate for Apache Pulsar, version
> >>> 1.22.0-incubating.
> >>>
> >>> It fixes the following issues:
> >>> https://github.com/apache/incubator-pulsar/milestone/11?closed=1
> >>>
> >>> *** Please download, test and vote by Thursday, March 1, 2018, 10:00
> GMT.
> >>>
> >>> Note that we are voting upon the source (tag), binaries are provided
> for
> >>> convenience.
> >>>
> >>> Source and binary files:
> >>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> >>> pulsar-1.22.0-incubating-candidate-3/
> >>>
> >>> Maven staging repo:
> >>> https://repository.apache.org/content/repositories/
> orgapachepulsar-1010/
> >>>
> >>> The tag to be voted upon:
> >>> v1.22.0-incubating-candidate-3 (5d14788e510faec23fd8ed189ed343
> e93b489dda)
> >>> https://github.com/apache/incubator-pulsar/releases/tag/
> >>> v1.22.0-incubating-candidate-3
> >>>
> >>> Pulsar's KEYS file containing PGP keys we use to sign the release:
> >>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >>>
> >>> Please download the source package, and follow the README to build
> >>> and run the Pulsar standalone service.
> >>>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Druid 0.12.0 release (pre incubation)

[Gian Merlino]

Thanks for the advice Julian.

For our next release after 0.12.0, with our normal schedule we would look
to start doing release candidates later this month and aim for a final
release in April / May (Druid release candidates usually bake for a month
or so). Whether we could do those release candidates in the incubator or
not depends on how fast we can get stuff migrated over -- I am optimistic
we can get it done fast enough but I am not totally sure.

Gian

On Fri, Mar 2, 2018 at 1:15 PM, Julian Hyde  wrote:

> As a mentor of Druid, sounds good to me. It’s good to keep on releasing
> regularly - the community relies on it.
>
> Please mention this in the board report (due in about a week).
>
> When will the next release be, and will you be able to make that under the
> incubator process?
>
> Julian
>
>
> > On Mar 2, 2018, at 1:09 PM, Gian Merlino  wrote:
> >
> > Hi incubators,
> >
> > Druid was recently accepted into the incubator (yay) - I now want to
> bring
> > up a release vote we already had in progress and that we expect to
> complete
> > early next week:
> > https://groups.google.com/d/topic/druid-development/sK777vmZ
> cR0/discussion.
> > Since this release is likely just days away, we intend to publish it as
> our
> > final pre-incubation release. Of course, we won't call it Apache Druid,
> and
> > we'll release it on http://druid.io/, not on
> > http://druid.incubator.apache.org/.
> >
> > Are there any other precautions we should take to avoid confusion? We
> could
> > also include some explicit statement that this release is not an Apache
> > release, to avoid confusing anyone that may have heard that Druid is
> > starting incubation.
> >
> > Gian
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Druid 0.12.0 release (pre incubation)

[Julian Hyde]

As a mentor of Druid, sounds good to me. It’s good to keep on releasing 
regularly - the community relies on it.

Please mention this in the board report (due in about a week).

When will the next release be, and will you be able to make that under the 
incubator process?

Julian


> On Mar 2, 2018, at 1:09 PM, Gian Merlino  wrote:
> 
> Hi incubators,
> 
> Druid was recently accepted into the incubator (yay) - I now want to bring
> up a release vote we already had in progress and that we expect to complete
> early next week:
> https://groups.google.com/d/topic/druid-development/sK777vmZcR0/discussion.
> Since this release is likely just days away, we intend to publish it as our
> final pre-incubation release. Of course, we won't call it Apache Druid, and
> we'll release it on http://druid.io/, not on
> http://druid.incubator.apache.org/.
> 
> Are there any other precautions we should take to avoid confusion? We could
> also include some explicit statement that this release is not an Apache
> release, to avoid confusing anyone that may have heard that Druid is
> starting incubation.
> 
> Gian


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Druid 0.12.0 release (pre incubation)

[Gian Merlino]

Hi incubators,

Druid was recently accepted into the incubator (yay) - I now want to bring
up a release vote we already had in progress and that we expect to complete
early next week:
https://groups.google.com/d/topic/druid-development/sK777vmZcR0/discussion.
Since this release is likely just days away, we intend to publish it as our
final pre-incubation release. Of course, we won't call it Apache Druid, and
we'll release it on http://druid.io/, not on
http://druid.incubator.apache.org/.

Are there any other precautions we should take to avoid confusion? We could
also include some explicit statement that this release is not an Apache
release, to avoid confusing anyone that may have heard that Druid is
starting incubation.

Gian

Re: [IP CLEARANCE] Apache Felix Bundle Archive File Installer Extension

[Craig Russell]

Hi Bertrand,

> On Mar 1, 2018, at 10:20 PM, Bertrand Delacretaz  
> wrote:
> 
> Hi Craig,
> 
> On Fri, Mar 2, 2018 at 1:19 AM, Craig Russell  wrote:
>> I apologize for coming late to this discussion, but longstanding policy
>> is to accept either SGA or CCLA that identifies the contribution to the
>> satisfaction of the contributor
> 
> So IIUC this means you agree with the way this has been handled?

I agree with accepting Intel's CCLA/grant for "Felix" and proceeding with IP 
Clearance.

I agree with the conclusion that Intel's explicit grant for "Felix" as 
identified on Schedule B of the CCLA provides sufficient coverage for us to 
remove Intel's copyright statements on the code donated to Felix.
> 
> I'm asking just to make sure the archives of this thread provide a
> very clear answer,
> in case we have similar situations in the future.

I hope that this thread will inform future situations where a CCLA/SGA is 
descriptive but not extremely detailed.

Craig

> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2

[Steve Lawrence]

The Apache Daffodil community has voted and approved the proposed
release of Apache Daffodil (Incubating) 2.1.0-rc2.

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Daffodil is an open source implementation of the DFDL specification that
uses DFDL schemas to parse fixed format data into an infoset, which is
most commonly represented as either XML or JSON. This allows the use of
well-established XML or JSON technologies and libraries to consume,
inspect, and manipulate fixed format data in existing solutions.
Daffodil is also capable of the reverse by serializing or "unparsing" an
XML or JSON infoset back to the original data format.

Vote thread:
https://lists.apache.org/thread.html/4b71db31a6a420098a18139a046c5493d5685137251b4727736a9f18@%3Cdev.daffodil.apache.org%3E

Specific issues found during the rc2 VOTE that are planned to be
resolved in the next release include:

  DAFFODIL-1906: Updates to LICENSE/NOTICE files
https://issues.apache.org/jira/browse/DAFFODIL-1906

  LEGAL-369: Guidance on Open Grid Forum (OGF) document inclusion
https://issues.apache.org/jira/browse/LEGAL-369

Result thread:
https://lists.apache.org/thread.html/f883421a96deffee80e59bd2fbbf07062dfe0ee26e4c4c4cfa194ba5@%3Cdev.daffodil.apache.org%3E


All distribution packages, including signatures, digests, etc. can be
found at:

https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.1.0-rc2/

Staging artifacts can be found at:

https://repository.apache.org/content/repositories/orgapachedaffodil-1001/

This release has been signed with PGP key 033AE661, corresponding to
slawre...@apache.org, which is included in the repository's KEYS file.
This key can be found on keyservers, such as:

http://pgp.mit.edu/pks/lookup?op=get=0x033AE661

It is also listed here:

https://people.apache.org/keys/committer/slawrence.asc

The release candidate has been tagged in git with v2.1.0-rc2.

For reference, here is a list of all closed JIRAs tagged with 2.1.0:

https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

For a summary of the changes in this release, see:

https://daffodil.apache.org/releases/2.1.0/

Please review and vote. The vote will be open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
- Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Willem Jiang]

Hi Justin

Thanks for the vote,  here is some thing that I want to clear about the
NOTICE file.

I just checked some projects Notice file, it looks like some projects[1][2]
list the License information about the third party dependencies in the
Notice file, and some of them[3] just list bundled NOTICE files.
 I guess spark and hadoop are trying they best to list all the legal
statements of third party dependencies in the NOTICE file to avoid the
violation of the Open Source License.
Could you give us some guide about how to keep the NOTICE file simple and
without introducing any legal issues?

As you may know the Service Center project is developed with Go language.
Go language need to compile the source code to build whole exe binary. So
we list all the third party dependencies code copyrights in the Notice
file.  I just found there are some guideline about the copyright
notification here[4].

"However, elements such as the copyright notifications embedded within BSD
and MIT licenses need  not
 be duplicated in NOTICE --
it suffices to leave those notices in their original locations."

As the lot of Go codes just put the License in the root directory, the
source code doesn't have the License header, it could be a challenge for us
to do the explicit statement without adding the copyright to NOTICE file.

Finally We will add the src postfix to the source zip for user to find out
it easily.


[1]https://github.com/apache/spark/blob/master/NOTICE
[2]https://github.com/apache/hadoop/blob/trunk/NOTICE.txt
[3]
https://github.com/apache/camel/blob/master/apache-camel/src/main/release/NOTICE.txt
[4]http://www.apache.org/dev/licensing-howto.html#guiding-principle





Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 2, 2018 at 4:26 PM, Justin Mclean  wrote:

> Hi,
>
> -1 (binding) as there is incorrect and far too much information in NOTICE.
> License information goes in LICENSE not NOTICE. [1] Also only things that
> are actually bundled need to be mentioned not dependancies. [2]
>
> BTW it's not entirely clear which of the releases artefacts are source
> release and what aren’t without carefully looking at them.
>
> I checked:
> - signatures and hash correct
> - disclaimer exists
> - LICENSE is missing things
> - NOTICE is not correct
> - no unexpected binaries
> - source code have ASF headers
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Two issues with license and notice auditing

[sebb]

On 2 March 2018 at 11:41, Carlos Santana  wrote:
> Thanks sebb
>
> What do we do with “Apache Tentacles cannot support tar.gz”

Never used it, but here are some suggestions:

Provide a patch to the project.

Unpack the archive and check it manually

Unpack the archive and repack as zip, then use tentacles again.

If there is a zip archive as well as a tar.gz, then use Tentacles to
check the zip, and a diff program to check that the contents of the
two archives are the same.
(which they should be, barring any EOL considerations).

> How are others dealing with this? Are you using Tentacles or another tool
> in your releases?
>
> — Carlks
>
> On Fri, Mar 2, 2018 at 5:07 AM sebb  wrote:
>
>> On 2 March 2018 at 04:28, Carlos Santana  wrote:
>> > Forwarding to Incubator mailing list to see if they any guidance.
>> >
>> > -- Forwarded message -
>> > From: Ying Chun Guo 
>> > Date: Thu, Mar 1, 2018 at 10:27 PM
>> > Subject: Two issues with license and notice auditing
>> > To: 
>> >
>> >
>> > Hi, team
>> >
>> > When we are using Apache Creadur to audit licensing and notice files, we
>> > met with two problems. I'm looking for any people who have experiences on
>> > that.
>> >
>> > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
>> format
>> > of Apache license header, which we plan to use in the small test files.
>>
>> Please raise a JIRA against RAT so the license can be added to the list.
>>
>> Meanwhile, you can add your own licenses:
>>
>> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
>>
>> > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
>> >
>> > We have solutions to bypass these two questions. For the first issue, we
>> > can put those files with mini headers in the Rat exclusion list.
>>
>> Please don't do that; see above.
>>
>> > For the
>> > second issue, we can use bash script to check LICENSE and NOTICE or we
>> can
>> > use zip format instead, other than tar.gz. But I would like to check if
>> > there are any other suggestions to these issues. Thanks.
>> >
>> > Best regards
>> > Ying Chun Guo (Daisy)
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Jim Jagielski]

+1 (binding)

> On Mar 2, 2018, at 3:17 AM, Andrews Sahaya Albert  
> wrote:
> 
> +1
> 
> - Verified signatures
> - Ran simple producer & consumer against the binary distribution
> - Compiled the src distribution, ran unit tests and ran sample
> producer/consumer test against it
> - OS version: MacOS 10.12.6
> 
> 
> - I had to update "advertisedAddress=" to localhost in
> conf/standalone.conf to get the producer and consumer connect to the
> broker, which I didn't have to do in previous releases. It could be
> due to my laptop upgrade. Can't we set "localhost" as the default
> value instead of empty?
> 
> 2018-03-01 23:24:51,640 - WARN  -
> [pulsar-client-io-1-1:ConnectionPool@200] - Failed to open connection
> to MYHOSTNAME:6650 : CompletionException
> 2018-03-01 23:24:51,640 - WARN  -
> [pulsar-client-io-1-1:HandlerBase@85] -
> [persistent://sample/standalone/test1/t1-51] [sub1] Error connecting
> to broker: org.apache.pulsar.client.api.PulsarClientException:
> java.util.concurrent.CompletionException:
> java.net.UnknownHostException: failed to resolve 'MYHOSTNAME' after 4
> queries
> 
> Thanks,
> Andrews.
> 
> On Thu, Mar 1, 2018 at 12:40 AM, Sijie Guo  wrote:
>> +1
>> 
>> * the distributions looks good (checked md5, sha, asc)
>> * test the binary distribution: standalone, run examples
>> * src distribution looks good: compile, unit tests, run standalone and
>> examples.
>> 
>> Verified at MacOS 10.13.1
>> 
>> - Sijie
>> 
>> 
>> On Sun, Feb 25, 2018 at 3:42 PM, Jai Asher  wrote:
>> 
>>> Kindly ignore the previous message sent on the same subject since it
>>> contained the wrong dates.
>>> ==
>>> 
>>> This is the fourth release candidate for Apache Pulsar, version
>>> 1.22.0-incubating.
>>> 
>>> It fixes the following issues:
>>> https://github.com/apache/incubator-pulsar/milestone/11?closed=1
>>> 
>>> *** Please download, test and vote by Thursday, March 1, 2018, 10:00 GMT.
>>> 
>>> Note that we are voting upon the source (tag), binaries are provided for
>>> convenience.
>>> 
>>> Source and binary files:
>>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
>>> pulsar-1.22.0-incubating-candidate-3/
>>> 
>>> Maven staging repo:
>>> https://repository.apache.org/content/repositories/orgapachepulsar-1010/
>>> 
>>> The tag to be voted upon:
>>> v1.22.0-incubating-candidate-3 (5d14788e510faec23fd8ed189ed343e93b489dda)
>>> https://github.com/apache/incubator-pulsar/releases/tag/
>>> v1.22.0-incubating-candidate-3
>>> 
>>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>>> 
>>> Please download the source package, and follow the README to build
>>> and run the Pulsar standalone service.
>>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Two issues with license and notice auditing

[John D. Ament]

Probably a similar response - raise a ticket to Tentacles
https://issues.apache.org/jira/projects/TENTACLES/issues

FWIW, this is the first I'm ever hearing of this project.

John

On Fri, Mar 2, 2018 at 6:41 AM Carlos Santana  wrote:

> Thanks sebb
>
> What do we do with “Apache Tentacles cannot support tar.gz”
>
> How are others dealing with this? Are you using Tentacles or another tool
> in your releases?
>
> — Carlks
>
> On Fri, Mar 2, 2018 at 5:07 AM sebb  wrote:
>
> > On 2 March 2018 at 04:28, Carlos Santana  wrote:
> > > Forwarding to Incubator mailing list to see if they any guidance.
> > >
> > > -- Forwarded message -
> > > From: Ying Chun Guo 
> > > Date: Thu, Mar 1, 2018 at 10:27 PM
> > > Subject: Two issues with license and notice auditing
> > > To: 
> > >
> > >
> > > Hi, team
> > >
> > > When we are using Apache Creadur to audit licensing and notice files,
> we
> > > met with two problems. I'm looking for any people who have experiences
> on
> > > that.
> > >
> > > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
> > format
> > > of Apache license header, which we plan to use in the small test files.
> >
> > Please raise a JIRA against RAT so the license can be added to the list.
> >
> > Meanwhile, you can add your own licenses:
> >
> >
> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
> >
> > > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
> > >
> > > We have solutions to bypass these two questions. For the first issue,
> we
> > > can put those files with mini headers in the Rat exclusion list.
> >
> > Please don't do that; see above.
> >
> > > For the
> > > second issue, we can use bash script to check LICENSE and NOTICE or we
> > can
> > > use zip format instead, other than tar.gz. But I would like to check if
> > > there are any other suggestions to these issues. Thanks.
> > >
> > > Best regards
> > > Ying Chun Guo (Daisy)
> >
>

Re: Two issues with license and notice auditing

[Carlos Santana]

Thanks sebb

What do we do with “Apache Tentacles cannot support tar.gz”

How are others dealing with this? Are you using Tentacles or another tool
in your releases?

— Carlks

On Fri, Mar 2, 2018 at 5:07 AM sebb  wrote:

> On 2 March 2018 at 04:28, Carlos Santana  wrote:
> > Forwarding to Incubator mailing list to see if they any guidance.
> >
> > -- Forwarded message -
> > From: Ying Chun Guo 
> > Date: Thu, Mar 1, 2018 at 10:27 PM
> > Subject: Two issues with license and notice auditing
> > To: 
> >
> >
> > Hi, team
> >
> > When we are using Apache Creadur to audit licensing and notice files, we
> > met with two problems. I'm looking for any people who have experiences on
> > that.
> >
> > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
> format
> > of Apache license header, which we plan to use in the small test files.
>
> Please raise a JIRA against RAT so the license can be added to the list.
>
> Meanwhile, you can add your own licenses:
>
> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
>
> > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
> >
> > We have solutions to bypass these two questions. For the first issue, we
> > can put those files with mini headers in the Rat exclusion list.
>
> Please don't do that; see above.
>
> > For the
> > second issue, we can use bash script to check LICENSE and NOTICE or we
> can
> > use zip format instead, other than tar.gz. But I would like to check if
> > there are any other suggestions to these issues. Thanks.
> >
> > Best regards
> > Ying Chun Guo (Daisy)
>

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Andrews Sahaya Albert]

+1

- Verified signatures
- Ran simple producer & consumer against the binary distribution
- Compiled the src distribution, ran unit tests and ran sample
producer/consumer test against it
- OS version: MacOS 10.12.6


- I had to update "advertisedAddress=" to localhost in
conf/standalone.conf to get the producer and consumer connect to the
broker, which I didn't have to do in previous releases. It could be
due to my laptop upgrade. Can't we set "localhost" as the default
value instead of empty?

2018-03-01 23:24:51,640 - WARN  -
[pulsar-client-io-1-1:ConnectionPool@200] - Failed to open connection
to MYHOSTNAME:6650 : CompletionException
2018-03-01 23:24:51,640 - WARN  -
[pulsar-client-io-1-1:HandlerBase@85] -
[persistent://sample/standalone/test1/t1-51] [sub1] Error connecting
to broker: org.apache.pulsar.client.api.PulsarClientException:
java.util.concurrent.CompletionException:
java.net.UnknownHostException: failed to resolve 'MYHOSTNAME' after 4
queries

Thanks,
Andrews.

On Thu, Mar 1, 2018 at 12:40 AM, Sijie Guo  wrote:
> +1
>
> * the distributions looks good (checked md5, sha, asc)
> * test the binary distribution: standalone, run examples
> * src distribution looks good: compile, unit tests, run standalone and
> examples.
>
> Verified at MacOS 10.13.1
>
> - Sijie
>
>
> On Sun, Feb 25, 2018 at 3:42 PM, Jai Asher  wrote:
>
>> Kindly ignore the previous message sent on the same subject since it
>> contained the wrong dates.
>> ==
>>
>> This is the fourth release candidate for Apache Pulsar, version
>> 1.22.0-incubating.
>>
>> It fixes the following issues:
>> https://github.com/apache/incubator-pulsar/milestone/11?closed=1
>>
>> *** Please download, test and vote by Thursday, March 1, 2018, 10:00 GMT.
>>
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>>
>> Source and binary files:
>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
>> pulsar-1.22.0-incubating-candidate-3/
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachepulsar-1010/
>>
>> The tag to be voted upon:
>> v1.22.0-incubating-candidate-3 (5d14788e510faec23fd8ed189ed343e93b489dda)
>> https://github.com/apache/incubator-pulsar/releases/tag/
>> v1.22.0-incubating-candidate-3
>>
>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>>
>> Please download the source package, and follow the README to build
>> and run the Pulsar standalone service.
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3

[Makoto Yui]

Hi IPMC members,

It's already 72 hours passed.

We need two more votes from IPMC members.

Could anyone in IPMC volunteer help verifying our release?

With a prepared docker image, just type the following commands to run Rat check:

  $ docker run -it hivemall/verify:v0.5.0-rc3
  $ wget 
https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/hivemall-0.5.0-incubating-source-release.zip
  $ unzip hivemall-0.5.0-incubating-source-release.zip
  $ cd hivemall-0.5.0-incubating
  $ mvn apache-rat:check

Thanks,
Makoto

2018-02-20 14:19 GMT+09:00 Makoto Yui :
> Hi all,
>
> The Apache Hivemall community has approved a proposal to release
> Apache Hivemall v0.5.0
> by v0.5.0 Release Candidate 3.
>
> We now kindly request that the Incubator PMC members review and vote
> on this incubator release candidate.
>
> The PPMC vote thread is located here:
> 
> https://www.mail-archive.com/dev@hivemall.incubator.apache.org/msg00462.html
> (vote)
> 
> https://www.mail-archive.com/dev@hivemall.incubator.apache.org/msg00468.html
> (vote result)
>
> Links to various release artifacts are given below.
>
> - The source tarball, including signatures, digests, ChangeLog, etc.:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/
> - Sources for the release:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/hivemall-0.5.0-incubating-source-release.zip
> - Git tag for the release:
>   
> https://git-wip-us.apache.org/repos/asf?p=incubator-hivemall.git;a=shortlog;h=refs/tags/v0.5.0-rc3
> - The Nexus Staging URL:
>   
> https://repository.apache.org/content/repositories/orgapachehivemall-1003/
> - KEYS file for verification:
>   https://dist.apache.org/repos/dist/dev/incubator/hivemall/KEYS
> - For information about the contents of this release, see:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/ChangeLog.html
>
> Artifacts verification how-to can be found in
> http://hivemall.incubator.apache.org/verify_artifacts.html
>
> Please vote accordingly:
>
> [ ] +1  approve (Release this package as Apache Hivemall 0.5.0-incubating)
> [ ] -1  disapprove (and reason why)
>
> The vote will be open for at least 72 hours.
>
> Regards,
> Makoto
> on behalf of Apache Hivemall PPMC
>
> --
> Makoto YUI 
> Research Engineer, Treasure Data, Inc.
> http://myui.github.io/



-- 
Makoto YUI 
Research Engineer, Treasure Data, Inc.
http://myui.github.io/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Two issues with license and notice auditing

[sebb]

On 2 March 2018 at 04:28, Carlos Santana  wrote:
> Forwarding to Incubator mailing list to see if they any guidance.
>
> -- Forwarded message -
> From: Ying Chun Guo 
> Date: Thu, Mar 1, 2018 at 10:27 PM
> Subject: Two issues with license and notice auditing
> To: 
>
>
> Hi, team
>
> When we are using Apache Creadur to audit licensing and notice files, we
> met with two problems. I'm looking for any people who have experiences on
> that.
>
> 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short format
> of Apache license header, which we plan to use in the small test files.

Please raise a JIRA against RAT so the license can be added to the list.

Meanwhile, you can add your own licenses:
https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html

> 2. Apache Tentacles cannot support tar.gz files in the staging repo.
>
> We have solutions to bypass these two questions. For the first issue, we
> can put those files with mini headers in the Rat exclusion list.

Please don't do that; see above.

> For the
> second issue, we can use bash script to check LICENSE and NOTICE or we can
> use zip format instead, other than tar.gz. But I would like to check if
> there are any other suggestions to these issues. Thanks.
>
> Best regards
> Ying Chun Guo (Daisy)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Stian Soiland-Reyes]

?On 25 February 2018 at 23:36, Jai Asher  wrote:
> This is the fourth release candidate for Apache Pulsar, version
> 1.22.0-incubating.
>
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/11?closed=1
>
> *** Please download, test and vote by Friday, Feb 23, 2018, 10:00 GMT.

Oo, I'll better hurry up then! :)
Normally the wording is "The vote is open for at least 72 hours" --
you are OK to keep it open a bit longer if you need sufficient votes
or have not tallied them yet.


> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-1.22.0-incubating-candidate-3/

Is it fourth of third release candidate? Use consistent numbering.
Starting with "RC0" is a bit unusual..

> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1010/

My vote: +1 (binding)


+0 checksums valid (I think)
? asc signatures (sorry, my machine lacks gpg today)
+1 tag vs commit
+0 src.tar.gz vs git tag  (generate_protobuf.sh and
generate_protobuf_docker.sh missing from dist - are they needed?)
+1 mvn install
+1 src LICENSE
+1 bin NOTICE
+0 src NOTICE -- copyright should extend into 2017-2018
+1 src/bin DISCLAIMER
+1 bin LICENSE and licenses (but why extra LICENSE-HdrHistogram0.txt?)
+0 bin NOTICE -- are all of these copyrights really forwarded from their NOTICE?
+1 mvn apache-rat:check - well-documented excludes

As an overall comment I think good work on the licenses!


I did a spot check, and guava.jar does not have a NOTICE, so unless
that was copied from a zip/tar that had such a NOTICE, then there
would be nothing to propagate. On the other side netty.jar has a
humongous NOTICE which somehow just becomes "Copyright 2014 The Netty
Project" in your NOTICE -- this seems to violate their Apache license.
  Has this been discussed on legael?


Your Git repository contains .gitignore.swp from vim which you
probably want to delete.



Your checksum files are in an unusual style:

C1 B8 C8 91 23 92 6A 56  82 F6 E9 F3 25 86 8B 58

CA1B352F 9576C8CB F16258F8 DEABF8F6 E95A926F 665E2FD8 30A38532 8BC639C6 20FD34E6
 6948396A CCD1A123 F072F93D 55D316EB EE34D208 9E0E9174 95AA09EE

Normally the .md5 and .sha512 files contain the checksum only, in
lowercase hex without spacing, e.g.

c1b8c89123926a5682f6e9f325868b58
ca1b352f9576c8cbf16258f8deabf8f6e95a926f665e2fd830a385328bc639c620fd34e66948396accd1a123f072f93d55d316ebee34d2089e0e917495aa09ee

This makes it easier to check against tools like md5sum and shasum.

You didn't include .sha1 checksums, but extra points for .sha512 :)

It is customary to include the checksums (at least md5) or the
dist.apache.org svn revision in the [VOTE] email, to any avoid
accidental last-minute-tampering confusion and to keep it in the
mailing list archives.


Tested with:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T20:39:06+01:00)
Maven home: /usr/local/share/maven
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Justin Mclean]

Hi,

+1 binding 

A minor issue the NOTICE year need updating.

I checked:
- incubating in name
- hashes and signatures good
- DISCLAIMER exists
- LICENSE is good
- NOTICE year is last year
- can compile from source

Thanks,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SensSoft (Incubating) UserALE.js 1.0.0 RC#1

[Justin Mclean]

Hi,

+1 binding 

There’s a minor thing in LICENSE that needs fixing.

I checked:
- signatures and hashes are good
- DISCLAIMER exists
- LICENSE appendix includes incorrect copyright
- NOTICE is good
- No unexpected binary files
- No sure if "compile from source" counts here :-)

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Justin Mclean]

Hi,

-1 (binding) as there is incorrect and far too much information in NOTICE. 
License information goes in LICENSE not NOTICE. [1] Also only things that are 
actually bundled need to be mentioned not dependancies. [2]

BTW it's not entirely clear which of the releases artefacts are source release 
and what aren’t without carefully looking at them.

I checked:
- signatures and hash correct
- disclaimer exists
- LICENSE is missing things
- NOTICE is not correct
- no unexpected binaries
- source code have ASF headers

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Timothy Chen]

+1 binding

Reviewed license and release artifacts / signatures.

Tim

On Fri, Mar 2, 2018 at 12:05 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Reviewed:
> * build from src
> * ASF headers
> * checksum and signatures
> * DISCLAIMER
> * License is OK
> * We can do a minor improvement on the NOTICE formating
>
> Thanks !
> Regards
> JB
>
> On 02/28/2018 02:25 PM, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for vote to release Apache ServiceComb Service-Center
> (Incubating) version 1.0.0-m1.
> >
> > Apache ServiceComb (Incubating) Community has voted and approved the
> release.
> >
> > Vote Thread:
> https://lists.apache.org/thread.html/b2d87628d019c069f478c56cadaf794112add210c504e3ac4c3056e5@%3Cdev.servicecomb.apache.org%3E
> >
> > Result Thread:
> https://lists.apache.org/thread.html/527a77d1467880602a7d679bd21d281b58fb365fa29b18a96a2a3676@%3Cdev.servicecomb.apache.org%3E
> >
> > Release Notes:
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes.md
> >
> > Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m1/
> >
> > Release Tag:
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m1
> >
> > Release CommitID:  8d40fc3b10e99c9084a7b62504226007660ad6de
> >
> > Keys to Verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >
> > Guide to build the release from Source:
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> >
> > Voting will start now(Wednesday, February 28, 2018) and will remain open
> for next 72 hours, Request all IPMC members to give their vote.
> >
> > [ ] +1 Release this package as 1.0.0-m1.
> > [ ] +0 No Opinion.
> > [ ] -1 Do not release this package because...
> >
> > Regards
> > Asif
> >
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Jean-Baptiste Onofré]

+1 (binding)

Reviewed:
* build from src
* ASF headers
* checksum and signatures
* DISCLAIMER
* License is OK
* We can do a minor improvement on the NOTICE formating

Thanks !
Regards
JB

On 02/28/2018 02:25 PM, Mohammad Asif Siddiqui wrote:
> Hello All,
> 
> This is a call for vote to release Apache ServiceComb Service-Center 
> (Incubating) version 1.0.0-m1.
> 
> Apache ServiceComb (Incubating) Community has voted and approved the release.
> 
> Vote Thread: 
> https://lists.apache.org/thread.html/b2d87628d019c069f478c56cadaf794112add210c504e3ac4c3056e5@%3Cdev.servicecomb.apache.org%3E
> 
> Result Thread: 
> https://lists.apache.org/thread.html/527a77d1467880602a7d679bd21d281b58fb365fa29b18a96a2a3676@%3Cdev.servicecomb.apache.org%3E
> 
> Release Notes: 
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes.md
> 
> Release Candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m1/
> 
> Release Tag: 
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m1
> 
> Release CommitID:  8d40fc3b10e99c9084a7b62504226007660ad6de
> 
> Keys to Verify the Release Candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> 
> Guide to build the release from Source: 
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> 
> Voting will start now(Wednesday, February 28, 2018) and will remain open for 
> next 72 hours, Request all IPMC members to give their vote.
> 
> [ ] +1 Release this package as 1.0.0-m1.
> [ ] +0 No Opinion.
> [ ] -1 Do not release this package because...
> 
> Regards
> Asif
> 
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org