ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt versioning model critique
Date: Fri, 20 Apr 2007 22:57:26 +0200	[thread overview]
Message-ID: <46292936.9060909@wxs.nl> (raw)
In-Reply-To: <4628B2A0.1040902@gmail.com>

fdu.xiaojf@gmail.com wrote:
> Vyatcheslav Yatskovsky wrote:
>   
>> Dear Patrtic,
>>
>>   
>>     
>>> ... ConTeXt would probably stabilize, which IMHO is not a good thing.
>>> One thing I really love ConTeXt for is the speed new techniques are
>>> adopted (pdf features, luatex,...) One day we might have a ConTeXt
>>> MKII book for those who are afraid of swithing to pdftex2.
>>>     
>>>       
>> ConTeXt should be eventually stabilized so that someone can make some use of it. But, there is a way for rapid adopting of new techniques too.
>>
>> My experience of using open-source products (I'm best familiar with Moodle) suggest that there should be overlapping cycles in development:
>> 1. Allocate new version number and start implementing new features.  Many things are broken at the moment and the version becomes unusable for production purposes. 
>>     
in addition to taco's answer:

i seldom do big chances in the distributed version; actually, i always 
use the alpha/beta/whatever in production here;
>> 2. Stabilize this version and make definite release (number x.x.). Now it can be used for production.
>> 3. Continue resolve bugs in this version AND perform Step 1 IN PARALLEL.
>>     
you can consider the tex live versions the formal stable versions -)

fyi: the real experimental stuff is in mkiv code and only a few have 
this on their machines; it's not in alpha/beta releases at all

keep in mind that a more complex versioning model will put my/taco's 
time for 'paid' work even more under pressure
>> Moodle follows this model and I always wandered how smooth it was to migrate between releases. Everything is completely predictable.
>> Please, look at http://download.moodle.org/ to get the idea of their versioning.
>>
>> I think ConTeXt needs similar versioning model badly. Now it has rather naive model (release dates) that doesn't help in deciding about stability at all.
>>
>>   
>>     
>   I strongly agree that ConTeXt needs an improved versioning model.
>   
in principle you can take any version you want from the svn repos 
(nicely packages in zips btw)

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  parent reply	other threads:[~2007-04-20 20:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1176544802.32527.ntg-context@ntg.nl>
2007-04-14 11:29 ` Vyatcheslav Yatskovsky
2007-04-14 15:03   ` Ulf Martin
2007-04-14 20:47     ` Hans Hagen
2007-04-14 21:19       ` luigi scarso
2007-04-20 12:31   ` fdu.xiaojf
2007-04-20 13:17     ` Taco Hoekwater
2007-04-23  1:15       ` fdu.xiaojf
2007-04-20 20:57     ` Hans Hagen [this message]
2007-04-20 21:42       ` Table of contents and 2UP or 2SIDE Horacio Suarez
2007-04-21  6:23         ` Hans Hagen
2007-04-14 12:28 ` Some progress with XeTeX Vyatcheslav Yatskovsky

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=46292936.9060909@wxs.nl \
    --to=pragma@wxs.nl \
    --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).