Where is the macOS app ?

[Tormen]

Hi,
the roadmap talks about "worked out quite good and the app has shown to be very stable."
https://github.com/thsmi/sieve/wiki/Roadmap
But I could not find any app to download / use.

And no release since 2021:
https://github.com/thsmi/sieve/releases

I would be very happy to sponsor this project as I find SIEVE really extremely useful.
But wanted to ensure that this is not dead as so many other SIEVE clients unfortunatly (http://sieve.info/clients) and ideally to see the status of the current progres.

Or did I miss something?
Thx a lot in advance!

PS: I would need a MacOS build

[BabyFnord]

FWIW, I've attached the last unofficial macOS build available corresponding to https://github.com/thsmi/sieve/releases/tag/0.6.1 here:
sieve-0.6.1.7z.001.zip
sieve-0.6.1.7z.002.zip
sieve-0.6.1.7z.003.zip

nota bene: Remove the .zip extension, use a 7zip compatible decompressing tool. Github messages allow for 25MB max per file, hence it's split into three parts. If you get some kind of permissions error, ie. app won't start, run xattr -cr /Applications/sieve.app in Terminal …

[polarathene]

The developer is no longer working on the project, thus no nightly builds get produced. They're unresponsive to attempts to reach them previously, not much you can do about that.

Unfortunately it was brought to their attention to consider a proper release but they disagreed.

See here for more details on why it's not possible to get a build, along with the justification for a new release being published (since the nightly builds only approach has resulted in this problem).

[thsmi]

@polarathene
please don't spread fake news and false information it does not help anyone!

There are sadly no other contributors. And yes I am currently low on time to do the development. So there is no they.

There is a proper release for Windows and Linux, which works fine for most users. Yes there are some issues on certain fedora linux machines. But other than that it works. So what should it be good for wasting time in doing a new release from an unchanged base? This is just pointless. It is basically just switching the build date. But you are obviously not able or willing to understand this.

If you are not happy with the situation then you have two choices either contribute and or don't use the project or remain silent. Trolling won't change anything except that you are getting ignored and as as side effect you burn valuable time which could have gone into development.

[polarathene]

please don't spread fake news and false information it does not help anyone!

The last commit was Jan 7th, 10 months ago? Your Github profile activity is also low.

It is a fair statement to say there is no active work on the project, especially when prior attempts from users about the issue at hand over the past months has gone unanswered. It is not fake news that you were unresponsive.

It is not to say you have abandoned the project, but that given the release policy you previously communicated with nightly / CI builds being the only intended source in the foreseeable future, with the lack of activity on the project those were no longer triggered thus the last CI builds expired (no longer accessible to users).

---

And yes I am currently low on time to do the development. So there is no they.

Try not to take this the wrong way, it is factual statements for users to understand the state of the project and what to expect.

There is no pressure on you to do anything and as a maintainer of projects I do understand.

By "they" I did not mean multiple people, I just find it quicker than adjusting for gender.

---

There is a proper release for Windows and Linux, which works fine for most users.

Nov 2021:

• Users are reporting problems with compatibility now.
• macOS users have no such access, they were direct to nightly builds but those have since become unavailable. They must build from source.

So what should it be good for wasting time in doing a new release from an unchanged base? This is just pointless. It is basically just switching the build date. But you are obviously not able or willing to understand this.

I've stated previously why I think a release would be valid, I don't see any point in debating that again. I know from the last time we discussed this that you won't budge on the idea and will happily let years continue to pass with the same justification, regardless of other reasons that you consider invalid.

If you are not happy with the situation then you have two choices either contribute and or don't use the project or remain silent.

I don't use the project. If I did I'm perfectly capable of building from source myself. I got a notification recently from user activity, then I noticed an issue and discussion about the same problem that had little context, so I added some for the benefit of other users that were wondering what was going on.

Trolling won't change anything except that you are getting ignored and as as side effect you burn valuable time which could have gone into development.

I'm not trolling 🤷‍♂️

My interactions with you does not motivate contributions, you've had those in the past and chosen to hold off a release since the changes to you are not worth a release regardless how much time drags on. You also cited nightly builds as a way to justify that, which as users have been expressing over the past few months have become unavailable.

If anyone is trolling it's your decision to not listen to your actual users that consistently ask about a release. You had CI infrastructure to build the macOS release and could have published a release for that as a result for those users (I don't user macOS FWIW), but you chose not to because directing users to those builds was good enough to you.

Fair, except you became busy as we all do, and now those builds became unavailable. You could trigger them again, and that'll work until the problem repeats itself.

If what I've said is fake news / false information and you really believe it's trolling, by all means assist your users with a release or triggering a CI build again for them. Otherwise if you don't have time for the project, update the README to communicate to your community that you are seeking new contributors or maintainers, or the status of your project if you're unable to maintain it going forward due to other commitments/priorities, that's perfectly ok and understandable.

[thsmi]

@polarathene please stop trolling and spreading fake and incomplete information! Before posting something please familiarize yourself with the facts!

There was never any official macOS release. I don't own a mac and developing stuff for macOS is always extra painful. The macOS user fraction is loud by very tiny. The user-base ration was stable over the last one and a halve decades. Windows and Linux are pretty much on the same level. The number of macOS users is tiny. And for curiosity there are more installation on SUN Machines than on macOS.

The macOS compatibility was contributed by a macOS user, but he did not have the time to support full releases. Thus the advice for macOS was always and is build it on you own or if you don't want to build it but know what you are doing, then use the nightly build.

But picking just a random nightly build is not a working concept, unless you know which branch triggered the build with which changes. They are experimental build and no betas or release candidates! And thus I definitely do not point users to the nightly build as you claim.

I generally point users to use the stable releases. Only if there is a hot-fix for a specific topic to test by a user, then you'll find a link to a nightly build in side an issue.

[thsmi]

@Tormen Tormen

You find the app for Windows an Linux in the last release:

But there never was a release for macOS (https://github.com/thsmi/sieve/wiki/FAQ---Application#app-macos-builds). I don't own a Mac and developing stuff for Mac is always special and extra painful. You always need to go an unexpected mac special extra mile...

Currently the only way to get a macOS build is to build it on your own from a stable build.
Or use the build provided by another macOS.

Currently there are no nightly builds because there weren't any changes recently. But in general it is not the best idea to use a nightly build unless you really know what you are doing and what changed.