Skip to content

Conversation

@LeonidVas
Copy link
Contributor

Before, many tarantool modules pushes only to the tarantool repositories. Now we push the modules to old tarantool repositories
(for backward compatibility) and to the "modules" repository.

Before, many tarantool modules pushes only to the tarantool repositories. Now we push the modules to old tarantool repositories (for backward compatibility) and to the "modules" repository.
@LeonidVas LeonidVas self-assigned this Nov 24, 2021
@Totktonada
Copy link
Contributor

I have no objections against this change, but before we'll get it out of our heads I would like to formalize where exactly we want to land our modules. See my question here.

@LeonidVas
Copy link
Contributor Author

I have no objections against this change, but before we'll get it out of our heads I would like to formalize where exactly we want to land our modules. See my question here.

tarantool/queue#158

@LeonidVas LeonidVas merged commit d1bd93a into master Dec 16, 2021
@LeonidVas LeonidVas deleted the lvasiliev/gh-no-ticket-add-modules-to-enabled branch December 16, 2021 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants