[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-233.
Resolution: Fixed
> Integrate [maven-release-plugin] for eagle rele
[
https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen closed EAGLE-367.
--
Resolution: Fixed
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-
[
https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-367:
---
Fix Version/s: v0.4.0
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-
[
https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen reopened EAGLE-367:
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-
[
https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-367:
---
Affects Version/s: v0.4.0
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-
Michael Wu created EAGLE-383:
Summary: create scripts to facilitate release process
Key: EAGLE-383
URL: https://issues.apache.org/jira/browse/EAGLE-383
Project: Eagle
Issue Type: Task
Hi all,
Voting is now closed and has passed with the following tally:
- PPMC +1: Julian Hyde, Hao Chen, Edward Zhang, Qinwen Zhao (sum: 4)
- Others +1: Huizhi Lu (sum: 1)
A vote will now be called on gene...@incubator.apache.org. Thank you all
for voting for this release candidate.
Michael
u, Huizhi <h...@ebay.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
> > > * Signature checked, md5, sha1 verified
> > > * Apache rat:check passed (mvn apache-rat:check)
>
> * Ran rat:check and passed
>
> - Hao
>
> On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi <h...@ebay.com> wrote:
>
> > +1 (non-binding)
> >
> > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
> > * Signature checked, md5, sh
i <h...@ebay.com> wrote:
> +1 (non-binding)
>
> * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
> * Signature checked, md5, sha1 verified
> * Apache rat:check passed (mvn apache-rat:check)
> * Release matches tag.
>
>
> -Huizhi
>
>
+1 (non-binding)
* Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
* Signature checked, md5, sha1 verified
* Apache rat:check passed (mvn apache-rat:check)
* Release matches tag.
-Huizhi
> On Jul 11, 2016, at 2:40 AM, Michael Wu <mchl@gmail.com> wrote
+1 (non-binding)
* Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
* Signature checked, md5, sha1 verified
* Apache rat:check passed (mvn apache-rat:check)
* Release matches tag.
-Huizhi
> On Jul 11, 2016, at 2:40 AM, Michael Wu <mchl@gmail.com> wrote
Downloaded, checked license, notice, signatures, built on OS X JDK 1.7.
Checked that the JARs have gone.
+1 (binding)
Julian
> On Jul 11, 2016, at 2:40 AM, Michael Wu <mchl@gmail.com> wrote:
>
> Hi all,
>
> This is a release vote for Apache Eagle, version 0.4.
Hi all,
This is a release vote for Apache Eagle, version 0.4.0-incubating, release
candidate 3.
Highlighted changes in this release are as the following:
* JBDC Metadata Storage Extension
* Topology management in remote mode including start/stop/status
operations
* Auditlogparser
[
https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu closed EAGLE-367.
Resolution: Done
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-
://github.com/apache/incubator-eagle/pull/259
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356
> ---
>
> Key: EAGLE-367
> URL: https://issues.apache.org/jira/b
://github.com/apache/incubator-eagle/pull/259
LGTM
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356
> ---
>
> Key: EAGLE-367
> URL: https://issues.apache.
ff82a5413529ac0764a5196285d5a2a392244350
Author: anyway1021 <m...@apache.org>
Date: 2016-07-11T07:15:57Z
update CHANGELOG.txt appending bugs: EAGLE-355, EAGLE-356
> update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and
Michael Wu created EAGLE-367:
Summary: update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355
and EAGLE-356
Key: EAGLE-367
URL: https://issues.apache.org/jira/browse/EAGLE-367
Project: Eagle
Hi all,
In order not to bring adverse impact to those who continuously contribute
upon branch "branch-0.4", and also for the sake of fixing issues found in
voting of apache-eagle-0.4.0-incubating-rc2, I've just created new release
branch "branch-0.4.0" for upcoming 0.4.
Github user anyway1021 closed the pull request at:
https://github.com/apache/incubator-eagle/pull/258
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user anyway1021 commented on the issue:
https://github.com/apache/incubator-eagle/pull/258
I totally agree with you, let me close this PR and have a try.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user haoch commented on the issue:
https://github.com/apache/incubator-eagle/pull/258
In fact, I prefer to keep this jar in source code, but remove from built
package only, how do you think?
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user anyway1021 opened a pull request:
https://github.com/apache/incubator-eagle/pull/258
Eagle 365 solve issues found in release vote for 0.4.0-incubating-rc2
Delete depended .jar files.
You can merge this pull request into a Git repository by running:
$ git pull https
, on 1 hand not
> blocking future maven builds, on the other hand can make it satisfy
> apache's release policy. Currently, I'm still not sure if it may bring many
> additional efforts, but customer friendly seems very important to a project.
>
> So, could you give some details on how mu
Hi all,
Voting for the release of Apache Eagle 0.4.0-incubating (Release Candidate
2) has been cancelled because of having the following issues:
1. jar files exist in source.
Sorry for the inappropriate RC2, thank you to everyone who voted. I'll fix
the issue and create RC3 for voting in dev
Hi all,
Voting for the release of Apache Eagle 0.4.0-incubating (Release Candidate
1) has been cancelled because of having the following issues:
1. The extracted directory name is inappropriate, with "rc" inside.
2. CHANGELOG first line doesn't meet branding guidelines, and it does
Simply reply to the original VOTE thread prefix the subject with [CANCEL]
In the body of the reply, just add comments that the VOTE is cancelled due
to exe files found as release artifacts.
On Sat, Jul 9, 2016 at 12:48 AM, Liangfei.Su <suliang...@gmail.com> wrote:
> Mike,
>
> I
Hi Julian,
I'd say, it's the quality of the release that is more important than
anything else. As you mentioned, I'll bring another discussion for this
issue. BTW, could you let me know if I have to send a result email of the 2
rejected RC to cancel the VOTE? Thanks.
Michael
On Sat, Jul 9, 2016
e has dependencies.
Regards
Hemanth
On 7/7/16, 11:30 PM, "Michael Wu" <mchl@gmail.com> wrote:
>@ Hemanth,
>
>Did you mean to directly remove the eagle-assembly/src/main/lib/tomcat
>directory before packaging the source? I saw the directory removed in
>0.3.0-incu
/7/16, 7:59 PM, "Hao Chen" <h...@apache.org> wrote:
>+1 (binding) for release this Apache Eagle (Incubating) Version
>0.4.0-incubating Release Candidate 2
>
>* Built successfully on java version "1.7.0_75", OS X 10.10.5
>* Checked license, notice, signature
d5, sha1 verified (
> > > > https://httpd.apache.org/dev/verification.html)
> > > > * Apache rat:check passed (mvn apache-rat:check)
> > > >
> > > > * Commit and tag matched
> > > >
> > > >
> > > > Thanks
> > &g
ache rat:check passed (mvn apache-rat:check)
> > >
> > > * Commit and tag matched
> > >
> > >
> > > Thanks
> > >
> > > Edward
> > >
> > > On Tue, Jul 5, 2016 at 11:04 PM, Michael Wu <mchl@gmail.com>
> wrot
+1 (binding) for release this Apache Eagle (Incubating) Version
0.4.0-incubating Release Candidate 2
* Built successfully on java version "1.7.0_75", OS X 10.10.5
* Checked license, notice, signatures, especially CHANGELOG.txt covering
all released versions' changes.
* Apache-rat:ch
passed (mvn apache-rat:check)
> >
> > * Commit and tag matched
> >
> >
> > Thanks
> >
> > Edward
> >
> > On Tue, Jul 5, 2016 at 11:04 PM, Michael Wu <mchl@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> This
ture checked, md5, sha1 verified (
> https://httpd.apache.org/dev/verification.html)
> * Apache rat:check passed (mvn apache-rat:check)
>
> * Commit and tag matched
>
>
> Thanks
>
> Edward
>
> On Tue, Jul 5, 2016 at 11:04 PM, Michael Wu <mchl@gmail.com> wrote:
>
+1 (non-binding)
* Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
* Signature checked, md5, sha1 verified
* Apache rat:check passed
* Release matches tag.
Nice release!
-Huizhi
> On Jul 5, 2016, at 11:04 PM, Michael Wu <mchl@gmail.com> wrote
S X
> * Checked license, notice, signatures
> * Ran apache-rat:check, and it passed
> * Checked that release matches tag at github
>
> * I saw you added ‘brew install node’ to README.md - thanks!
> * I saw that CHANGELOG.txt now contains previous releases — good idea
> * I saw
+1 (binding)
* Downloaded & built successfully on JDK 1.7 OS X
* Checked license, notice, signatures
* Ran apache-rat:check, and it passed
* Checked that release matches tag at github
* I saw you added ‘brew install node’ to README.md - thanks!
* I saw that CHANGELOG.txt now contains prev
Hi all,
This is a release vote for Apache Eagle, version 0.4.0-incubating, release
candidate 2.
Highlighted changes in this release are as the following:
* JBDC Metadata Storage Extension
* Topology management in remote mode including start/stop/status
operations
* Auditlogparser
[
https://issues.apache.org/jira/browse/EAGLE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu closed EAGLE-352.
Resolution: Done
> Fix found issues on release-0.4.0-rc1 and create
> On Thu, Jun 30, 2016 at 3:56 PM, Henry Saputra <henry.sapu...@gmail.com>
> > wrote:
> >
> > > Putting the KEYS in dis folder is used to verify the signature of the
> > > release artifacts.
> > >
> > > I think it is more used for convenience since Eagle alre
bating" is the actual *version*, and why is there "incubator"
> in
> > the name?
> >
> > BTW: why do you erase content of previous release versions in
> > CHANGELOG.txt but just keep v0.4.0's ? I think the CHANGELOG.txt should
> > track all historical changes in
Michael,
As we already agreed referring to previous releasing, please use "Apache
Eagle x.y.z-incubating" where "Apache Eagle" is *product name* and
"x.y.z-incubating" is the actual *version*, and why is there "incubator" in
the name?
BTW: why do you er
“Apache" has to be present, and so does “incubating”, and your version number
should not start with “v". As for the order of words, I did a search[1] for
recent releases and there’s no clear standard:
* Apache Taverna Command-line 3.1.0-incubating
* Apache Trafodion (incubating) rel
is there any place that automatically sync the
> keys to groups, please? Thanks!
>
> Michael
>
> On Thu, Jun 30, 2016 at 3:56 PM, Henry Saputra <henry.sapu...@gmail.com>
> wrote:
>
> > Putting the KEYS in dis folder is used to verify the signature of the
>
Michael Wu created EAGLE-352:
Summary: Fix found issues on release-0.4.0-rc1 and create rc2
Key: EAGLE-352
URL: https://issues.apache.org/jira/browse/EAGLE-352
Project: Eagle
Issue Type: Task
sed by brackets), am I correct?
Next, I'll change the dir name inside the tar, modify release note
head-line, highlight the building requirement of npm in README.md, add
LICENSE to asf_logo.svg, they could be done shortly. As to branding issues,
it may take some time to detect and change all the cl
Downloaded, built successfully using JDK 1.7 on OS X. Checked signatures,
license, notice.
The directory inside the tar file is called
apache-eagle-0.4.0-incubating-src-rc1. I would name it
apache-eagle-0.4.0-incubating-src, because when it is released it will be a
release, not a release
; Putting the KEYS in dis folder is used to verify the signature of the
> release artifacts.
>
> I think it is more used for convenience since Eagle already have group sig
> file at https://people.apache.org/keys/group/eagle.asc
>
> - Henry
>
> On Thu, Jun 30, 2016 at 1:55 PM, Mich
Hi all,
This is a release vote for Apache Incubator Eagle, version 0.4.0, release
candidate 1.
Highlighted changes in this release are as the following:
* JBDC Metadata Storage Extension
* Topology management in remote mode including start/stop/status
operations
* Auditlogparser for MapR's
Putting the KEYS in dis folder is used to verify the signature of the
release artifacts.
I think it is more used for convenience since Eagle already have group sig
file at https://people.apache.org/keys/group/eagle.asc
- Henry
On Thu, Jun 30, 2016 at 1:55 PM, Michael Wu <mchl@gmail.
Hi Hemanth,
Reading your WIKI of release process, I've merged my gpg-pub-key into KEYS
file, and have committed it to svn, which is visible at
http://www.apache.org/dist/incubator/eagle/.
However, I got confused on step-14 at below fragment, see:
*
..
Once this file has
Github user anyway1021 commented on the issue:
https://github.com/apache/incubator-eagle/pull/243
rebase to involve new commits coming after this PR is opened.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user anyway1021 commented on the issue:
https://github.com/apache/incubator-eagle/pull/243
@julianhyde , no, the changes of this PR is not made by
maven-release-plugin. I was using maven-version-plugin to erase the -SNAPSHOT
suffix.
Actually I'm researching maven
Github user julianhyde commented on the issue:
https://github.com/apache/incubator-eagle/pull/243
Are you using maven-release-plugin? (Actually it's inherited from the
Apache parent POM.)
It is able to update versions in all your pom.xml files automatically,
removing
[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Zhang updated EAGLE-233:
---
Fix Version/s: (was: v0.4.0)
v0.5.0
> Integrate [maven-release-plu
Hi team,
As we are approaching the v0.4 release time, we still have 20+ tickets that
target at v0.4.0 and remain "open" status. They block us to create
elaborate release note.
I've created a jira filter unresolved tickets
<https://issues.apache.org/jira/issues/?jql=project%20%3D%
Hi team,
As we are approaching the v0.4 release time, we still have 18 tickets that
target at v0.4.0 and remain "open" status. They block us to create
elaborate release note.
I've created a jira filter unresolved tickets
<https://issues.apache.org/jira/issues/?filter=12335967>
+1 for thinking about minor release.
Frequent releases are usually good for any software. With first release
done and all license issues resolved, the upcoming releases should be
smooth.
For incubating project you have overhead of a week for voting (both dev and
incubator list), but would become
[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-233:
---
Labels: development tools (was: tools)
> Integrate [maven-release-plugin] for eagle rele
[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-233:
---
Labels: tools (was: )
> Integrate [maven-release-plugin] for eagle rele
[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen reassigned EAGLE-233:
--
Assignee: Hao Chen (was: Michael Wu)
> Integrate [maven-release-plugin] for eagle rele
ven-release-plugin] for eagle release
> --
>
> Key: EAGLE-233
> URL: https://issues.apache.org/jira/browse/EAGLE-233
> Project: Eagle
> Issue Type: New Feature
>
[
https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-233:
---
Assignee: Michael Wu (was: Hao Chen)
> Integrate [maven-release-plugin] for eagle rele
Hao Chen created EAGLE-233:
--
Summary: Integrate [maven-release-plugin] for eagle release
Key: EAGLE-233
URL: https://issues.apache.org/jira/browse/EAGLE-233
Project: Eagle
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/EAGLE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu resolved EAGLE-143.
---
Resolution: Fixed
> Create Eagle release 0.
hread) listing all
> votes. Is there anyway to show this ?
>
> Regards
> Hemanth
>
>
>
>
> On 3/28/16, 12:18 PM, "Julian Hyde" <jh...@apache.org
> <mailto:jh...@apache.org>> wrote:
>
>> (Changed subject; was: "Re: [RESULT][VOTE]
Hyde" <jh...@apache.org> wrote:
>(Changed subject; was: "Re: [RESULT][VOTE] Release Eagle Incubating Version
>0.3.0(RC3)”.)
>
>Remember, the vote period is a *minimum* of 72 hours to give everyone ample
>time to review. It doesn’t matter if you receive 3 +1 votes
Thanks all, I am coming late for reviewing the release artifacts.
I will run my VOTE in general@ list instead.
Please forward the VOTE to general@ list incubator.
- Henry
On Mon, Mar 28, 2016 at 8:40 AM, Dendukuri, Hemanth <hdenduk...@ebay.com>
wrote:
> Voting is now closed and t
few
>hours, provided they are in the period.
>
>> On Mar 26, 2016, at 10:59 AM, Dendukuri, Hemanth <hdenduk...@ebay.com> wrote:
>>
>> The voting for "Apache Eagle, 0.3.0 Release Candidate 3" passed with 3
>> binding +1 votes from the Incubator PMC members and
this bug.
> > >
> > >
> > >Thanks
> > >
> > >Edward
> > >
> > >On Thu, Mar 24, 2016 at 10:29 AM, Dendukuri, Hemanth <
> hdenduk...@ebay.com
> > >
> > >wrote:
> > >
> > >> Hi all,
> > &
; >
> >
> >Thanks
> >
> >Edward
> >
> >On Thu, Mar 24, 2016 at 10:29 AM, Dendukuri, Hemanth <hdenduk...@ebay.com
> >
> >wrote:
> >
> >> Hi all,
> >>
> >>
> >>This is the incubator release of Apache Ea
common.TestDateTimeUtil)” fails.Looks that is
>because of timezone issue, I will fix this bug.
>
>
>Thanks
>
>Edward
>
>On Thu, Mar 24, 2016 at 10:29 AM, Dendukuri, Hemanth <hdenduk...@ebay.com>
>wrote:
>
>> Hi all,
>>
>>
>>This
duk...@ebay.com>
wrote:
> Hi all,
>
>
>This is the incubator release of Apache Eagle, 0.3.0 Release
> Candidate 3.
>
>We fixed all comments.
>
>Thanks to everyone who has contributed to this release.
>
>Here’s release notes:
>
> The voting for "Apache Eagle, 0.3.0 Release Candidate 3" passed with 3
> binding +1 votes from the Incubator PMC members and One +1 VOTE from apache
> contributor. There are no 0 or -1 votes.
>
> Votes:
> +1 Julian Hyde(binding)
> +1 amareshwarisr(binding)
The voting for "Apache Eagle, 0.3.0 Release Candidate 3" passed with 3 binding
+1 votes from the Incubator PMC members and One +1 VOTE from apache
contributor. There are no 0 or -1 votes.
Votes:
+1 Julian Hyde(binding)
+1 amareshwarisr(binding)
+1 Hao Chen(binding)
+1 (Liangfei.Su
ature from "Hemanth Dendukuri (CODE SIGNING KEY) <
>>> hdenduk...@apache.org>"
>>>
>>> $ mvn clean install
>>> ...
>>> [INFO]
>>>
>>> [INFO] BUILD
--
>
> - Hao
>
> On Fri, Mar 25, 2016 at 1:29 AM, Dendukuri, Hemanth <hdenduk...@ebay.com>
> wrote:
>
> > Hi all,
> >
> >
> >This is the incubator release of Apache Eagle, 0.3.0 Release
> > Candidate 3.
> >
> >
Hi all,
This is the incubator release of Apache Eagle, 0.3.0 Release Candidate 3.
We fixed all comments.
Thanks to everyone who has contributed to this release.
Here’s release notes:
https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f
The Voting is closed. I already sent out details with subject “[CANCEL] [VOTE]
Release Eagle Incubating Version 0.3.0”
On 3/21/16, 12:36 PM, "Julian Hyde" <jh...@apache.org> wrote:
>Medha,
>
>Your ‘+1’ is ambiguous. I suspect that your ‘+1’ meant you agreed with
Medha,
Your ‘+1’ is ambiguous. I suspect that your ‘+1’ meant you agreed with Langfei
about modifying READ.me. But this is a vote thread, so your ‘+1’ could be
interpreted to mean that you approve of the release.
Eagle devs,
Vote threads are for voting only. If you need to have wider
> ok
> > > for me too.
> > >
> > > On Wed, Mar 16, 2016 at 2:52 AM, Hao Chen <h...@apache.org> wrote:
> > >
> > > > Amareshwari,
> > > >
> > > > 1) As to LICENSE, do you think my modification is ok here:
> > > >
ks
>Amareshwari
>On Wed, Mar 16, 2016 at 3:22 PM, Hao Chen <h...@apache.org> wrote:
>
>> Amareshwari,
>>
>> 1) As to LICENSE, do you think my modification is ok here:
>> https://github.com/haoch/incubator-eagle/blob/fix-release-v0.3.0/LICENSE?
>>
>&g
ents without fail.
>
>MD5, SHA1 and SHA512 matches. I think we should not keep other .sha file.
>
>Next release, I think you only need the .sha1 file; omit the .sha and .sha512
>files.
>
>Also, I'm not sure if you can add and drop files from directory once the vote
>is cal
> On Mar 16, 2016, at 1:36 AM, amareshwarisr . <amareshw...@gmail.com> wrote:
>
> - Unit tests failed, details below
I’ll state, for the record, that it’s OK make a release with unit tests that
fail. You just have to decide, as a community, that all unit tests passing
>
> > Julian already have statement on test. Just one note that unit test runs
> ok
> > for me too.
> >
> > On Wed, Mar 16, 2016 at 2:52 AM, Hao Chen <h...@apache.org> wrote:
> >
> > > Amareshwari,
> > >
> > > 1) As to LI
Julian already have statement on test. Just one note that unit test runs ok
for me too.
On Wed, Mar 16, 2016 at 2:52 AM, Hao Chen <h...@apache.org> wrote:
> Amareshwari,
>
> 1) As to LICENSE, do you think my modification is ok here:
> https://github.com/haoch/incubator-eagl
ll execute below comments without fail.
MD5, SHA1 and SHA512 matches. I think we should not keep other .sha file.
Next release, I think you only need the .sha1 file; omit the .sha and .sha512
files.
Also, I'm not sure if you can add and drop files from directory once the vote
is called out.
In
-archives.apache.org/mod_mbox/eagle-dev/201603.mbox/browser
Thank you to all who reviewed and voted
We will cancel this release candidate.
Regards,
Hemanth
On 3/14/16, 2:58 PM, "Dendukuri, Hemanth" <hdenduk...@ebay.com> wrote:
>Hi all,
>
>
> This is the incub
; >> >
> >> >eagle-external/eagle-ambari/lib/EAGLE/package/patches/app.js comes
> from?
> >> Although it is a text file, it is 1.7M lines long so I doubt
> >> >that you can call it "source code". Was it generated? Was it copied
> from
ource file headers :
> > > >
> > > >As per the doc :
> > > >
> > > >A file without any degree of creativity in either its literal elements
> > or
> > > >its structure is not protected by copyright law; therefore, such a
> fi
ements
> or
> > >its structure is not protected by copyright law; therefore, such a file
> > >does not require a license header
> > >
> > >So, should be fine. You might want to update your pom's rat check with
> > >
> > >
> > >
Responses inline.
On Wed, Mar 16, 2016 at 11:46 PM, Julian Hyde <jh...@apache.org> wrote:
>
> > On Mar 16, 2016, at 1:36 AM, amareshwarisr . <amareshw...@gmail.com>
> wrote:
> >
> > - Unit tests failed, details below
>
> I’ll state, for the record, t
Hemanth,
Could you please rebuild the latest package so that we could continue to
vote for the release?
Regards,
Hao
On Thu, Mar 17, 2016 at 10:38 AM, Jilin <smith3...@gmail.com> wrote:
> Yes. All the package in node_module is build by npm. They will not be
> included in eagle
; >
>> >eagle-external/eagle-ambari/lib/EAGLE/package/patches/app.js comes from?
>> Although it is a text file, it is 1.7M lines long so I doubt
>> >that you can call it "source code". Was it generated? Was it copied from
>> another project?
>> >
>>
) As to LICENSE, do you think my modification is ok here:
> https://github.com/haoch/incubator-eagle/blob/fix-release-v0.3.0/LICENSE?
>
> 2) As to missing source headers problems about some files like
> json/MANIFEST.MF
> which don't support comments for license header, how shoul
GitHub user haoch opened a pull request:
https://github.com/apache/incubator-eagle/pull/126
Fix release v0.3.0
* Remove kafka-python from top level license as it's under Apache License
877ca93
* Copy external license content for six,Google Fonts,AdminLTE e0529d4
completes.
On Tue, Mar 15, 2016 at 9:25 PM, amareshwarisr . <amareshw...@gmail.com> wrote:
> MD5, SHA1 and SHA512 matches. I think we should not keep other .sha file.
Next release, I think you only need the .sha1 file; omit the .sha and
.sha512 files.
> Also, I'm not sure if you can a
>
> > > >~$ sha1sum apache-eagle-0.3.0-incubating-src.tar.gz
> > > >852e296fd6a1bc6b81eff7126a658683489ef104
> > > >apache-eagle-0.3.0-incubating-src.tar.gz
> > > >~$ shasum apache-eagle-0.3.0-incubating-src.tar.gz
> > > >852e296fd6a1bc6b
1 - 100 of 140 matches
Mail list logo
