Re: A Call For Open Governance Of X Development

Mark Vojkovich <[email protected]>
Newsgroups gmane.comp.xfree86.forum
Message-ID <[email protected]>
On Sun, 23 Mar 2003, Vadim Plessky wrote:

> Sorry for the late jump to the thread, but late ris betetr than never. :-)

> * XFree86 should be released on regular basis, and it should be splitted to 
> separate modules in such a way that upgrad eof one module doens't force you 
> to upgrade other modules too.

   I too think XFree86 should be released periodically.  No more than
once a quarter (unless you need an emergency security fix), no less than
twice a year.  No more than once a quarter because releases take alot
of time and keep developers away from actual development.  Also, in
order to release so frequently, you have to strictly observe code 
freezes.  When you release too frequently, you spend more time in
code freezes than you do in developement phases.

   Twice a year is a good schedule because new hardware is released
twice a year.  Corresponding releases to the spring and fall hardware
releases is not a bad idea. 

   As for the modules, you are lucky XFree86 isn't like Linux kernel
and actually has some semblence of binary compatibility between modules.
However, this still breaks down sometimes because it's not strictly
enforced, and probably shouldn't be because it would keep you from
ever being able to make any significant changes.


> 
> As about limited development resources - I am not sure that we can radically 
> change this in current economical environment.

   Yes.  The periodic release schedule relies on somebody having the
time to do this.  As a volunteer organization, this is not something
you can guarantee.   


			Mark.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.