Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continuous release #292

Open
iTrooz opened this issue Nov 4, 2022 · 6 comments
Open

Continuous release #292

iTrooz opened this issue Nov 4, 2022 · 6 comments

Comments

@iTrooz
Copy link

iTrooz commented Nov 4, 2022

The last release is from over a year ago, but there seems to be a lot of changes (commits) since then.
If this is true, and if the release cycle must stay like this, I think it would be good to have a continuous release that is updated with the latest CI artifacts (which would also require a CI that build the app ofc)

I am willing to work on this, but I would like your approval (or from anyone that can merge a PR) first. Would you like such a feature ?

@DinuruSeniya
Copy link

DinuruSeniya commented Nov 17, 2022

I also support this. The current CI runner fails due to an outdated NodeJS version. However even after fixing that, I still get this error.
ERR : Because git_touch depends on antd_mobile from path which doesn't exist (could not find package antd_mobile at "../ant-design-mobile-flutter"), version solving failed.
It'd be helpful to have an updated app built on new versions of Flutter.

In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval.

@iTrooz
Copy link
Author

iTrooz commented Nov 17, 2022

In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval.
You mean, maintaining a fork ?

The problem is that

  • I don't want to spend time continuously maintaining a project, even if it's just rebasing from time to time
  • not many people would even be aware of the fork
  • I don't want to work on something that maybe won't be used

Even if you meant just preparing the PR in advance, my last point still apply

@zen0bit
Copy link

zen0bit commented Dec 17, 2023

I am interested...

@Nevarro
Copy link

Nevarro commented Jan 10, 2024

I'd be interested as well. I'm looking for a way to manage Forgejo/Gitea issues on iOS, maybe with push notifications on due dates.

@AkechiShiro
Copy link

Is the project abandoned currently ? There hasn't been much activity on the main branch since 2 years ago, @pd4d10 @shreyas1599

It could be however that the project is close to working all fine and so far it doesn't need much updates, but I'm not sure, I believe dependencies should be kept up to date, continuous release could help with that.

I'm not sure if @iTrooz is still interested and can work on his proposed idea

@Nevarro
Copy link

Nevarro commented Jan 24, 2024

@pd4d10 Is there any chance for further development?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants