Uwe Stöhr wrote:
I'm a bit worried about how you discussed this topic, so let me propose
a plan:
1. We've made a HUGE step forward toward LyX 1.5.0 since beta 1, so put
the beta 2 out now!
We need more people to test our efforts in bugfixing. That's why I
publish new 1.5svn-versions
for Windows, but we need more testers on Linux and Mac. Publishing a
beta 2 right now costs us
nothing but we will get much.
(Who's by the way our release manager for LyX 1.5svn?)
Jose is but he could use some help from you and Christian I guess :-)
2. Step through the open bugs in bugzilla, fix it or postpone it to LyX
1.5.1 or 1.6 in this
severity order:
- look for all critical or blocker bugs: http://tinyurl.com/2kljug
-> only 14 including 3 unconfirmed bugs
- look for all bugs with the keyword "regression":
http://tinyurl.com/3ybszf
-> only 33 including some bugs that are already fixedintrunk (you
cannot search in bugzilla for
the case "if regression and if not fixedintrunk")
- look for major bugs with the milestone 1.5.0:
http://tinyurl.com/2m3xju
-> only 10
- look for other bugs with the milestone 1.5.0:
http://tinyurl.com/2sv4ud
-> 49 including 11 enhancements
(- and if you like look for bugs with the keyword "patch":
http://tinyurl.com/2b4uvu
-> 50!, perhaps we can use some of them now with only small
adjustments)
Looks like a good plan. Thanks for doing this.
Within the next month we should have done the step through the bugs.
Don't be too shy to postpone bugs, I mean when nobody of us has an idea
to fix a bug, what else should be do than postponing?
In a month I'll start to postpone bugs with milstone 1.5.0 that are not
modified until then - sorry for beeing a dictator in this case ;-)
IMO we should not wait an additional month. We should do that now.
3. 3-4 weeks after beta 2 we discuss the release again to have a
definite release date.
I think we should set the release date now, independently from the
remaining bugs. I propose approximatively one month after beta 2, say
May 15.
Abdel.
