release news for 2024-12-31
- announce version 2.3 of the mkiocccentry repo - update `sitemap.xml` - update `status.json` and `status.html`
This commit is contained in:
1 parent
eabeb2966a
commit
a5ca630dc2
5 files changed
+62
-44
No files matched your search
@@ -432,7 +432,14 @@ major events such as the opening of a new IOCCC, or who won.</p>
|
||||
FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
|
||||
for more information on Mastodon.</p>
|
||||
<h1 id="news">News</h1>
|
||||
<h2 id="section">2024-12-30</h2>
|
||||
<h2 id="section">2024-12-31</h2>
|
||||
<p>We have just released <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>.
|
||||
This repo 2.3 release includes important improvements (over repo release 2.1) to the <code>mkiocccentry(1)</code> tool
|
||||
as well as a critical fix for installing on BSD based systems.</p>
|
||||
<p>Please download <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>,
|
||||
and compile the <a href="faq.html#mkiocccentry">mkiocccentry tool set</a>. You may also wish to install this code.
|
||||
See also the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md">mkiocccentry FAQ</a> for more information.</p>
|
||||
<h2 id="section-1">2024-12-30</h2>
|
||||
<p>The IOCCC <a href="next/rules.html#rule13">Rule 13</a> no longer discourages the
|
||||
use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> compilers,
|
||||
UTF-8 characters do not impose a compiler problem. The related guideline
|
||||
@@ -443,7 +450,7 @@ modifications as means to tell the submitter that their submission was received.
|
||||
<p>All of the import IOCCC dates within the <a href="next/rules.html">IOCCC rules</a>
|
||||
have been moved into the “<a href="next/rules.html#dates">Important IOCCC dates</a>”
|
||||
section.</p>
|
||||
<h2 id="section-1">2024-12-28</h2>
|
||||
<h2 id="section-2">2024-12-28</h2>
|
||||
<h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
|
||||
<p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>,
|
||||
with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed
|
||||
@@ -471,7 +478,7 @@ and <a href="status.json">status.json</a> has been updated to reflect this new s
|
||||
<p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a>
|
||||
have been released.</p>
|
||||
<p>See <a href="faq.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p>
|
||||
<h2 id="section-2">2024-06-08</h2>
|
||||
<h2 id="section-3">2024-06-08</h2>
|
||||
<p>We continue to make good progress on the
|
||||
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
|
||||
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
|
||||
@@ -501,7 +508,7 @@ not having to look at them more than once on a whole, other than possible
|
||||
entries that have to be added at the end, like the example below.</p>
|
||||
<p>Once the <em>submit server</em> server is ready another FAQ will be added and that
|
||||
entry can be looked at alone.</p>
|
||||
<h2 id="section-3">2024-05-30</h2>
|
||||
<h2 id="section-4">2024-05-30</h2>
|
||||
<p>A number of issues from minor fixes have been applied to the
|
||||
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
|
||||
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
|
||||
@@ -536,7 +543,7 @@ ask for beta testing of the new <strong>IOCCC registration process</strong> and
|
||||
This will speed up the start date of IOCCC28.</p>
|
||||
<p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
|
||||
IOCCC.</p>
|
||||
<h2 id="section-4">2024-04-30</h2>
|
||||
<h2 id="section-5">2024-04-30</h2>
|
||||
<p>The website now is viewing by mobile devices such as cell phones
|
||||
and tablets. Devices with a screen resolution 1024 pixels and
|
||||
narrower are given a <em>hamburger-style</em> menu icon in place of
|
||||
@@ -558,7 +565,7 @@ files that are static (not generated <code>bin</code> tools) report </strong>no
|
||||
warnings, nor info** messages, changes involving fixing invalid
|
||||
links to local files have been corrected, and changes involving the
|
||||
<em>topbar</em> are now HTML 5 conforming.</p>
|
||||
<h2 id="section-5">2024-04-20</h2>
|
||||
<h2 id="section-6">2024-04-20</h2>
|
||||
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
|
||||
website has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
|
||||
compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
|
||||
@@ -576,10 +583,10 @@ glaring “<em>dancing bears</em>” and other frivolous web features.</p>
|
||||
where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
|
||||
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
|
||||
<p>Stay tuned!</p>
|
||||
<h2 id="section-6">2024-02-29</h2>
|
||||
<h2 id="section-7">2024-02-29</h2>
|
||||
<p>We continue to make good progress on website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
|
||||
<p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
|
||||
<h2 id="section-7">2023-05-22</h2>
|
||||
<h2 id="section-8">2023-05-22</h2>
|
||||
<p>We have been busy preparing for an important / significant update to this website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
|
||||
<p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
|
||||
please <strong>do not link to it</strong> as this repo and related website will disappear once the main
|
||||
@@ -635,7 +642,7 @@ that needs urgent fixing.
|
||||
The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
|
||||
who submit real IOCCC entries at risk.</p>
|
||||
<p>Stay tuned!</p>
|
||||
<h2 id="section-8">2023-01-30</h2>
|
||||
<h2 id="section-9">2023-01-30</h2>
|
||||
<p>We added to the
|
||||
<a href="status.json">status.json</a> page,
|
||||
a <em>“status_date”</em> JSON member whose value is the date
|
||||
@@ -647,7 +654,7 @@ a <em>“latest_news”</em> JSON member whose value is the date
|
||||
of the most recent news item.</p>
|
||||
<pre><code> "status_date" : "Mon Jan 30 02:28:44 PST 2023",
|
||||
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"</code></pre>
|
||||
<h2 id="section-9">2022-12-18</h2>
|
||||
<h2 id="section-10">2022-12-18</h2>
|
||||
<p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola
|
||||
(<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social&rpar">@home.social&rpar</span>;</a>
|
||||
we now maintain a <a href="status.json">status.json</a> page on this website.</p>
|
||||
@@ -665,7 +672,7 @@ The details of such additional JSON members are <em>TBD</em>.</p>
|
||||
Instead you will have to rely on the additional JSON information
|
||||
and/or read the <a href="#news">IOCCC news</a>,
|
||||
and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
|
||||
<h2 id="section-10">2022-11-29</h2>
|
||||
<h2 id="section-11">2022-11-29</h2>
|
||||
<p>We are planning to abandon our
|
||||
<a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
|
||||
in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
|
||||
@@ -700,7 +707,7 @@ is made possible by volunteers,
|
||||
and those who voluntarily
|
||||
<a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
|
||||
<p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
|
||||
<h2 id="section-11">2022-11-19</h2>
|
||||
<h2 id="section-12">2022-11-19</h2>
|
||||
<p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
|
||||
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
|
||||
a GitHub repo that includes the official iocccsize tool,
|
||||
@@ -712,13 +719,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co
|
||||
judges will go through the motions (without judging the content) of an IOCCC:
|
||||
testing the above mentioned tools and testing the submit server.</p>
|
||||
<p>We are working on complete rebuild of this website as well.</p>
|
||||
<h2 id="section-12">2022-01-15</h2>
|
||||
<h2 id="section-13">2022-01-15</h2>
|
||||
<p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
|
||||
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
|
||||
a tool that is based on, and is containing, the official iocccsize tool,
|
||||
will form a compressed tarball that a registered IOCCC contestant
|
||||
will upload to the submit server (when the contest is open of course).</p>
|
||||
<h2 id="section-13">2021-12-27</h2>
|
||||
<h2 id="section-14">2021-12-27</h2>
|
||||
<p><a href="judges.html">The Judges</a>
|
||||
are continuing to work on re-tooling how we run the IOCCC.
|
||||
We are writing tools under various repositories our
|
||||
@@ -727,7 +734,7 @@ We are writing tools under various repositories our
|
||||
Sorry for the delay, but we think you will appreciate the re-tooling
|
||||
when it is completed.
|
||||
Stay tuned!</p>
|
||||
<h2 id="section-14">2021-10-21</h2>
|
||||
<h2 id="section-15">2021-10-21</h2>
|
||||
<p><a href="judges.html">The Judges</a>
|
||||
are re-tooling how we run the IOCCC.
|
||||
Our goal is to build a smoother, more rapid process centered around
|
||||
|
||||
Reference in new issue
Block a user