Todos before v0.9 #10
Replies: 13 comments 45 replies
-
@im-coder-lg, what features would you like to be added to TimerX? And do you actuallay use timerx? |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
@sumeshir26 can you just trigger the build workflow? So that we can know if it succeeds here? |
Beta Was this translation helpful? Give feedback.
-
@im-coder-lg |
Beta Was this translation helpful? Give feedback.
-
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.
|
Beta Was this translation helpful? Give feedback.
-
@im-coder-lg I did try getting OpenSUSE WSL but it gave some error when i ran pip install cx_freeze |
Beta Was this translation helpful? Give feedback.
-
I also posted a question on Stack Overflow, waifting on a response on that. |
Beta Was this translation helpful? Give feedback.
-
Yes, those work, but cx-freseze fails to install |
Beta Was this translation helpful? Give feedback.
-
@im-coder-lg Whats your idea |
Beta Was this translation helpful? Give feedback.
-
@im-coder-lg I Fixed the MSI error, it should work now! |
Beta Was this translation helpful? Give feedback.
-
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. Logspython 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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
2756
, comment linked, upstream(cx_Freeze error) and will be ticked off after finding the fix.)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
New Contributors
Adding one more thing:
No changelogs in a demo.
Beta Was this translation helpful? Give feedback.
All reactions