[jira] [Assigned] (MNEMONIC-274) Add another Dockerfile for Ubuntu system

2017-05-31 Thread Yanhui Zhao (JIRA) 

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

Yanhui Zhao reassigned MNEMONIC-274:


Assignee: Yanhui Zhao

> Add another Dockerfile for Ubuntu system
> 
>
> Key: MNEMONIC-274
> URL: https://issues.apache.org/jira/browse/MNEMONIC-274
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Yanhui Zhao
> Fix For: 0.9.0-incubating
>
>
> The existed Dockerfile has described how to setup Mnemonic development 
> environment for CentOS only, so we need another one for Ubuntu, because the 
> Ubuntu also is one of most popular server system.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-31 Thread Johnu George (JIRA) 
Johnu George created MNEMONIC-275:
-

 Summary: 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: Wang, Gang
 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.3.15#6346)

Re: Apache Mnemonic Releasing

2017-05-31 Thread Debojyoti Dutta 
Hi Gary

Thx for the 1st version  happy to help and will add to the notes as I
do the release :)

debo

On Wed, May 31, 2017 at 4:17 PM, Gary Wong  wrote:

> Got it, Thanks, Let me submit initial version of "how to release" to wiki
> page.
>
> Very truly yours.
> Gary
>
> On Wed, May 31, 2017 at 3:18 PM, Patrick Hunt  wrote:
>
>> Having a "how to release" wiki page (or any kind of living document) for
>> the project ensures that anyone in the community can release the product.
>> This is great for onboarding new RMs, etc...
>>
>> Patrick
>>
>> On Wed, May 24, 2017 at 9:27 AM, Debojyoti Dutta 
>> wrote:
>>
>> > Thx a lot Gary and Patrick for the tips on release management. It would
>> be
>> > my 1st so I am going to seamlessly ask for forgiveness :)
>> >
>> > debo
>> >
>> > On Tue, May 23, 2017 at 7:43 PM, Patrick Hunt  wrote:
>> >
>> >> fyi many projects capture this, some even capture the exact email
>> formats
>> >> etc..., on their wiki. Typically as a "how to release" page, e.g.
>> >>
>> >> https://wiki.apache.org/hadoop/HowToRelease
>> >> http://htrace.incubator.apache.org/building.html
>> >>
>> >> You might compare to what you've created, however each project
>> typically
>> >> has it's own special cases.
>> >>
>> >> For things like "Commit the whole new release candidate folder in the
>> >> staged trunk
>> >> using the SVN client to commit it all" (and similar) you probably
>> should
>> >> just give the command to run to simplify things and reduce the chances
>> for
>> >> error. The more you can make each operation "copy/paste" the more
>> likely
>> >> you'll have a successful release and easier for the RM. That said the
>> more
>> >> you can automate the better (typically by adding it to mvn).
>> >>
>> >> Patrick
>> >>
>> >> On Tue, May 23, 2017 at 5:50 PM, Gang(Gary) Wang 
>> >> wrote:
>> >>
>> >>> Hi Debo
>> >>>
>> >>> Thanks you Debo for becoming our new releasing manager, I'm trying to
>> >>> detail the steps below from my previous releases, hope it can help.
>> >>>
>> >>> Hi PPMCs
>> >>>
>> >>> Please correct me if any missing or incorrect items below and welcome
>> to
>> >>> optimize & improve the following steps, Thanks!
>> >>>
>> >>> 1) Prepare a Linux box (one time setup)
>> >>> The commands are running on Linux OS, so please have a Linux box or a
>> >>> Virtual Machine for releasing
>> >>>
>> >>> 2) Prepare your release key if not yet or expired (one time setup)
>> >>> https://www.apache.org/dev/openpgp.html#generate-key
>> >>> Please also put your key fingerprint into your account,
>> >>> https://id.apache.org
>> >>>
>> >>> 3) Start a GPG agent on your Linux box using the following command
>> >>> (before
>> >>> releasing)
>> >>> $eval 'gpg-agent --daemon --use-standard-socket'
>> >>>
>> >>> 4) Install SVN client on your laptop to upload staged/released
>> artifacts
>> >>>
>> >>> 5) Using SVN client to check out the staged trunk (One time and Update
>> >>> before voting)
>> >>> https://dist.apache.org/repos/dist/dev/incubator/mnemonic
>> >>> This trunk is used to upload the release candidates before voting on
>> >>> dev@list
>> >>>
>> >>> 6) Using SVN client to check out the release trunk (One time and
>> Update
>> >>> after voting)
>> >>> https://dist.apache.org/repos/dist/release/incubator/mnemonic
>> >>> This trunk is used to upload the releases after voting on general@list
>> >>>
>> >>> 7) Using SVN client to checkout the project status file (One time and
>> >>> Update after releasing)
>> >>> https://svn.apache.org/repos/asf/incubator/public/trunk/cont
>> >>> ent/projects/mnemonic.xml
>> >>>
>> >>> 8) Replace the KEYS file contents with yours in both trunk of stage
>> and
>> >>> release and then commit the changes using SVN client
>> >>>
>> >>> 9) run the following command for auto release packaging on project
>> >>> directory
>> >>> $./build-tools/release.sh  > >>> version>
>> >>> 
>> >>> for example
>> >>> $./build-tools/release.sh 0.8.0 0.8.0 rc1
>> >>> Note that usually we use the same current version in above command as
>> we
>> >>> cannot predict whether or not have a new candidate for this release
>> >>> before
>> >>> voting
>> >>> In this step, you may have to input your GPG password to allow gpg to
>> >>> sign
>> >>> off artifacts using your private key
>> >>>
>> >>> 10) Prepare the new release candidate folder on stage trunk
>> >>> please duplicate a folder from latest release candidate on stage trunk
>> >>> and
>> >>> rename it as current release candidate.
>> >>> for example: 0.8.0-incubating-rc1
>> >>> and then empty the src folder
>> >>>
>> >>> 11) Update the CHANGES.txt for current release candidate on stage
>> trunk
>> >>> a) open the JIRA for Mnemonic project
>> >>> b) in the overview, click the "Versions"
>> >>> c) click the latest version that needs to be release, for example
>> >>> "0.8.0-incubating"
>> >>> d) click the button "Release Notes" on top-right
>> >>> e) copy

Re: Apache Mnemonic Releasing

2017-05-31 Thread Gary Wong 
Got it, Thanks, Let me submit initial version of "how to release" to wiki
page.

Very truly yours.
Gary

On Wed, May 31, 2017 at 3:18 PM, Patrick Hunt  wrote:

> Having a "how to release" wiki page (or any kind of living document) for
> the project ensures that anyone in the community can release the product.
> This is great for onboarding new RMs, etc...
>
> Patrick
>
> On Wed, May 24, 2017 at 9:27 AM, Debojyoti Dutta  wrote:
>
> > Thx a lot Gary and Patrick for the tips on release management. It would
> be
> > my 1st so I am going to seamlessly ask for forgiveness :)
> >
> > debo
> >
> > On Tue, May 23, 2017 at 7:43 PM, Patrick Hunt  wrote:
> >
> >> fyi many projects capture this, some even capture the exact email
> formats
> >> etc..., on their wiki. Typically as a "how to release" page, e.g.
> >>
> >> https://wiki.apache.org/hadoop/HowToRelease
> >> http://htrace.incubator.apache.org/building.html
> >>
> >> You might compare to what you've created, however each project typically
> >> has it's own special cases.
> >>
> >> For things like "Commit the whole new release candidate folder in the
> >> staged trunk
> >> using the SVN client to commit it all" (and similar) you probably should
> >> just give the command to run to simplify things and reduce the chances
> for
> >> error. The more you can make each operation "copy/paste" the more likely
> >> you'll have a successful release and easier for the RM. That said the
> more
> >> you can automate the better (typically by adding it to mvn).
> >>
> >> Patrick
> >>
> >> On Tue, May 23, 2017 at 5:50 PM, Gang(Gary) Wang 
> >> wrote:
> >>
> >>> Hi Debo
> >>>
> >>> Thanks you Debo for becoming our new releasing manager, I'm trying to
> >>> detail the steps below from my previous releases, hope it can help.
> >>>
> >>> Hi PPMCs
> >>>
> >>> Please correct me if any missing or incorrect items below and welcome
> to
> >>> optimize & improve the following steps, Thanks!
> >>>
> >>> 1) Prepare a Linux box (one time setup)
> >>> The commands are running on Linux OS, so please have a Linux box or a
> >>> Virtual Machine for releasing
> >>>
> >>> 2) Prepare your release key if not yet or expired (one time setup)
> >>> https://www.apache.org/dev/openpgp.html#generate-key
> >>> Please also put your key fingerprint into your account,
> >>> https://id.apache.org
> >>>
> >>> 3) Start a GPG agent on your Linux box using the following command
> >>> (before
> >>> releasing)
> >>> $eval 'gpg-agent --daemon --use-standard-socket'
> >>>
> >>> 4) Install SVN client on your laptop to upload staged/released
> artifacts
> >>>
> >>> 5) Using SVN client to check out the staged trunk (One time and Update
> >>> before voting)
> >>> https://dist.apache.org/repos/dist/dev/incubator/mnemonic
> >>> This trunk is used to upload the release candidates before voting on
> >>> dev@list
> >>>
> >>> 6) Using SVN client to check out the release trunk (One time and Update
> >>> after voting)
> >>> https://dist.apache.org/repos/dist/release/incubator/mnemonic
> >>> This trunk is used to upload the releases after voting on general@list
> >>>
> >>> 7) Using SVN client to checkout the project status file (One time and
> >>> Update after releasing)
> >>> https://svn.apache.org/repos/asf/incubator/public/trunk/cont
> >>> ent/projects/mnemonic.xml
> >>>
> >>> 8) Replace the KEYS file contents with yours in both trunk of stage and
> >>> release and then commit the changes using SVN client
> >>>
> >>> 9) run the following command for auto release packaging on project
> >>> directory
> >>> $./build-tools/release.sh   >>> version>
> >>> 
> >>> for example
> >>> $./build-tools/release.sh 0.8.0 0.8.0 rc1
> >>> Note that usually we use the same current version in above command as
> we
> >>> cannot predict whether or not have a new candidate for this release
> >>> before
> >>> voting
> >>> In this step, you may have to input your GPG password to allow gpg to
> >>> sign
> >>> off artifacts using your private key
> >>>
> >>> 10) Prepare the new release candidate folder on stage trunk
> >>> please duplicate a folder from latest release candidate on stage trunk
> >>> and
> >>> rename it as current release candidate.
> >>> for example: 0.8.0-incubating-rc1
> >>> and then empty the src folder
> >>>
> >>> 11) Update the CHANGES.txt for current release candidate on stage trunk
> >>> a) open the JIRA for Mnemonic project
> >>> b) in the overview, click the "Versions"
> >>> c) click the latest version that needs to be release, for example
> >>> "0.8.0-incubating"
> >>> d) click the button "Release Notes" on top-right
> >>> e) copy the Text between "Configure Release Notes" and "Edit/Copy
> Release
> >>> Notes"
> >>> f) open CHANGES.txt and replace all contents with the one just copied
> >>>
> >>> 12) Upload packaged artifacts from Linux box
> >>> Please use tools e.g. SCP to download all artifacts suffixed with
> >>> *.tar.gz
> >>> under target/ folder

[jira] [Created] (MNEMONIC-274) Add another Dockerfile for Ubuntu system

2017-05-31 Thread Wang, Gang (JIRA) 
Wang, Gang created MNEMONIC-274:
---

 Summary: Add another Dockerfile for Ubuntu system
 Key: MNEMONIC-274
 URL: https://issues.apache.org/jira/browse/MNEMONIC-274
 Project: Mnemonic
  Issue Type: New Feature
  Components: Docker
Affects Versions: 0.9.0-incubating
Reporter: Wang, Gang
 Fix For: 0.9.0-incubating


The existed Dockerfile has described how to setup Mnemonic development 
environment for CentOS only, so we need another one for Ubuntu, because the 
Ubuntu also is one of most popular server system.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)