Todos before v0.9

[im-coder-lg]

So, we got a lot of tasks after the merge of #9, #8 had a big commit history, so no. 9 was created. It's simple, not a big commit history but big changelogs. In fact, you can view them here and here.
Now, we need to do some tasks after the big merge(200 additions, 100 removals in #9).
They are as follows:

• Merge fix: Actions #9.
• Test on Windows 7 and 11 (@im-coder-lg and @sumeshir26, others are welcome to help on this)
• Test on macOS High Sierra+ (@not-nef but can be done during the holidays as said in #6 or anyone else, just volunteer here!)
• Make sure checks succeed without loose ends (@im-coder-lg Patch actions #12)
• Document changes (@im-coder-lg and @sumeshir26 for review)
• Triage on installer bug(error code 2756, comment linked, upstream(cx_Freeze error) and will be ticked off after finding the fix.)
• Get ready for v1.0.0-alpha!
  I think I will document the changes on StackEdit and post it as a secret gist here.
  These are the tasks to complete for v1.0.0-alpha's release. After that, we head towards beta, maybe RCs, and then hit the major v1.0.0 milestone.
  Edit by @im-coder-lg: We could try using the Auto Release notes feature to make automatic notes. testing that now.
  Edit by @im-coder-lg: We hit the jackpot. The Auto Release Notes feature is all we want! Read the entire section below:

Auto Release Notes

What's Changed

• feat(including bugs): minor changes that increases functionality by @im-coder-lg in feat(including bugs): minor changes that increases functionality #1
• feat: Dark mode by @sumeshir26 in feat: Dark mode #2
• feat: Always on top by @sumeshir26 in feat: Always on top #4
• fix: Actions by @sumeshir26 in fix: Actions #9
• Patch actions by @im-coder-lg in Patch actions #12
• feat: Actions Improvements by @sumeshir26 in feat: Actions Improvements #13
• feat: Actions improvements(Part 2) by @sumeshir26 in feat: Actions improvements(Part 2) #14
• feat: Unified action by @sumeshir26 in feat: Unified action #19

New Contributors

• @im-coder-lg made their first contribution in feat(including bugs): minor changes that increases functionality #1
• @sumeshir26 made their first contribution in feat: Dark mode #2
  Adding one more thing:
• @not-nef made their first contribution in feat: New Icon +Sun Valley theming in configurator.py #18.

No changelogs in a demo.

Edit by @im-coder-lg: Can we create a separate category on Discussions just for release tasks? So that this is not a general talk, it's kinda important, right?

[sumeshir26]

@im-coder-lg, what features would you like to be added to TimerX? And do you actuallay use timerx?
What about the tar.gz?

[im-coder-lg]

what features would you like to be added to TimerX?

First, a settings tab.
Next, the ability to activate blur as an optional feature, kinda like an Easter egg, like Google Easter eggs, it will be hidden.
After that, a simple documentation site where we address common issues(I know how to manage this 😉)

And do you actuallay use timerx?

I don't use it much since I don't keep a lot of timers, but I will try one and as the usual way, forget about it after 5 minutes. But it's be fun seeing my reaction after realising that TimerX was running, with a timer. Hopefully I'll get reminded to eat lunch after some time in my PC.

What about the tar.gz?

That is a hard question. If we can package it, it'd be easy. But half of Google searches are dead ends. But I think I will find something for the tarball and work on it.

[im-coder-lg]

We need to document the (major) commits that happened since v0.1 so that's what I meant. I will document it(after #9 is merged), can you review it?

[sumeshir26]

@im-coder-lg Sure

[im-coder-lg]

@sumeshir26 can you just trigger the build workflow? So that we can know if it succeeds here?

[sumeshir26]

Okay

[im-coder-lg]

Now, the checks work. PS: The macOS environment uses is macOS Catalina(10.15), so we can confirm that this will work on Big Sur and Monterey. If @not-nef or anyone with a local Mac machine tests the installer and the app, we can tell that macOS works.

[sumeshir26]

@im-coder-lg Do the notifications work on Win7

[im-coder-lg]

Yeah it shows up as a small bubble which is fine.

[sumeshir26]

@im-coder-lg

I tried to run bdist_rpm on replit, and it worked! It created a tar.gz at dist/TimerX-[version].tar.gz! So we can use github actions for tar.gz!

[im-coder-lg]

What's the command? Also, in the cx-Freeze issue, I figured out something. @marcelotduarte told us to use Alien(sudo apt install alien) on Debian-based systems(that includes Ubuntu), so we could use that to package files on a Gitpod env.

[sumeshir26]

build the ROM package on that?

ROM or RPM?

[im-coder-lg]

RPM, sorry about that. What about openSUSE?

[sumeshir26]

@im-coder-lg Doing that, can you look at the latest action run?

[im-coder-lg]

Ubuntu fails from here: https://github.com/sumeshir26/TimerX/runs/4530058102?check_suite_focus=true#step:5:80
Can't we try building on Fedora/any RHEL-based systems like CentOS and then publish here?

[im-coder-lg]

I wonder if we could install Fedora on Raspberry Pi...

[sumeshir26]

@im-coder-lg I did try getting OpenSUSE WSL but it gave some error when i ran pip install cx_freeze

[im-coder-lg]

Did you try pip3 and sudo?

[sumeshir26]

I also posted a question on Stack Overflow, waifting on a response on that.
Also, can you paste the markdown for yojur md markdown design?

[im-coder-lg]

Oops, didn't notice this... What markdown design? If you are asking for the banner one, it is this:

| your-text
| ---

Preview:

your-text

[sumeshir26]

Yes, those work, but cx-freseze fails to install

[im-coder-lg]

I just got an idea, will inform later.

[sumeshir26]

@im-coder-lg Whats your idea

[sumeshir26]

@im-coder-lg

[im-coder-lg]

Sorry for that... Got a really bad headache so dozed off... I'll also test by installing CentOS, I just need some free time.

[sumeshir26]

@im-coder-lg Try this
timerx_1.0-2_all.deb.zip
:

[im-coder-lg]

Testing that soon!

[im-coder-lg]

Have you tried breaking the DEB down with PeaZip? I did and it seems to be confusing... Will post the screenshots soon here.

[sumeshir26]

@im-coder-lg I Fixed the MSI error, it should work now!

[im-coder-lg]

Test complete, updating the todo list!

[im-coder-lg]

Hey, just wanna tell you guys this(also @not-nef welcome to the Contributors community!) that the Ubuntu build in the final Release build kinda seems like it's malfunctioning. I have collapsed the logs below, so you can check that if you want.

Logs

python setup.py bdist_rpm
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.12/x64
running bdist_rpm
creating build
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/rpm
creating build/bdist.linux-x86_64/rpm/SOURCES
creating build/bdist.linux-x86_64/rpm/SPECS
creating build/bdist.linux-x86_64/rpm/BUILD
creating build/bdist.linux-x86_64/rpm/RPMS
creating build/bdist.linux-x86_64/rpm/SRPMS
writing 'build/bdist.linux-x86_64/rpm/SPECS/TimerX.spec'
running sdist
running egg_info
creating TimerX.egg-info
writing TimerX.egg-info/PKG-INFO
writing dependency_links to TimerX.egg-info/dependency_links.txt
writing top-level names to TimerX.egg-info/top_level.txt
writing manifest file 'TimerX.egg-info/SOURCES.txt'
adding license file 'LICENSE' (matched pattern 'LICEN[CS]E*')
reading manifest file 'TimerX.egg-info/SOURCES.txt'
writing manifest file 'TimerX.egg-info/SOURCES.txt'
running check
warning: check: missing required meta-data: url
creating TimerX-1.0

warning: check: missing meta-data: either (author and author_email) or (maintainer and maintainer_email) must be supplied

creating TimerX-1.0/TimerX.egg-info
copying files to TimerX-1.0...
copying LICENSE -> TimerX-1.0
copying README.md -> TimerX-1.0
copying setup.py -> TimerX-1.0
copying TimerX.egg-info/PKG-INFO -> TimerX-1.0/TimerX.egg-info
copying TimerX.egg-info/SOURCES.txt -> TimerX-1.0/TimerX.egg-info
copying TimerX.egg-info/dependency_links.txt -> TimerX-1.0/TimerX.egg-info
copying TimerX.egg-info/top_level.txt -> TimerX-1.0/TimerX.egg-info
Writing TimerX-1.0/setup.cfg
creating dist
Creating tar archive
removing 'TimerX-1.0' (and everything under it)
copying dist/TimerX-1.0.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES
copying ./assets/logo.png -> build/bdist.linux-x86_64/rpm/SOURCES
building RPMs
error: Unable to open icon /home/runner/rpmbuild/SOURCES/logo.png: No such file or directory
error: query of specfile build/bdist.linux-x86_64/rpm/SPECS/TimerX.spec failed, can't parse
error: Failed to execute: "rpm -q --qf '%{name}-%{version}-%{release}.src.rpm %{arch}/%{name}-%{version}-%{release}.%{arch}.rpm\\n' --specfile 'build/bdist.linux-x86_64/rpm/SPECS/TimerX.spec'"
Error: Process completed with exit code 1.

Process failed, so maybe if GitHub has a Fedora Linux image or a CentOS image, we could try on that and then convert the entire RPM into DEB personally, right?

[im-coder-lg]

Anyway, it's kinda solved. I think it's kind of pointless to have the DEB. Try getting PeaZip Portable, open the DEB on that and just check the so-called archive.

[im-coder-lg]

People, I feel we are ready for the next release. @sumeshir26 can you please tell the release name 'cause you got my brain haywired in #21.
After that, let's release the next version on Christmas(your gift this year 😉) or New Year and then maybe get the next version out by Febraury of 2022.

[sumeshir26]

The name is v1.0-alpha. Need to update setup.py soon

[im-coder-lg]

I will add that to the PR of mine.

[im-coder-lg]

Hey @sumeshir26 can you setup Vercel here? For the website ofc, but during the setup, change the root dir and change the framework to Docusaurus 2.

[sumeshir26]

Ok, wait till wednesday.

[im-coder-lg]

Ok, wait till wednesday.

Wait, what? PS: Setup takes only 5 minutes, you'll have to check if it's into production soon.