>> We have the tinycc 0.9.28 release canditate for a long time,
>> but still no release
@grischka, we need you
>> Savannah has a buglist for tinycc:
>> https://savannah.nongnu.org/bugs/?group=tinycc
>> It works for collecting issue,
>> but unfortunately no one works on this issue list
> I did not even know that there is a bug tracker!
Yes, the bug tracker is a builtin feature of the software,
which is running to serve gnu.org and nongnu.org
> Note that
> https://bellard.org/tcc/
> says very clearly
> You want to help ?
> Here are some suggestions:
> Report bugs to the mailing list (and eventually fix them).
> which seems to foster mailing-list communication,
> and that is what was my impression for the many years i am on this list.
Yes, I know this text..
And with so few developer working on improving tinycc,
the mailing list is the main location, where bug reports where recognized
and sometimes get fixed.
But as soon, as a Mail is out of the short term history, it is also ignored.
As an example, i wrote about fixing tinycc to support
`nolibc.h`, but my assembly skills and my understanding,
how tccasm.c and the arch dependant assember parts work
where not good enough, so i was not able to fix it myself.
My mail is now 23 month old.
Out of sight,out of mind.
>> @grischka, what additional things can we do, to help you to make a release?
>> Last time it just suddenly happened.
I hope for a release every day.
> I mean, v0.9.28 is just another number, right?
NO
Some people just get the outdated tcc 0.9.27 from the tcc homepage,
and many linux distributions also have outdated tinycc packages.
As an example, my distribution package is from 14.Aug.2020.
That's better that the plain tcc-0.9.27 but still more than 3.5 years old.
> Currently it is
> version=20240309
> gitver=9d2068c6309dc50dfdbbc30a5d6757683d3f884c
Self compiling from the mob branch is not the issue.
The Download link on the TinyCC homepage links to
https://download.savannah.gnu.org/releases/tinycc/
and the newest tinycc is from 17.Dec.2017
> You do this prodding all the time,
A release is important.
See above.
> This is stunning since i learned that you contributed
> to this software over fourteen (14!) years ago already,
Upps, so long ago.....
I'm getting older
> half a decade or so before i subscribed.
You're welcome. Everybody can help.
> Why don't you treat this is a "permanent rolling release"
> instead for as long as there is no .28,
A rolling release does not help, see above.
> or (heaven!) 1.0
After the tcc-0.9.28 release, i wish tcc to get
* more attention
* a bunch of updates and fixes
* hopefully c99 conformance
* probably a better c11/c17 conformance
* probably more c23 features
*
* a lot more testing
* a tcc-0.9.29 release
*
* even more attention
* even more updates and fixes
* even more testing
* a tcc-1.0 release
The times between releases must be much shorter.
As an example, wine has a bi-weekly snapshot release,
which gets a new revision number and there is a yearly
stabilization/bugfix only phase, which ends in a new major release.
> I am happy to have tcc and that there are some major contributors
> that bring this project that i use almost every day forward.
You're welcome.
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
