Transition from tea4j to tea4j-autodeploy #907

Open
opened 1 month ago by opyale · 6 comments
opyale commented 1 month ago
Collaborator
https://codeberg.org/opyale/tea4j-autodeploy
opyale added the
Priority-high
External-dependecy
Long-term
labels 1 month ago
Owner

After some tests and confirmations, if everything goes well. Can we push the code to tea4j reposiotry?

After some tests and confirmations, if everything goes well. Can we push the code to tea4j reposiotry?
Poster
Collaborator

That's possible too, but the tea4j repository could also be set up to just mirror the contents of the tea4j-autodeploy repository.

That's possible too, but the ``tea4j`` repository could also be set up to just mirror the contents of the ``tea4j-autodeploy`` repository.
Owner

I guess it's better to manage it at one place rather than mirroring. Just my thoughts. Looks more convinient.

I guess it's better to manage it at one place rather than mirroring. Just my thoughts. Looks more convinient.
Poster
Collaborator

Yes, I think the best way would be to just transfer the ownership as soon as this is actually possible. But in the meantime the simplest way would be to just use my repository directly.

Yes, I think the best way would be to just transfer the ownership as soon as this is actually possible. But in the meantime the simplest way would be to just use my repository directly.
Owner

You mean to keep the repo tea4j-autodeploy as is but under gitnex org?

You mean to keep the repo `tea4j-autodeploy` as is but under gitnex org?
Poster
Collaborator

Yes. I think that the autodeploy part is especially useful, since it implies that all updates are managed and deployed automatically.

Yes. I think that the ``autodeploy`` part is especially useful, since it implies that all updates are managed and deployed automatically.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.