Hello Wojtek,
Answers below...
On 19/03/2023 00:07, Wojtek wrote:
Hi Benoit,
Answers below :-)
On 18/03/2023 01:15, Benoit TELLIER wrote:
Hello Wojtek
Answers inlined.
While answering inline, could you use customary ">" to denote quoting?
I helps with reading.
Btw. which e-mail client do you use? It seems it's not correctly
setting "References" header and thus breaking the threading.
An homemade application for JMAP protocol:
https://github.com/linagora/tmail-flutter/
References and In-Reply-To is yet to be managed (
https://github.com/linagora/tmail-flutter/issues/1608 ) but thanks for
the report.
I will use Thunderbird so as not to alter threading here by the time it
gets fixed.
Le mars 17, 2023 10:09 PM, de Wojtek A couple of questions:
- how do you actually publish docker images to docker hub?
Manually upon releases. Asf releases shall be a manual process.
But as docker is a non official release artifact (licensing) my bet
is that infringement on the asf policy should be tolerable...
OK
I see that
you use `buildTar` goal, which simply creates tarballs that then can be
imported to docker daemon and then pushed to remote repository;
unfortunately it doesn't support multi-platform - only `build` does,
which immediately push to remote repository (which is not ideal and
there is an issue opened in jib repository to split building and
pushing)
- do you publish any "nightly" builds? master is build every day but it
doesn't seem to be published?
> Nightly releases are discouraged within the asf as it encourages the
use of non released materials.
But i won-t oppose a nightly docker build if there is a consensus on
it...
OK, though not sure if it's essential.
Using `build` goal would probably require
using different profiles for release (with image as
`apache/james:`, eg: `apache/james:jpa-latest`) and then other
which would use different tag.
Wojtek
Continuing - one alternative could also be - building docker images
using `buildTar` in normal run (thus it wouldn't be published but
still be build) and having "release" profile that would use `build`
goal that would actually push artifacts.
Yes, that is how I understood so far your proposal.
As long as it gets documented in
https://james.staged.apache.org/james-project/3.7.3/community/release.html#_push_docker_containers
that is fine.
Also if we end up with many image, a script to help the release
performer might be handy...
Last but not least, which naming scheme for docker images do you have in
mind for handling different plateforms?
Regards,
Benoit
Wojtek
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
