automate the distribution release

[benoitc]

Following comment on #194 (comment) we should have a way to automate the release and not to lag behind.

Todo:

• create travis scripts
• setup travis env with the appropriate key

[samwar]

@benoitc Any chance this issue can get addressed? I need the latest version v2.20.0 in hex.

[samwar]

@etrepum Since you seem to be the largest current contributor to this project is this something you can do?

I'm trying to upgrade my project to erlang 21 and between v2.20.0 not being in hex and webmachine relying on v2.18.0 it's making my life difficult.

[etrepum]

I don't think I have access to publish the package to hex, I've never done it and don't know how.

[samwar]

Is that something you think you could look into? There's already a hex package out there and I know webmachine is pinned to using the v2.18.0 version.

[etrepum]

It appears that @benoitc is the sole owner of the package on hex.pm. I'll give him another day to respond and if not then I'll go through the dispute policy and see if I can take over the package through that route and figure it out.

[etrepum]

I've emailed @benoitc directly and CC'd the hex.pm support team per their dispute policy. May take up to 30 days. If it doesn't happen in a week I'll see what I can do to escalate.

[etrepum]

I've had an email discussion with the team at Hex.pm and they are unwilling to make an exception to their policy and expedite this. Their recommendation is to fork the package and/or wait 30 days. I'm not going to deal with a temporary fork, but you are welcome to do so if you like. You may also contact them (or @benoitc) and see if you can get this expedited. Until then, I'll just set a reminder to start looking into it again in 30 days.

[benoitc]

i will make the release today. network was not working at fosdem.

On Sun 2 Feb 2020 at 00:14, Bob Ippolito ***@***.***> wrote: I've had an email discussion with the team at Hex.pm and they are unwilling to make an exception to their policy and expedite this. Their recommendation is to fork the package and/or wait 30 days. I'm not going to deal with a temporary fork, but you are welcome to do so if you like. You may also contact them (or @benoitc <https://github.com/benoitc>) and see if you can get this expedited. Until then, I'll just set a reminder to start looking into it again in 30 days. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#200?email_source=notifications&email_token=AAADRITC3WKE7ENCSVKSCQ3RAX647A5CNFSM4FLQLXOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRJDRI#issuecomment-581079493>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADRITQIJGASONETMRQ7ATRAX647ANCNFSM4FLQLXOA> .

-- Sent from my Mobile

[etrepum]

Great, thanks! When you get a chance, can you also add me to the hex.pm admin list as well so we have more people that can be “on call” for releases?

[benoitc]

yes i will

On Sun 2 Feb 2020 at 09:07 Bob Ippolito ***@***.***> wrote: Great, thanks! When you get a chance, can you also add me to the hex.pm admin list as well so we have more people that can be “on call” for releases? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#200?email_source=notifications&email_token=AAADRIU3GWZFSQCTZWPQFCLRAZ5NPA5CNFSM4FLQLXOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRQOPY#issuecomment-581109567>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADRITHGLBR6XD3XHNRQE3RAZ5NPANCNFSM4FLQLXOA> .

-- Sent from my Mobile

[benoitc]

there is no new tag since 2.20 which I just published. Can you tag current master @etrepum ?

[etrepum]

I've tagged 2.20.1, the only change since then was the metadata update that you made