Maintenance-related issues about apns4erl HOT 9 CLOSED

I just checked and all those deps are only used for tests!
Yeah… @paulo-ferraz-oliveira @ferigis: You can do whatever you need there. As long as you preserve the coverage, I can't care less about what tools we use to test the system.

from apns4erl.

@elbrujohalcon, are you a maintainer of this? If not, who could give me some guidance, here?

from apns4erl.

I am not. This is @ferigis' project.

from apns4erl.

OK, I'll wait on @ferigis' feedback, then. Thanks.

from apns4erl.

Ping.

from apns4erl.

hi Paulo, sorry for the late response, I have been quite disconnected lately.

First of all thanks for using apns4erl and helping us with the maintenance :)

Honestly I am not aware of the latest projects in Erlang since I am writing a lot of Elixir these days so I would like to hear @elbrujohalcon opinion.

Brujo, what do you think about the proposals? I am not sure if Aleppo/katana have a proper replacement or maybe we should update it in order to avoid warnings.

from apns4erl.

@ferigis @paulo-ferraz-oliveira:

• Get rid of rebar3_codecov. Yeah, go ahead, kill it.
• aleppo. I have no idea what we are using it for, honestly. Is it because this project uses an old version of elvis somewhere?
• katana. Again, not sure what pieces of it we're using here. Most likely it's worth updating that project, generating a new release, and then using that new release here.

from apns4erl.

I'm going to dig deeper, since it seems katana needs a bit of an update too.

from apns4erl.

inaka/erlang-katana#160 opened, after which I think I'll tackle this. Let me prepare it with a _checkouts -oriented approach, though.

from apns4erl.