This is an automated email from the ASF dual-hosted git repository.
humbedooh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-ponymail-foal.git
The following commit(s) were added to refs/heads/master by this push:
new 92eb3f9 Add a disclaimer for Foal, and a small roadmap
92eb3f9 is described below
commit 92eb3f9698b65f5c94bb90e361c6adf52c495901
Author: Daniel Gruno <[email protected]>
AuthorDate: Mon Aug 24 20:41:46 2020 +0200
Add a disclaimer for Foal, and a small roadmap
This disclaimer generally speaking applies to all PM setups pre-foal as
well, but might as well put it out there.
---
README.md | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/README.md b/README.md
index c7f2843..6260fe0 100644
--- a/README.md
+++ b/README.md
@@ -5,3 +5,23 @@ _Next generation suite of services and tools for Apache Pony
Mail_
This repository aims to contain the next generation of Apache Pony Mail,
a pure python version of Apache Pony Mail with support for ElasticSearch 6.x
and above.
+
+
+### Roadmap
+Work is underway on the following items:
+
+- Improved archiver and import tools **[DONE]**
+- New UI for the end user **[DONE]**
+- 100% python backend, no mod_lua required. **[COMING SOON]**
+
+
+### Migration disclaimer:
+_While compatible with the original Pony Mail, this will not be a drop-in
replacement.
+Migration of the old database will be needed, and there may be edge cases
where
+re-imaging a database from scratch (re-importing from mbox files as opposed to
migrating
+your ElasticSearch database) will not produce the exact same permalinks as
before, if
+the input options don't match exactly. For lists with a List-ID header present
in all
+emails (and no override used), this should not be the case for any permalinks,
and
+they should be the same. If you have an existing Pony Mail database, migrating
it
+with the provided migration tool is highly recommended if you wish to preserve
old
+permalinks._
