From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Tue, 19 Mar 2013 14:47:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1303191434180.7751@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <5148AB62.50002@wxs.nl>
On Tue, 19 Mar 2013, Hans Hagen wrote:
> One these days there will be a first iteration of this years 'current'
> release. This has to do with the texlive code freeze.
Are there any plans to do an actual development freeze a few weeks before
the TL code freeze to ensure that the TL version is not beta quality.
Although most active users use ConTeXt standalone and are willing to
update frequently, TL still plays an important role in introducing new
users to ConTeXt. An experienced TeX user who wants to try ConTeXt is more
likely to try ConTeXt distributed as part of TL rather than ConTeXt
standalone. When there are serious bugs with ConTeXt TL, it gives the
impression that ConTeXt is not a mature macro package.
As anecdotal evidence, I used ConTeXt TL for my most recent article for
tugboat. There were some serious bugs in ConTeXt TL (multi-column
footnotes not working, marking styles not working, wrong font scaling,
etc.) and I had to struggle to get everything to work correctly. Most of
these bugs were fixed in the latest beta. But if I were a new user, I
would not have the patience to download and test the latest beta when a
supposedly stable release has serious bugs.
So, I'd like to suggest that for a few weeks before the TL freeze, we do a
ConTeXt-beta freeze with only changes being bug fixes.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-19 18:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 18:16 Hans Hagen
2013-03-19 18:47 ` Aditya Mahajan [this message]
2013-03-19 19:05 ` Hans Hagen
2013-03-20 1:52 ` Aditya Mahajan
2013-03-20 6:05 ` Otared Kavian
2013-03-20 8:05 ` Meer H. van der
2013-03-20 8:19 ` Keith J. Schultz
2013-03-20 8:40 ` Hans Hagen
2013-03-20 9:27 ` Mojca Miklavec
2013-03-20 9:37 ` Hans Hagen
2013-03-20 8:12 ` Keith J. Schultz
2013-03-20 8:25 ` Marcin Borkowski
2013-03-20 17:54 ` Keith J. Schultz
2013-03-21 10:19 ` Mojca Miklavec
2013-03-21 10:32 ` Alan BRASLAU
2013-03-21 14:26 ` Marcin Borkowski
2013-03-22 7:31 ` Keith J. Schultz
2013-03-22 8:26 ` command reference (was: upto current) Peter Münster
2013-03-22 10:11 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-22 10:25 ` command reference Peter Münster
2013-03-22 12:04 ` Hans Hagen
2013-03-22 14:42 ` command reference (was: upto current) Sietse Brouwer
2013-03-22 16:07 ` Sietse Brouwer
2013-03-22 17:21 ` command reference Hans Hagen
2013-03-24 21:48 ` Sietse Brouwer
2013-03-25 9:42 ` command reference (was: upto current) Keith J. Schultz
2013-03-25 9:34 ` Keith J. Schultz
2013-03-22 14:19 ` upto current Bill Meahan
2013-03-22 14:32 ` Taco Hoekwater
2013-03-22 14:37 ` luigi scarso
2013-03-22 14:47 ` Hans Hagen
2013-03-25 8:02 ` Keith J. Schultz
2013-03-20 8:49 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.02.1303191434180.7751@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).