Hi Mechtilde, On Tuesday 18 of May 2010, Mechtilde wrote:
> In my view there are different problems. > > 1. the different build environments, not only ooo-build or vanilla. Each > distri has its own environment with some small differences. Sure, that is a challenge, but of course it is the package maintainer's duty to fix those. > 2. the more or less missing QA-Process. Not sure what are you talking about? Are you saying that go-oo has no QA process? - that would be a complete news to me :-) The fact that we differ in the development style (everyone commits the patches directly to the main repository, no CWSes, and the possibility for bugs coming from integration/merges of various CWSes), does not mean that we do not have a QA process. We have a tinderbox that notifies committers of wrong commits, we release betas in timely manner, have quite an extensive test plan (in our Testopia), run qatesttool during the beta phase & analyze the results, have a large set of documents for regression testing, etc. Oh yes, I must not forget the bug triage of the new bugs which guarantees the initial treatment of the new bugs in up to a (working) day or two. > > That's how I can formulate the problem, although I'm glad we > > have some form of final upstream contribution in the end. > > we (from the project) should also learn how distributions work and how > they build/maintain their versions I hope the above helped you at least a bit. > >>> - that the Go-OO team moves to our own IZ and that both branches > >>> get a common reporting platform, a common visibility (and perhaps a > >>> common treatment). > > One idea to a way could be that we take the person how is responsible > for a distribution in the CC so (s)he can decide if this problem is a > distribution problem or a go-oo problem. Sure - that would be a good use of the alias too. > >> We would create an alias like [email protected], and anything > >> that you identify as a go-oo only bug, you'd just reassign to this > >> alias, instead of closing it as 'invalid'. We would take care of the > >> proper assignment of the bug (all the go-oo people have an IZ account > >> too), and its solution. > > and here we have to work together to analyzed where the bug come from. > in the past time it was not so easy to motivate the people to workout > the reason of the problem. Sure, it is always challenging to get answers for needinfos :-) > >> What do you think, please? > > I can't see an advantage of this alias. The advantage is one entry point for all the bugs that you find out as "probably go-oo only". Regards, Kendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
