Am 13.03.2014 09:18, schrieb Vincent van Ravesteijn:
... which means that in the ideal future, if you want a new feature
accepted into LyX, you should provide documentation about it and have
it well tested....
I am a bit annoyed about this. I only want a working release. I develop LyX for 10 years now and
helped to release LyX 1.4, 1.5, 1.6 and 2.0. It turned out that it is the most effective way to
update the docs after the feature freeze. Formerly we added the documentation immediately but this
was error-prone because
- the feature contributer wrote the documentation
- the documentation was written long before other features went in
It is normal that the contributer of a feature see it with different eyes than others and normal
users. This also applies for my own contributions and I am happy to have people like Ignacio and
Jean-Pierre who point me to issues in the doc texts so that normal users can understand them.
However, many bugs arise months after the feature contribution because e.g. the framework later was
changed etc. So the final documentation helps to test every feature with the feature-ready release.
- I need a test release for the win installer. This can be a RC1 release but
I need then some weeks afterwards to get enough feedback.
We have two beta releases released with a windows installer. What
changed in the installer that you need a new RC release and you need a
few weeks to get feedback ?
See its changelog in master - I completely changed the handling of Perl, its interaction with MikTeX
and fixed some bugs. I can also not test all the different languages (dictionaries and thesaurus)
due to lack of time.
Btw. to where can I upload the updated dependency package?
@ everybody: Can you please review
http://wiki.lyx.org/LyX/NewInLyX21
if all new features are listed so that I know what to document.
These are not blocking issues, but thanks for reminding people.
I of course know that this is no blocker but why does nobody wants to enrich
the page?
regards Uwe
