Bring this to everyone's attention, I know you'll be flaming me but: features and stuff that works is dying everywhere.. Somebody has to speak up.. need to fix fallouts, not checkin more stuff that breaks.. that is not progress? Is this crash landing/and stuff missing and nolonger working going to end soon? If stuff is going to land why not patch all the fallout bugs and test on your trunk/patch fallout build, then check all relatent patches into the CVS.. because the current method is just causing us people to go bonkers, and we are not seeing engineerers, qa/etc people say hah, ok.. thanks, maybe we should get right on it, and file them fallout bugs.. have em fixed asap before checking in new crash landings.. That would actually be progress...
So then as a tester I can open Bugzilla's new handy-dandy query for "stuff that works just fine, is now broken bugs because of yesterday's checkin's" listed here under your buildid=for today: It would also allow engineers to really see what they had broken for the day before = faster finding regressions = faster fixing bugs. CVS should mostly be used for crash landings for bugs that will break other components.. not ones where we are changing stuff that works in the same component into a bug. -> man when I developed software I'd crash land my own build and fix it before crashing the main build others have to rely on. no-wonder progress is slow. to do this you: A)create new local mirror copy as backup.. B)create local another mirror->edit code->it breaks->fix it C)create new local mirror->fix all fallout bugs-> D)create new local mirror->check if everything is stable E)Save as backup F)copy back to main build environment->fix problems in main build. G)go back to A) did I mention that visual bug in the editor, where text is displayed on the right side of a paragraph someplace verticle than it should be.. like the right most 4 characters, (this happens when you are typing text which then moves sentenced down a line at a time.. using the delete key for removing text and bring a sentence up a line will have those 4 characters line back up with the correct line. Taking a screenshot now. moving the window with the scrollbar also fixes the lineup of text. (maybe I'll file a bug in tomorrow on it. Problem is Mozilla doesn't do a redraw of the composer window, so once you click on the subject block the 4 characters go back to being visually lined up) This is making me want to just go back to using ns6.2 for my main browsing experience. I like testing Mozilla, but this is getting crazy, because all we can say to your bugs are can you reproduce this problem? Well If you tested the builds you checked patches into your self maybe you'd notice it too, and fix it before 100 newsgroup people go crazy.. Thankyou for reading.. and goodnight. oh, btw: Do what? I dont wanna do that as an end user-> are you crazy? I dont wanna delete lines from a file after click on the twisty everytime. And delete files because it not really a bug, its a feature its broken now.. come on.. Development really needs some organization and better methodology here.. I suppose I'm just summarizing what people say about Mozilla's Open-Source Problems.. and giving you ways it can be fixed.. This is positive feedback, and not trying to flame anyone person.. just the the general development here.. but if you think I hit your sore spot, I'm sorry.. like I said, someone has to step up to the plate to give you people some real leadership in development that actually works better than all the issues we have going on. maybe Mozilla should create seperate crash landing trees for each component of Mozilla.. then check those fixes into the trunk after issues get fixed. Dman84 wrote: > Dman84 wrote: > >> Jay Garcia wrote: >> >>> Seth Spitzer wrote: >>> >>> >>>> To work around it, remove lines from your localstore.rdf: >>>> >>>> <RDF:Description about="chrome://messenger/content/*.xul#msgHeaderView" >>>> state="true" /> >>>> >>>> (*.xul, depends on if you use the normal or vertical 3 pane view) >>>> >>>> if someone knows the bug #, please add this info to the bug. >>>> >>>> -Seth >>>> >>>> >>>> Peter Lairo wrote: >>>> >>>> >>>> >>>>> Hi, >>>>> >>>>> the header pane vanished after minimizing it. Does anyone know what >>>>> file >>>>> i need to delete to make it reappear? >>>>> >>>>> using mozilla 2001-11-01, winNT >>>>> >>>>> >>>>> >>>> >>> >>> Interesting, went to the bug posted by Pratik and big bold red letters >>> told me not top post with this version of Mozilla as it will cause >>> database corruption. >>> >>> Helluva day, I think I'll go cut grass or something less useless >>> ..... :-D >>> >>> Todays "afternoon" build. >>> >>> >> >> and Headers still disappear after clicking on twisty in 2001-11-02-09 >> W2K.. oh the builds are getting worse as the days go by.. more stuff >> is not working day after day .. DB problems.. people checking in >> stuff, missing files on checkins.. lots of crash landings. Oh well, >> I'd like to wait till they get fixed, because Mozilla is becoming more >> useless in this milestone everyday. maybe stop checking in new stuff, >> and just fix all the regression fallouts for the milestone 0.9.6.. >> >> -dman84 >> > > Why cant people crash land stuff on their local builds then fix the > problems then check that into the trunk, it would save us a lot of > headaches, huh? > > -dman84 >
