Releases
Final Releases
2.1.22
Git Hash: dc65fa6e68a5f48fe02cf6f8c82576de3034d716
Changelog
FIX: improve windows compat
2.1.21
Git Hash: c2e65048956cdd17b2c0a303a612ac4f2a5eaff1
Changelog
FIX: LIB-15 - “Need cache_decrypt_message() to pass back longmsg/longmsg_formatted”
2.1.20
Git Hash: 1483087317fb86ad359338d6048691798e61a3e2
Changelog
- BUILD: Windows build updated
2.1.19
Git Hash: 1511498d82fce5f8de4fb188a26cd39b6c9b3e83
Changelog
- FIX: NO JIRA TICKET. Apparently some change i did (because i suspected a possible bug) actually resolved the “huss sync issue” volker was debugging the engine for. But, the actual fix is in this release (6fe0f96ee7547073b55cd969ca5221528dee62aa)
- INTERNAL: LIB-13: “Define Coding Standards And Project Structure” - Reformat (almost) the whole codebase using clang-format.
- BUILD: The C++ Standard to be used (pEp-wide) has now been raised to C++14 (max)
2.1.18
Git Hash: 9b4a3c78710ac7ffad145b1696e79d6dd4391733
Changelog
- FIX: LIB-14 Android build: Always include android/log.h not just on debug
- CI: DEPENDENCIES - libpEpAdapter does not specify engine version to be used.
2.1.17
libpEpAdapter |
1270d1476e5e401210ef7eb1a708d7cf8029c8e5 |
Release_2.1.17 |
pEpEngine |
c6cd6b02dc18c980e8fe7ed36bf4211054d85c3e |
Release_2.1.23 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.16
libpEpAdapter |
8612056193b5e73b4cd61e1a30b0ab839b39d2ed |
Release_2.1.16 |
pEpEngine |
eadb495d62ee76605ef0962c3e22a15e02607e87 |
Release_2.1.22 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.15
libpEpAdapter |
842c764e85238b9fe305296d62d2ef4ffc42f3c7 |
Release_2.1.15 |
pEpEngine |
ad88bec8c3f44ddea2e919a2b648534b2c329ebf |
Release_2.1.21 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.14
libpEpAdapter |
915632d3fa54fcbddfe2592a85ee4d4dca28b260 |
Release_2.1.14 |
pEpEngine |
68a9460adcc6d72ed30b528892bc23ce19189133 |
Release_2.1.20 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.13
libpEpAdapter |
6d318e5685b808d10510bb7b85592b8c3e457b92 |
Release_2.1.13 |
pEpEngine |
55f7338ca95972f74cf51a7558d25189b2de9d2f |
Release_2.1.19 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.12
libpEpAdapter |
513dd36e1b9923a9215df8941cfc54ff2a747330 |
Release_2.1.12 |
pEpEngine |
61ea387f41fbb28daded8ddb7bd8fe03b8c3c9f9 |
Release_2.1.18 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.11
libpEpAdapter |
5cca0658b7bde24aa7707cd07c6ec6af10d28ade |
Release_2.1.11 |
pEpEngine |
cdd9161de63d98ff5fc4653f1cc5cd0a3b6dae75 |
Release_2.1.16 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.10
libpEpAdapter |
d9049651855d7315a2b258f52b72f99cf783a09a |
Release_2.1.10 |
pEpEngine |
a3806eb2c36e21a31d8e15231056ba39213995f1 |
Release_2.1.15 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.9
libpEpAdapter |
bcd05ee2040260b9f2c2bc4a1f78c04cdd90accb |
Release_2.1.9 |
pEpEngine |
a432932ced70c1c2d6ecd9b5ba8c796f768334f8 |
Release_2.1.14 |
Changelog
- BUILD: Dependency update pEpEngine
2.1.8
libpEpAdapter |
ff0b8afbb83dbfa5707d21a06a110102358414d6 |
Release_2.1.8 |
pEpEngine |
6af7aa85782f7d588a2d9bfcc25d6389b4f1c276 |
Release_2.1.13 |
Changelog
- Fix: pEpLog missing includes on android platform
2.1.7
libpEpAdapter |
30e7668d5156176adf8ea622c03e02d31542177d |
Release_2.1.7 |
pEpEngine |
6af7aa85782f7d588a2d9bfcc25d6389b4f1c276 |
Release_2.1.13 |
Changelog
- Fix: pEpLog does not use the engine for logging anymore
- Feature: pEpLog add support for android
- Build: Windows build updated for pEpLog.cc changes
- Build: Android build updated (now using *.cc to compile)
- CI: don’t use insecure docker registries anymore
2.1.6
libpEpAdapter |
6f9a485f2ab7dde1c34b300e6a04cdcfc5365676 |
Release_2.1.6 |
pEpEngine |
6af7aa85782f7d588a2d9bfcc25d6389b4f1c276 |
Release_2.1.13 |
Changelog
- ALL FILES - replace
#pragma
once with standard include guards (and make sure license header)
- Merged in current master branch
- Makefile - Use compiler to generate .d files instead of using sed
- CI files added
- Add reference to pEpEngine project in Windows project
2.1.5
libpEpAdapter |
277204c40d2ac44c655cacbdf8f4d121e6f9b675 |
Release_2.1.5 |
Changelog
- use
std::<atomic>
types for thread synchronization. (otherwise undef behaviour)
- Semaphore - use
std::<atomic>
types for thread synchronization. (otherwise undef behaviour)
- pEpLog:
- added pEpEngine logging API support (providing platform abstractions and portability)
- runtime switching
- thread-safety
Release Candidates
Do NOT use any release candidates in a final release. If you want to use a specific RC for a final release (because if has gone throught the testing stage successfully), please request a release for that specific RC.
3.0-RC5
libpEpAdapter |
c961f665d62d947b98d4c6c6f74ff82c284175d1 |
Release_3.0-RC5 |
pEpEngine |
c6cd6b02dc18c980e8fe7ed36bf4211054d85c3e |
Release_2.1.23 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC5
libpEpAdapter |
c961f665d62d947b98d4c6c6f74ff82c284175d1 |
Release_3.0-RC5 |
pEpEngine |
c6cd6b02dc18c980e8fe7ed36bf4211054d85c3e |
Release_2.1.23 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC4
libpEpAdapter |
7344ab26eba99999c25c301cee2ce1ec767d2753 |
Release_3.0-RC4 |
pEpEngine |
eadb495d62ee76605ef0962c3e22a15e02607e87 |
Release_2.1.22 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC3
libpEpAdapter |
e69179229e7555d070a253560530dd48392c2636 |
Release_3.0-RC3 |
pEpEngine |
ad88bec8c3f44ddea2e919a2b648534b2c329ebf |
Release_2.1.21 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC2
libpEpAdapter |
dbc036a95dec3aa8f0edd0524bbe34a6ca693359 |
Release_3.0-RC2 |
pEpEngine |
68a9460adcc6d72ed30b528892bc23ce19189133 |
Release_2.1.20 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC1
libpEpAdapter |
e0371109dfea05797870600e6857ab8571fbc730 |
Release_3.0-RC1 |
pEpEngine |
55f7338ca95972f74cf51a7558d25189b2de9d2f |
Release_2.1.19 |
Changelog
- BUILD: Dependency update pEpEngine
3.0-RC0
libpEpAdapter |
b8004d624ef119d7cf17586701abd676a0a7559a |
Release_3.0-RC0 |
pEpEngine |
61ea387f41fbb28daded8ddb7bd8fe03b8c3c9f9 |
Release_2.1.18 |
Changelog
VERSIONING:
- It has been defined now that the version numbers of libpEpAdapter are totally independent of anything else.
- The increased major version number is deliberate, and to make clear, that the version numbers are decoupled from now on.
About This Docuement
heck> | 1) Which engine version should be specified if the adapter supports a whole range of versions?
fdik> | 1) the latest engine darthmama recommends to use
heck> | 2) what if there is a new engine version but no new adapter version ( New engine func needed, but no change in adapter required) ?
fdik> | 2) you add a new version always even if nothing changed
heck> | 3) only direct deps of the adapter ? (like libpEpAdapter, pEpEngine), OR the full stack of deps and deps of deps...??? (like which version of rust to compile sequoia?, etc... )
fdik> | 3) full stack
heck> | 4) how far back do i need to documet the releases? from now on? or all regressively all rels there have ever been?
fdik> | 4) from now on beginning what needs to be used now
heck> | 5) for patch rels of adapter, is the correct engine versio to be used always latest of this minor release like 2.1.<highest-available> ?
fdik> | 5) => darthmama decides
heck> | if its full stack, i think its almost unavoidable that dependency info needs to be published of each component recursively down the tree.
heck> | So, in other words, pEpEngine will need to publish their rel infos (deps) for each rel
heck> | sequoia will have to provide that too, etc...
heck> | its a dependency tree...
heck> | in which every component inherits all dependencies from all its children
heck> | or did you imagine a different sort of approach to the problem...
heck> | ?
fdik> | see the provided example page