[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

[Yanhui Zhao (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144735#comment-16144735
 ] 

Yanhui Zhao commented on MNEMONIC-304:
--

Support has been implemented. Verified that built is successful and current 
test case can pass. Sending pull request for peer review. Thanks.

> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144732#comment-16144732
 ] 

ASF GitHub Bot commented on MNEMONIC-304:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/62

MNEMONIC-304 Add suppot for Pair to ParameterHolder class

Some test cases need to pass Pair as parameters when creating durable 
class. Current ParameterHolder class doesn't have the support for this feature.

Build is successful and test case passed after ParameterHolder class is 
updated. Please review and help to double check. Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #62


commit c9812eec2e949d73540e6356bf1b091ef9c220d4
Author: Yanhui Zhao 
Date:   2017-08-29T04:28:04Z

MNEMONIC-304 Add suppot for Pair to ParameterHolder class




> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-mnemonic pull request #62: MNEMONIC-304 Add suppot for Pair to Par...

[yzz127]

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/62

MNEMONIC-304 Add suppot for Pair to ParameterHolder class

Some test cases need to pass Pair as parameters when creating durable 
class. Current ParameterHolder class doesn't have the support for this feature.

Build is successful and test case passed after ParameterHolder class is 
updated. Please review and help to double check. Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #62


commit c9812eec2e949d73540e6356bf1b091ef9c220d4
Author: Yanhui Zhao 
Date:   2017-08-29T04:28:04Z

MNEMONIC-304 Add suppot for Pair to ParameterHolder class




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (MNEMONIC-353) Assign fixed version number to docker Centos build

[Yanhui Zhao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yanhui Zhao closed MNEMONIC-353.

Resolution: Fixed

Issue is fixed. Ticket closed.

> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144702#comment-16144702
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/61


> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144691#comment-16144691
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

GitHub user yzz127 reopened a pull request:

https://github.com/apache/incubator-mnemonic/pull/61

MNEMONIC-353 Assign fixed version number to docker Centos build

Assign a version number instead of "latest" for docker Centos build for 
compatibility concerns.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #61


commit 529ae4ea59d65d0a5002847449e2342ca1a40516
Author: Yanhui Zhao 
Date:   2017-08-27T03:24:09Z

MNEMONIC-353 Assign fixed version number to docker Centos build




> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144690#comment-16144690
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

Github user yzz127 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/61


> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-mnemonic pull request #61: MNEMONIC-353 Assign fixed version numbe...

[yzz127]

GitHub user yzz127 reopened a pull request:

https://github.com/apache/incubator-mnemonic/pull/61

MNEMONIC-353 Assign fixed version number to docker Centos build

Assign a version number instead of "latest" for docker Centos build for 
compatibility concerns.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #61


commit 529ae4ea59d65d0a5002847449e2342ca1a40516
Author: Yanhui Zhao 
Date:   2017-08-27T03:24:09Z

MNEMONIC-353 Assign fixed version number to docker Centos build




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-mnemonic pull request #61: MNEMONIC-353 Assign fixed version numbe...

[yzz127]

Github user yzz127 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/61


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (MNEMONIC-354) asf-site build script lacks information that causing confusions when uploading

[Yanhui Zhao (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144683#comment-16144683
 ] 

Yanhui Zhao commented on MNEMONIC-354:
--

Verified that this issue has been fixed. Ticket closed. Thanks

> asf-site build script lacks information that causing confusions when uploading
> --
>
> Key: MNEMONIC-354
> URL: https://issues.apache.org/jira/browse/MNEMONIC-354
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Wang, Gang
>Priority: Critical
> Fix For: 0.9.0-incubating
>
> Attachments: 
> 0001-MNEMONIC-354-asf-site-build-script-lacks-information.patch
>
>
> Build.md lacks following info: "git branch asf-site origin/asf-site", which 
> is causing confusions to build and upload the website.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-354) asf-site build script lacks information that causing confusions when uploading

[Yanhui Zhao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yanhui Zhao closed MNEMONIC-354.

Resolution: Fixed

Ticket closed.

> asf-site build script lacks information that causing confusions when uploading
> --
>
> Key: MNEMONIC-354
> URL: https://issues.apache.org/jira/browse/MNEMONIC-354
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Wang, Gang
>Priority: Critical
> Fix For: 0.9.0-incubating
>
> Attachments: 
> 0001-MNEMONIC-354-asf-site-build-script-lacks-information.patch
>
>
> Build.md lacks following info: "git branch asf-site origin/asf-site", which 
> is causing confusions to build and upload the website.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] Graduation?

[Gang(Gary) Wang]

Yes, I also totally agree this and we will try our best for the readiness
for the graduation.

For the suggestion that John advised, we have prepared the following
comments for your review, Thanks!

*CD20 - You have a link in your header called GITHUB that brought me to
your source code.  Other projects use hacking guides.  Unless you're on
gitbox, the git primary repo should be the ASF hosted repos.*

The github link has been removed from CD20 and using
http://mnemonic.incubator.apache.org/develop/ as the link of website. we
also create ticket MNEMONIC-355 (resolved) to remove Github link from
navigator menu on website.

*CD30 - The usage of docker is in of itself a violation of this item, from
my point of view.  In your case, you're pointing to "centos:latest" which
today is C7.2, but in a few months will be C7.3.*

Yes, we will fix it through Apache Jira MNEMONIC-353(reviewed) and
MNEMONIC-356(WIP)

*CD50 - I can't tell if the pull requests to your repo are from committers
or from contributors.  If I take
https://github.com/apache/incubator-mnemonic/pull/60
 as an example, the
commit message says nothing about provenance of the source code.*

We have requested to revoke all stalled PRs, and all commit messages must
contain Apache JIRA number and title.

*LC50 - You mention in your response why this is incorrect (the use of
*most*)*

Yes we will correct it with "The files in the project source repository
have appropriate headers", The files under target/ that generated by mvn
building process would be excluded and all other project files have been
properly licensed and guarded by RAT plugin.

*RE10 - You link to http://mnemonic.incubator.apache.org/news/
 but that doesn't include any
download links.  http://mnemonic.incubator.apache.org/downloads/
 does include download
links to the proper release mirrors.*

That has been corrected by replacing it with the link
http://mnemonic.incubator.apache.org/downloads/

*RE20 - You mention non-PMC members in the vote (PPMC).*

Yes, we started with the community vote for releasing and the result
explicitly shows binding and non-binding votes.

*RE30 - Again, not using mirror.*

Looks no mirror link in this field.

*RE40 - Correct answer would be "NO. We do not distribute binary releases."*

Yes it is and corrected

*RE50 - Your release process neglects deleting old artifacts.*

Sorry I forgot it and corrected it by the Apache Jira ticket MNEMONIC-357
(resolved) as well as MNEMONIC-358 (resolved)

*QU10 - Code quality is more than bug reports.  You may want to use
linters, sonar, etc.*

Yes, we will investigate this plugin and apply them to project later, as
for now, the QU10 has been replaced with "YES. The project records all bugs
in the Apache’s JIRA issue tracker. Developer also uses Eclipse or Intellij
IDEA to improve their code quality."

*QU20 - This is only achievable if you've had a security vulnerability
reported.  If you haven't had one reported, there's no way to confirm this.*

The QU20 has been replaced with "YES. Security issues would be treated with
the highest priority, computing service and memory service are separated
from other modules and defined by interfaces, so security concerns could be
largely mitigated by introduced this design at first place.", that this
emphasize we consider the security aspect from design viewpoint as well.

*QU50 - I see that MNEMONIC-203/217 have been open for around 6 months.*

We have asked owners to properly handle those tickets

*CO10 - Github shows two pull requests open without any commentary or
questions from the project's committers.  Why is that?*

They are stalled PRs, we have asked the owner to properly revoke them.

*The full checklist as follows for you to add comments*
https://docs.google.com/document/d/10LKTjPMceV4s4MrSRIA9L8pg7jLFp-ec-TmW96mZbXM/edit?usp=sharing

Very truly yours
Gary





On Mon, Aug 28, 2017 at 2:25 PM, John D. Ament 
wrote:

> Huge +1 to that.
>
> On Mon, Aug 28, 2017 at 5:18 PM Henry Saputra 
> wrote:
>
> > The "checklist" suppose to just provide guide for readiness our
> > graduation. It was NOT mandatory checklist.
> >
> > This should be used primarily for self check to make sure we are ready
> for
> > graduation.
> >
> >
> > - Henry
> >
> > On Fri, Aug 25, 2017 at 7:50 PM, John D. Ament 
> > wrote:
> >
> >> Hello,
> >>
> >> So first, I'll say its always great to see a podling aim to graduate.
> Its
> >> not up to me to measure whether the podling has been successful or not,
> >> but
> >> instead the IPMC as a whole.  I can give you some feedback on the APMM
> >> assessment, but I'll point out that I'm not a fan of this form and
> >> completing this form is not a requirement for graduation.
> >>
> >> So please, when reviewing the below list, understand that 

[jira] [Resolved] (MNEMONIC-358) Missing update website step in Wiki release guide

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang resolved MNEMONIC-358.
-
   Resolution: Fixed
Fix Version/s: 0.9.0-incubating

> Missing update website step in Wiki release guide
> -
>
> Key: MNEMONIC-358
> URL: https://issues.apache.org/jira/browse/MNEMONIC-358
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Release, Wiki
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNEMONIC-358) Missing update website step in Wiki release guide

[Wang, Gang (JIRA)]

Wang, Gang created MNEMONIC-358:
---

 Summary: Missing update website step in Wiki release guide
 Key: MNEMONIC-358
 URL: https://issues.apache.org/jira/browse/MNEMONIC-358
 Project: Mnemonic
  Issue Type: Bug
  Components: Release, Wiki
Affects Versions: 0.9.0-incubating
Reporter: Wang, Gang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MNEMONIC-358) Missing update website step in Wiki release guide

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang reassigned MNEMONIC-358:
---

Assignee: Wang, Gang

> Missing update website step in Wiki release guide
> -
>
> Key: MNEMONIC-358
> URL: https://issues.apache.org/jira/browse/MNEMONIC-358
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Release, Wiki
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MNEMONIC-357) Missing Cleanup step in Wiki Release guide

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang resolved MNEMONIC-357.
-
   Resolution: Fixed
Fix Version/s: 0.9.0-incubating

> Missing Cleanup step in Wiki Release guide
> --
>
> Key: MNEMONIC-357
> URL: https://issues.apache.org/jira/browse/MNEMONIC-357
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Wiki
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> The Dist repository needs to be cleaned up after releasing a new version, all 
> release candidates should be removed from stage trunk and all previous 
> version also should be removed from release trunk. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MNEMONIC-357) Missing Cleanup step in Wiki Release guide

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang reassigned MNEMONIC-357:
---

Assignee: Wang, Gang

> Missing Cleanup step in Wiki Release guide
> --
>
> Key: MNEMONIC-357
> URL: https://issues.apache.org/jira/browse/MNEMONIC-357
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Wiki
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
>
> The Dist repository needs to be cleaned up after releasing a new version, all 
> release candidates should be removed from stage trunk and all previous 
> version also should be removed from release trunk. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNEMONIC-357) Missing Cleanup step in Wiki Release guide

[Wang, Gang (JIRA)]

Wang, Gang created MNEMONIC-357:
---

 Summary: Missing Cleanup step in Wiki Release guide
 Key: MNEMONIC-357
 URL: https://issues.apache.org/jira/browse/MNEMONIC-357
 Project: Mnemonic
  Issue Type: Bug
  Components: Wiki
Affects Versions: 0.9.0-incubating
Reporter: Wang, Gang


The Dist repository needs to be cleaned up after releasing a new version, all 
release candidates should be removed from stage trunk and all previous version 
also should be removed from release trunk. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] Graduation?

[John D. Ament]

Huge +1 to that.

On Mon, Aug 28, 2017 at 5:18 PM Henry Saputra 
wrote:

> The "checklist" suppose to just provide guide for readiness our
> graduation. It was NOT mandatory checklist.
>
> This should be used primarily for self check to make sure we are ready for
> graduation.
>
>
> - Henry
>
> On Fri, Aug 25, 2017 at 7:50 PM, John D. Ament 
> wrote:
>
>> Hello,
>>
>> So first, I'll say its always great to see a podling aim to graduate.  Its
>> not up to me to measure whether the podling has been successful or not,
>> but
>> instead the IPMC as a whole.  I can give you some feedback on the APMM
>> assessment, but I'll point out that I'm not a fan of this form and
>> completing this form is not a requirement for graduation.
>>
>> So please, when reviewing the below list, understand that completing this
>> is not a requirement for graduation.  Even then, podlings who think they
>> pass it may be missing things.
>>
>> CD20 - You have a link in your header called GITHUB that brought me to
>> your
>> source code.  Other projects use hacking guides.  Unless you're on gitbox,
>> the git primary repo should be the ASF hosted repos.
>>
>> CD30 - The usage of docker is in of itself a violation of this item, from
>> my point of view.  In your case, you're pointing to "centos:latest" which
>> today is C7.2, but in a few months will be C7.3.
>>
>> CD50 - I can't tell if the pull requests to your repo are from committers
>> or from contributors.  If I take
>> https://github.com/apache/incubator-mnemonic/pull/60 as an example, the
>> commit message says nothing about provenance of the source code.
>>
>> LC50 - You mention in your response why this is incorrect (the use of
>> *most*)
>>
>> RE10 - You link to http://mnemonic.incubator.apache.org/news/ but that
>> doesn't include any download links.
>> http://mnemonic.incubator.apache.org/downloads/ does include download
>> links
>> to the proper release mirrors.
>>
>> RE20 - You mention non-PMC members in the vote (PPMC).
>>
>> RE30 - Again, not using mirror.
>>
>> RE40 - Correct answer would be "NO. We do not distribute binary releases."
>>
>> RE50 - Your release process neglects deleting old artifacts.
>>
>> QU10 - Code quality is more than bug reports.  You may want to use
>> linters,
>> sonar, etc.
>>
>> QU20 - This is only achievable if you've had a security vulnerability
>> reported.  If you haven't had one reported, there's no way to confirm
>> this.
>>
>> QU50 - I see that MNEMONIC-203/217 have been open for around 6 months.
>>
>> CO10 - Github shows two pull requests open without any commentary or
>> questions from the project's committers.  Why is that?
>>
>> Regards,
>>
>> John
>>
>> On Fri, Aug 25, 2017 at 3:00 PM Gang(Gary) Wang  wrote:
>>
>> > Hi John, Our Mentors and PPMCs
>> >
>> > We have prepared Apache Maturity checklist for your evaluation, please
>> > guide us to graduate our project, thanks.
>> >
>> > All comments and suggestions are welcome!
>> >
>> > Cheers!
>> > Gary
>> >
>> >
>> > On Thu, Aug 17, 2017 at 1:31 PM, Gang(Gary) Wang 
>> wrote:
>> >
>> >> Hi John
>> >>
>> >> Fixed it, Thank you for reminding me
>> >>
>> >> Very truly yours
>> >> Gary
>> >>
>> >>
>> >> On Thu, Aug 17, 2017 at 12:39 PM, John D. Ament > >
>> >> wrote:
>> >>
>> >>> Please take a look at
>> >>> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/
>> >>>
>> >>>
>> >>> On Thu, Aug 17, 2017 at 1:55 PM Gang(Gary) Wang 
>> >>> wrote:
>> >>>
>>  Hi John
>> 
>>  This issue has been fixed please refresh your browser and then review
>>  it, Thanks!
>> 
>>  Very truly yours
>>  Gary
>> 
>> 
>>  On Thu, Aug 17, 2017 at 10:33 AM, Gang(Gary) Wang 
>>  wrote:
>> 
>> > Hi John
>> >
>> > I didn't realize that and thank you very much for pointing it out,
>> we
>> > will correct this according to your guidance.
>> >
>> > Thanks!
>> > Very truly yours
>> > Gary
>> >
>> >
>> > On Thu, Aug 17, 2017 at 4:54 AM, John D. Ament <
>> johndam...@apache.org>
>> > wrote:
>> >
>> >> Thanks, but you're still out of compliance.
>> >>
>> >> - You're linking directly to your un-mirrored artifacts, but you
>> >> should be linking to your mirrored artifacts.
>> >> - You have not cleaned up your old releases, your old releases
>> should
>> >> be archived.
>> >>
>> >> Now here's the catch - we require mirroring but I can't find
>> anything
>> >> saying what the mirroring URL is.  The format is going to be
>> >> http://apache.org/dyn/closer.cgi/incubator/mnemonic and you'll
>> want
>> >> to grab your specific version from there.
>> >>
>> >> John
>> >>
>> >>
>> >>
>> >> On Wed, Aug 16, 2017 at 9:31 PM Gang(Gary) Wang 
>> >> wrote:
>> >>
>> >>> Hi John,
>> >>>
>> 

Re: [DISCUSS] Graduation?

[Henry Saputra]

The "checklist" suppose to just provide guide for readiness our graduation.
It was NOT mandatory checklist.

This should be used primarily for self check to make sure we are ready for
graduation.


- Henry

On Fri, Aug 25, 2017 at 7:50 PM, John D. Ament 
wrote:

> Hello,
>
> So first, I'll say its always great to see a podling aim to graduate.  Its
> not up to me to measure whether the podling has been successful or not, but
> instead the IPMC as a whole.  I can give you some feedback on the APMM
> assessment, but I'll point out that I'm not a fan of this form and
> completing this form is not a requirement for graduation.
>
> So please, when reviewing the below list, understand that completing this
> is not a requirement for graduation.  Even then, podlings who think they
> pass it may be missing things.
>
> CD20 - You have a link in your header called GITHUB that brought me to your
> source code.  Other projects use hacking guides.  Unless you're on gitbox,
> the git primary repo should be the ASF hosted repos.
>
> CD30 - The usage of docker is in of itself a violation of this item, from
> my point of view.  In your case, you're pointing to "centos:latest" which
> today is C7.2, but in a few months will be C7.3.
>
> CD50 - I can't tell if the pull requests to your repo are from committers
> or from contributors.  If I take
> https://github.com/apache/incubator-mnemonic/pull/60 as an example, the
> commit message says nothing about provenance of the source code.
>
> LC50 - You mention in your response why this is incorrect (the use of
> *most*)
>
> RE10 - You link to http://mnemonic.incubator.apache.org/news/ but that
> doesn't include any download links.
> http://mnemonic.incubator.apache.org/downloads/ does include download
> links
> to the proper release mirrors.
>
> RE20 - You mention non-PMC members in the vote (PPMC).
>
> RE30 - Again, not using mirror.
>
> RE40 - Correct answer would be "NO. We do not distribute binary releases."
>
> RE50 - Your release process neglects deleting old artifacts.
>
> QU10 - Code quality is more than bug reports.  You may want to use linters,
> sonar, etc.
>
> QU20 - This is only achievable if you've had a security vulnerability
> reported.  If you haven't had one reported, there's no way to confirm this.
>
> QU50 - I see that MNEMONIC-203/217 have been open for around 6 months.
>
> CO10 - Github shows two pull requests open without any commentary or
> questions from the project's committers.  Why is that?
>
> Regards,
>
> John
>
> On Fri, Aug 25, 2017 at 3:00 PM Gang(Gary) Wang  wrote:
>
> > Hi John, Our Mentors and PPMCs
> >
> > We have prepared Apache Maturity checklist for your evaluation, please
> > guide us to graduate our project, thanks.
> >
> > All comments and suggestions are welcome!
> >
> > Cheers!
> > Gary
> >
> >
> > On Thu, Aug 17, 2017 at 1:31 PM, Gang(Gary) Wang 
> wrote:
> >
> >> Hi John
> >>
> >> Fixed it, Thank you for reminding me
> >>
> >> Very truly yours
> >> Gary
> >>
> >>
> >> On Thu, Aug 17, 2017 at 12:39 PM, John D. Ament 
> >> wrote:
> >>
> >>> Please take a look at
> >>> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/
> >>>
> >>>
> >>> On Thu, Aug 17, 2017 at 1:55 PM Gang(Gary) Wang 
> >>> wrote:
> >>>
>  Hi John
> 
>  This issue has been fixed please refresh your browser and then review
>  it, Thanks!
> 
>  Very truly yours
>  Gary
> 
> 
>  On Thu, Aug 17, 2017 at 10:33 AM, Gang(Gary) Wang 
>  wrote:
> 
> > Hi John
> >
> > I didn't realize that and thank you very much for pointing it out, we
> > will correct this according to your guidance.
> >
> > Thanks!
> > Very truly yours
> > Gary
> >
> >
> > On Thu, Aug 17, 2017 at 4:54 AM, John D. Ament <
> johndam...@apache.org>
> > wrote:
> >
> >> Thanks, but you're still out of compliance.
> >>
> >> - You're linking directly to your un-mirrored artifacts, but you
> >> should be linking to your mirrored artifacts.
> >> - You have not cleaned up your old releases, your old releases
> should
> >> be archived.
> >>
> >> Now here's the catch - we require mirroring but I can't find
> anything
> >> saying what the mirroring URL is.  The format is going to be
> >> http://apache.org/dyn/closer.cgi/incubator/mnemonic and you'll want
> >> to grab your specific version from there.
> >>
> >> John
> >>
> >>
> >>
> >> On Wed, Aug 16, 2017 at 9:31 PM Gang(Gary) Wang 
> >> wrote:
> >>
> >>> Hi John,
> >>>
> >>> The Download menu item has been added to the navigator in home
> page,
> >>> Please refresh your browser to review it, Thank you very much for
> the
> >>> suggestion.
> >>>
> >>> Very truly yours
> >>> Gary
> >>>
> >>>
> >>> On Wed, Aug 16, 

[jira] [Closed] (MNEMONIC-272) Enable durable object wised persistent functions for Durable Map Tree Array

[Johnu George (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnu George closed MNEMONIC-272.
-
Resolution: Later

> Enable durable object wised persistent functions for Durable Map Tree Array
> ---
>
> Key: MNEMONIC-272
> URL: https://issues.apache.org/jira/browse/MNEMONIC-272
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
>
> The durable interface has been expanded to support object wised persistent 
> functions, so all inherited durable object has been impacted, it includes the 
> durable collections ie. durable map/tree/array.
> For the changes, please refer to MNEMONIC-270



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-275) Implement a default function to sync data to the persistent storage

[Johnu George (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnu George closed MNEMONIC-275.
-
Resolution: Later

> Implement a default function to sync data to the persistent storage
> ---
>
> Key: MNEMONIC-275
> URL: https://issues.apache.org/jira/browse/MNEMONIC-275
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Yanhui Zhao
> Fix For: 0.9.0-incubating
>
>
> Currently persist(), sync(), flush() calls are exposed to the user. This is 
> confusing.  Only one call should be exposed to user that provides the default 
> functionality. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-217) Implement cascading delete operation for a LinkedList

[Johnu George (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnu George closed MNEMONIC-217.
-
Resolution: Later

> Implement cascading delete operation for a LinkedList
> -
>
> Key: MNEMONIC-217
> URL: https://issues.apache.org/jira/browse/MNEMONIC-217
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Johnu George
>
> If the head node's autoreclaim flag is set and user calls its destroy(), all 
> the linked objects should be automatically destroyed. If autoreclaim flag is 
> not set,  user has to call destroy() manually. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNEMONIC-356) Assign fixed version number to docker Ubuntu build

[Wang, Gang (JIRA)]

Wang, Gang created MNEMONIC-356:
---

 Summary: Assign fixed version number to docker Ubuntu build
 Key: MNEMONIC-356
 URL: https://issues.apache.org/jira/browse/MNEMONIC-356
 Project: Mnemonic
  Issue Type: Task
  Components: Docker
Reporter: Wang, Gang
Assignee: Yanhui Zhao






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MNEMONIC-355) Remove Github link from navigator menu

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang resolved MNEMONIC-355.
-
   Resolution: Fixed
Fix Version/s: 0.9.0-incubating

Also, update the develop page to emphasize the Apache repo. and provide the 
mirrored GitHub link as an alternative way.

> Remove Github link from navigator menu
> --
>
> Key: MNEMONIC-355
> URL: https://issues.apache.org/jira/browse/MNEMONIC-355
> Project: Mnemonic
>  Issue Type: Task
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> we use Apache git repo. as our primary repo so remove GitHub link from the 
> navigator to avoid confusion



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MNEMONIC-355) Remove Github link from navigator menu

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang updated MNEMONIC-355:

Summary: Remove Github link from navigator menu  (was: Remove Github link 
from navigator manu)

> Remove Github link from navigator menu
> --
>
> Key: MNEMONIC-355
> URL: https://issues.apache.org/jira/browse/MNEMONIC-355
> Project: Mnemonic
>  Issue Type: Task
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
>
> we use Apache git repo. as our primary repo so remove GitHub link from the 
> navigator to avoid confusion



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNEMONIC-355) Remove Github link from navigator manu

[Wang, Gang (JIRA)]

Wang, Gang created MNEMONIC-355:
---

 Summary: Remove Github link from navigator manu
 Key: MNEMONIC-355
 URL: https://issues.apache.org/jira/browse/MNEMONIC-355
 Project: Mnemonic
  Issue Type: Task
  Components: Website
Affects Versions: 0.9.0-incubating
Reporter: Wang, Gang
Assignee: Wang, Gang


we use Apache git repo. as our primary repo so remove GitHub link from the 
navigator to avoid confusion



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-203) Document the build process for OS X

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang closed MNEMONIC-203.
---
Resolution: Information Provided

Docker based image file provided.

> Document the build process for OS X 
> 
>
> Key: MNEMONIC-203
> URL: https://issues.apache.org/jira/browse/MNEMONIC-203
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Debo Dutta
>Assignee: Debo Dutta
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-141) Provide accurate object size for application to use

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang closed MNEMONIC-141.
---
Resolution: Later

> Provide accurate object size for application to use
> ---
>
> Key: MNEMONIC-141
> URL: https://issues.apache.org/jira/browse/MNEMONIC-141
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Core, Memory-Service
>Affects Versions: 0.4.0-incubating
>Reporter: Wang, Gang
> Fix For: 0.9.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNEMONIC-139) Ensure the pool is opened for each of native calls.

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang closed MNEMONIC-139.
---
Resolution: Not A Problem

> Ensure the pool is opened for each of native calls.
> ---
>
> Key: MNEMONIC-139
> URL: https://issues.apache.org/jira/browse/MNEMONIC-139
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Memory-Service
>Affects Versions: 0.4.0-incubating
>Reporter: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> To avoid crash if use the pool after it is closed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MNEMONIC-112) cleaning up org_apache_mnemonic_service_computingservice_internal_PrintServiceImpl.c

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang updated MNEMONIC-112:


> cleaning up 
> org_apache_mnemonic_service_computingservice_internal_PrintServiceImpl.c
> 
>
> Key: MNEMONIC-112
> URL: https://issues.apache.org/jira/browse/MNEMONIC-112
> Project: Mnemonic
>  Issue Type: Improvement
>Reporter: Wei
>Assignee: Wei
>  Labels: performance
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> clean up redundant coding. not necessary any more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Deleted] (MNEMONIC-112) cleaning up org_apache_mnemonic_service_computingservice_internal_PrintServiceImpl.c

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang deleted MNEMONIC-112:



> cleaning up 
> org_apache_mnemonic_service_computingservice_internal_PrintServiceImpl.c
> 
>
> Key: MNEMONIC-112
> URL: https://issues.apache.org/jira/browse/MNEMONIC-112
> Project: Mnemonic
>  Issue Type: Improvement
>Reporter: Wei
>Assignee: Wei
>  Labels: performance
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> clean up redundant coding. not necessary any more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNEMONIC-354) asf-site build script lacks information that causing confusions when uploading

[Wang, Gang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNEMONIC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144192#comment-16144192
 ] 

Wang, Gang commented on MNEMONIC-354:
-

Fixed, please review it, Thanks!

> asf-site build script lacks information that causing confusions when uploading
> --
>
> Key: MNEMONIC-354
> URL: https://issues.apache.org/jira/browse/MNEMONIC-354
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Wang, Gang
>Priority: Critical
> Fix For: 0.9.0-incubating
>
>
> Build.md lacks following info: "git branch asf-site origin/asf-site", which 
> is causing confusions to build and upload the website.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MNEMONIC-354) asf-site build script lacks information that causing confusions when uploading

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang updated MNEMONIC-354:

Attachment: 0001-MNEMONIC-354-asf-site-build-script-lacks-information.patch

> asf-site build script lacks information that causing confusions when uploading
> --
>
> Key: MNEMONIC-354
> URL: https://issues.apache.org/jira/browse/MNEMONIC-354
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Wang, Gang
>Priority: Critical
> Fix For: 0.9.0-incubating
>
> Attachments: 
> 0001-MNEMONIC-354-asf-site-build-script-lacks-information.patch
>
>
> Build.md lacks following info: "git branch asf-site origin/asf-site", which 
> is causing confusions to build and upload the website.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MNEMONIC-354) asf-site build script lacks information that causing confusions when uploading

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang reassigned MNEMONIC-354:
---

Assignee: Wang, Gang  (was: wen tong)

> asf-site build script lacks information that causing confusions when uploading
> --
>
> Key: MNEMONIC-354
> URL: https://issues.apache.org/jira/browse/MNEMONIC-354
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Wang, Gang
>Priority: Critical
> Fix For: 0.9.0-incubating
>
>
> Build.md lacks following info: "git branch asf-site origin/asf-site", which 
> is causing confusions to build and upload the website.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MNEMONIC-352) Fix a name typo in develop page

[Wang, Gang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MNEMONIC-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wang, Gang resolved MNEMONIC-352.
-
Resolution: Fixed

> Fix a name typo in develop page
> ---
>
> Key: MNEMONIC-352
> URL: https://issues.apache.org/jira/browse/MNEMONIC-352
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wang, Gang
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)