Go to page:

Search:   Help

Developers' side bar

Selected categories


Shared groups



Categories: Development, Misc
<< | Page list | >>

Miscellanous unsorted notes regarding the LyX developmen. Place the notes here before they are eventually move to a wiki page of their own.

Types of releases

Jose wrote about releases and Christian copied it here:

Development releases that eventually lead to a stable release, e.g. LyX 1.5.0.

Alpha release
An alpha release is a release of the LyX software from the development source code at a point when only a few, if any, new major features are expected to be added before the first stable release.
Beta release
A beta release is a release of the LyX software from the development source code at a point when very few (and minor) new features are expected to be added before the first stable release.
Release candidate (prerelease)
A release candidate is a release of the LyX software from the development source code at a point when only bug fixes are expected to be added before the first stable release. If the bug fix requires a file format change then OK.

Stable releases:

Stable release
The first stable release after a development cycle. It will be followed by maintenance releases. Note that the LyX file format is guaranteed to not changed between stable releases (i.e. the first stable release and the maintenance releases).
Maintenance release
A release of the LyX software that primarily fixes bugs in the previous stable release. The LyX file format is never changed by a maintenance release.

Comparison for normal users:

  • alpha => primary purpose is to help with development
  • beta => daring users may try it, helping with development still major factor
  • pre => should be stable enough for daily work
  • stable => what users should use normally.

Guidelines for file names

Bo's guidelines:

Guideline 1: Classname == file name

Because classnames are in uppercase, files are also named in this way. src/insets/*, src/mathed/* and src/graphics/* follow this guideline well so these are what I have renamed so far.

Guideline 2: Clean or merge helper files

If they cannot be merged, the name should be something like:


This format will also be applied to _fwd and _pimpl and _funcs.

Andre's guidelines

If there's a single class Foo implemented in the file, it should be Foo.h/Foo.cpp. That should be the common case.

If there are classes FooSomething, FooHelper, FooSimilar in the file, it should be named Foo.h/Foo.cpp.

If there are free functions fooHelper, fooSimilar, fooOther in the file, it should be named foo.{h,cpp}.

Name clashes should be avoided.

There should be no {L,LyX,Q,QL} prefix to class and file names.

Documentation files in LyXVCS:lyx-devel/trunk


Just a place to note a link to the NetBSD's branches:

I wonder how they relate to whatever system we use... /Christian

Miscellaneous links

PhD thesis on release management in open source projects.

Date: Thu, 2 Aug 2007 08:49:53 +0200 From: Asger Ottar Alstrup <asger-CWqSVQmbN6c@public.gmane.org> To: lyx-devel-UqbJ+GOpo4+hPH1hqNUYSQ@public.gmane.org Newsgroups: gmane.editors.lyx.devel Subject: Release management dissertation

Hi, See http://www.cyrius.com/publications/michlmayr-phd.pdf for a dissertation about the role of release management in open source projects.

I have not read all of it, but it does contain some interesting thoughts about whether to use feature based releases, or time based releases. Also, it touches on what practices and tools seem to make release processes work better in terms of helping the resulting quality of the release.

It should be an interesting read at this point, where plans are being made for the process for 1.6.

Regards, Asger

On the evolution of the user interface of MS Word

Date: Mon, 20 Nov 2006 10:28:33 +0100 From: Jean-Marc Lasgouttes <lasgouttes-0hXrFu2P2+c@public.gmane.org> Newsgroups: gmane.editors.lyx.devel Subject: Interesting stuff: lots of info on office UI

I just stumbled on this. It has a lot of information on the evolution of word UI, what works, what does not work, and why office 2007 is as it is. http://blogs.msdn.com/jensenh/archive/2006/11/10/the-office-2007-ui-bible.aspx

Creating a dialog from scratch

URL: http://www.lyx.org/trac/changeset/25144

Log: Preliminar InsetInfo dialog. This was done as an exercise to show Bo (an others) how easy it is to create a new dialog. This dialog needs to be filled in, right now, there is just an OK button.


On the origins of TeX

Pavel sent the following to the developers' list:

sorry for the OT, but i couldn't resits to post this link. there's longer biographical story about TeX conception directly from D.Knuth. there are also many interesting observations about the software development generally; i really enjoyed the reading (though its just transcript of videos recorded and presented at that page too.) maybe you will be interested too.
it starts around section 52 and it goes on some next 15 sections. http://www.peoplesarchive.com/browse/transcript/6942/en//

Category: Development, Misc

Edit - History - Print - Recent Changes - All Recent Changes - Search
Page last modified on 2008-11-15 20:48 CET