Josà AbÃlio Oliveira Matos wrote: > Hi all, > cutting the nonsense and being objective what needs to be done to > release > a stable 1.4.0? > > Is it reasonable to have a HEAD that has problems while Alfredo is > fixing > the bugs in the other branch?
Mmmm I'm not fixing bugs that are in HEAD, I'm just fixing bugs that were introduced in Andre's patch. I'm still not completely sure if this has to go forcefully into 1.4.x but I'm confident that it will go into the main trunk at some point (if not I'd not be spending so much time in a dead project). I do feel that once CoordBranch is stabilized a bit more it would be easier to fix bugs there than in HEAD. > Looking in bugzilla for bugs related with 1.4.0, blocker, critical, > major > and normal I see 22. Is this up to date? What needs to be done to clean > this? I suspect it's not up-to-date. For instance, what about crash on C-page down, or the fact that e.g. the "Proposition" label appears in two consecutive paragraphs with the Proposition layout in 1.4 but not in 1.3? For the first person that suggest me to add them to bugzilla: feel free ;-) > What are the subjects that other developers are working and would like > to > have fixed before 1.4.0 release? Of course, all editing/visual regressions wrt 1.3.x. > Here is my list: > > lyx2lyx - improve the resilence of lyx2lyx to bad input, that means > basically catching all the python exceptions if not using a development > version. The code for this is almost on place. Half an hour should be > enough to fix this. > > linuxdoc - replace all the code for paragraphs generation by the one > used > by docbook, the code there is sufficiently general and is well tested to > make this replacement. It is almost a mater of copy and paste, a better > factorization can be done in 1.5. > > docbook - implement the suggestions of Chris, most of them are special > cases for insets, so should not impact the core. > > PS: Before some says that this was discussed before, this days my > memory > qualifies as golden fish, so forgive and let us update the discussion. > > One good example that I like is kde: > http://developer.kde.org/development-versions/kde-3.4-features.html > > The question is clearly to define what needs to be fixed, and attribute > priorities to bugs, what is blocker and what can wait for 1.4.1. In my very humble opinion, none of the above are blockers. There are many obvious regressions (like the two mentioned above) that are. Just load the UserGuide in 1.4.x and start moving/editing around. If you cannot find an obvious blocker in 30 seconds, I owe you a beer. > PS: I hope this is a constructive message towards a stable 1.4 release > before this year Christmas. :-) Humm... I think that's too optimistic, but let's hope ;-) PS: Despite what it may seem, I'm an optimistic guy. I've spent a lot of time in 1.4.x and I don't want to throw it away so I'll work for the release as much as I can. It will happend eventually ;-) Alfredo
