Next PM3 offical release. v.3.2.0

[iceman1001]

I'm opening up for discussions on when the next offical pm3 release should be published.

I suggest that after the following items it would be fitting.

1. Emv commands needs to be finished.
2. apdu commands needs to be finished.
3. pm3 slowness needs to be finished.

I also suggest new version to be v.3.2.0 since we have the new commands.

[merlokk]

As for EMV:

• for now i have implemented all EMV transactions without SDA,DDA,CDA (it will be made in next PR's) for VISA and MasterCard
• as for future: I need to merge argtable and then i show PR with all the rest EMV commands (dont like to do it twice) )
• the next part: scanner and emulator. scanner included in EMV transaction code. Just needs to do some refactoring to break big procedure to parts
• emulator. we will need JSON parser and make 14a sim command with next behavior:
  commands from client go to arm side and returns (like android host emulator)
  so it will be online emulator, because there will be many data structures. it will be easier to make it on client side
  What do you think?

[iceman1001]

We are not going to change argument parsing in this release. That is a later and huge change.
We just need need to have your EMV to a certain point. Like your next PR. And that will fine for this release.
I'm most concerned about PM3 being slow from the thread changes... That is a show-stopper.

All the rest of your ideas for emulator, json, scanner, is not to be discussed in this issue. It should have a thread on the forum instead.

[pwpiwi]

Agree with @iceman1001. It is again time to stabilize after approx. 200 commits since 3.0.1.

What do you think about separate branches for the releases? E.g. we would now create a stable_3_1_0 branch and let homebrew point to this branch. This would allow us to backport bug fixes which may occur on master branch later.

[iceman1001]

That is great idea, @pwpiwi
Now why haven't we done this before?

[micolous]

I'd like to get #463 and #506 landed in this release so I can target a stable release for Android porting work. I've ended up writing a hack to blow away most of the context.

[iceman1001]

3. pm3 slowness, related to Comms refactor mk2 #463. Looks like @pwpiwi has not gotten the answers he needs in order to accept it. Needs to be resolved.

#506 is non-relevant for a release.

Sidenote, not to be discussed in this issue but in its relevant issues.
Problem is @micolous PRs is that the pm3-as-a-lib is not going into PM3 Master. Once we can stop spending time looking at code that could already been in a branch, by-it-self, and focused on fixing non-working items in the source, this process could have been so much faster.

[iceman1001]

With EMV part4 merged, it will do fine for a release with 'hf emv'

• Whats the status on 'hf 14a apdu', and with that I mean issues not relating to an new argument parser.
• Whats the status on pm3 slowness?

[merlokk]

hf 14a apdu works. I have not seen any improvements.

[micolous]

@iceman1001 To be clear, I'm not trying to shove the whole "pm3-as-a-lib" into next release, I'm trying to get the comms refactor stuff in there. That does mean I've done some really ugly hacks inside my (Android) code to reinitialise PM3 client global state. Long term I want to get rid of it.

My goal is to put enough of the code changes into PM3 upstream that I need for Android -- most of the stuff I've done is written on the side with custom build scripts: https://github.com/AndProx/AndProx/tree/master/natives/src/main/cpp

Idea being that whatever you folks decide to cut as 3.2.0, I can point AndProx at and it would "just work" without major source modifications, and Android becomes a platform like every other.

I'm only after getting #463 (which was approved a month ago) and #506.

[iceman1001]

@micolous I love the effort you put into your project and wish you good luck with your android app.
To be clear, "pm3-as-a-lib" will not make into PM3 Master. The repo-owner has said so. He shares the idea that you can put it all in a branch, or make a new repo for your pm3 version.

Regarding this release issue:
The #506 still suffers from not unifying the different methods to abstract the printandlog function, as I commented there awhile ago. Once you unify that, I see no problem with getting #506 merged.

[iceman1001]

recap,

1. hardnested memory alignment bug fixed
2. externalisation printandlog fixed ( Allow externalisation of PrintAndLog #506)
3. pm3 slowness / comms ( Comms refactor mk2 #463 ) is not done

Number 3, is the current showstopper for a new release. @pwpiwi ?