What does the release process look like? about graphback HOT 5 CLOSED

Apologies for the lack of release. Our team moved out of the project temporarily and making fewer changes.
However, we going to reply and keep things alive for a while. If you would like to fork it or even become a maintainer of the project let us know
For the moment we can provide the latest release although there is no feature development happening on the project for the next 3-4 months timeframe.

from graphback.

TL;DR - you can become maintainer, get permission to release and work with Option 1 indefinitely or fork it and replicate entire infrastructure. Options 1 or 2 :)

from graphback.

@wtrocki Thank you for the transparency! I would be interested in becoming a maintainer in the near future. We're soon implementing more searching/filtering features and finding that the #1967 issue needs some attention :)

from graphback.

Thank you for chooising this option. Despite us not working on project, you would still have more or less team that will be responsive/help and answer questions etc.

from graphback.

Release process involves creating tag with the new version in the releases. CI/CD does the rest (unless templates were changed) then we need to push main https://github.com/aerogear/graphback/tree/templates-1.0.0 this branch to release templates.

Hope that answers question. Closing for now

from graphback.