Nvu progress 20040513
By glazou on Thursday 13 May 2004, 16:11 - Nvu - Permalink
I am not happy, not at all. So many things regressed or changed recently that I have a lot of problems with Nvu/Composer for the first time (when I mean a lot, it's really a lot..)
- my build on WinXP fails, showing a lot of debug assertions failing. I have no idea where it comes from, I can't even launch Nvu!!
- my build on linux shows errors in nsExtensionManager.js and is unable to open the Site Manager in the sidebar; the "tab is not available right now"!!!! If I click on the "Image" button, the whole UI freezes and I can't even kill the application!
I think I am going to revert my codebase to 1.7, the tree is in real bad shape now even if the tinderbox show green.
Comments
Good idea. As both Firefox and Thunderbird will base their next release on the 1.7 branch, Nvu should do likewise.
The tree is in pretty terrible shape right now. Ben is in the middle of landing the new extension manager, and most of comm.jar is no longer being built.
Jens - next release is one thing, but we need the trunk to work as well, otherwise the release after the next one won't happen!
michaell: IIRC, the plan is to have Firefox 1.0 based on the 1.7 branch, too... So I guess Nvu could also stay on the branch for the next few releases (perhaps even 1.0)
The SeaMonkey tree, or the toolkit/whatever tree?
This is one thing that worries me about moving to Firefox, btw -- right now I have a stable UI under which to develop Gecko... I've not been blocked by UI bustage for months, and I'd like to keep it that way.
Trunk is completely unusable if you want to build something with GTK2.
For example, one of the worst bug I ever reported, which kills Firefox/mozilla when ending a download, or mailnews / thunderbird when sending a mail or a news post.
Bug 242768 if you want to look at it.
One gets a week of vacation, and then all the problems pop up. That's how unfair life is ;(
Now trunk is in the middle of an alfa cycle. Also, 1.7 has not been released yet. As soon as it is released, all developers' attention will switch back to trunk to get back all the stability lost. So, if Nvu schedule can wait, sticking to trunk can be a win in the long run.
Another thing is if Nvu can get a tinderbox on mozilla.org, it would be easier to track bustages.