ejabberd 21.01 before Debian 11 freeze?

[Neustradamus]

Since ejabberd 20.12 (and deps), there were some improvements about SCRAM/LDAP/Dependencies.

• https://github.com/processone/ejabberd/compare/20.12...master

I think it would be very wise to do the new release before Debian 11 freeze deadline (2021-01-12), and the next Debian will be in 2023.

The copyright update must be done before of course.

Note: I have requested an update of ejabberd_auth_http to have SCRAM sync.

Thanks in advance.

[debalance]

The relevant freeze date here is 2021-Feb-12, see https://release.debian.org

[Neustradamus]

@debalance: Thanks for your comment.

2 days ago, in another project, the Debian maintainer of the project said:

A new version requires a transition, and the transition freeze starts 2021-01-12. We need to get clearance from the release team for a transition beforehand, and the new version will need to have migrated to testing/bullseye before the freeze starts, so you'd need to give it 2-5 days assuming no blocking bugs appear. This is probably only going to fly if a new release is published in the next couple of days, given my own time constraints.

On the other hand I don't mind refreshing the Debian patches based on what's gone upstream and otherwise cherry-picking important fixes without pushing a new upstream release. The only stipulation is that we can't have a significant ABI change (which needs a transition). That would buy us another month before the soft freeze on 2021-02-12. After that I can still get bug fixes in targeting specific Debian bugs.

If I understand perfectly for ejabberd project, after 2021-01-12, it will be a 20.12-x, instead of 21.01, no?

[debalance]

"transition" means library updates which require many other packages to be rebuilt. It does not affect ejabberd. I have always happily uploaded new versions of my packages until the soft freeze, see https://release.debian.org/bullseye/freeze_policy.html#soft

[debalance]

To be exact: a new ejabberd release must have migrated to testing before the soft freeze on 2021-Feb-12.
It takes at least 5 days after I have packaged+uploaded a new release for it to migrate, so a new ejabberd release until end of January should be fine.

[Neustradamus]

@debalance: Thanks for your clarification :)

[badlop]

ejabberd 21.01 has just been published

[Neustradamus]

@badlop: Thanks!

[debalance]

Splitting the translations into a separate repository makes things rather complicated for me...

[badlop]

The PO files are not needed for compiling, installing or running ejabberd.

They are used only for improving translated strings, or for running "make
translations"

El ds., 30 de gen. 2021, 14:27, Philipp Huebner [e-mail]
va escriure:

Splitting the translations into a separate repository makes things rather
complicated for me...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/processone/ejabberd/issues/3465#issuecomment-770212540,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXUJ7ZRGOWODQDEN5DNQTS4QCM3ANCNFSM4VSCOK6Q
.

[licaon-kter]

@debalance ^^^

I actually delete msg/* so that translations are not loaded at start, to speed up things.

[debalance]

@licaon-kter That's not an option for the official Debian package

@badlop Just to make sure I understand you correctly: the translations are still part of ejabberd in priv/msgs/*.msg, so I can go without ejabberd-po and still have the same i18n features as before?

[licaon-kter]

@debalance I just mentioned that, eg. You could pack those separately. :)

[badlop]

Right. As packager and at runtime, PO files are not needed. In fact
ejabberd doesn't understand the gettext syntax.

The only files that ejabberd uses at runtime are the *.msg files. If you
inspect them, they have erlang syntax. Those translations are loaded at
start time.

The *.po and *. pot files exist to make life easier for translators,
because those have gettext syntax and are easy to edit with several
editors.

And "make translations" runs the script that updates all of them, and
converts from ones to the others, ready to be committed to git.

El ds., 30 de gen. 2021, 15:57, Philipp Huebner [e-mail]
va escriure:

@licaon-kter https://github.com/licaon-kter That's not an option for
the official Debian package

@badlop https://github.com/badlop Just to make sure I understand you
correctly: the translations are still part of ejabberd in priv/msgs/*.msg,
so I can go without ejabberd-po and still have the same i18n features as
before?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/processone/ejabberd/issues/3465#issuecomment-770224294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXUJZEKISVBUA6FUDWRJDS4QM5XANCNFSM4VSCOK6Q
.

[Neustradamus]

@debalance: ejabberd uses "priv/msgs/*.msg", I know that the name is not really good, I have requested to change to "translations", it has been refused: https://github.com/processone/ejabberd/issues/3498.

Note: It is not possible to add new package into Debian 11, the date was 2021-01-12.

[debalance]

This issue can be closed, ejabberd 21.01 is uploaded to unstable.

[Neustradamus]

@debalance: Thanks!