Hi Oliver, On Fri, 2007-07-06 at 10:07 +0200, Oliver Craemer - Sun Germany - ham02 - Hamburg wrote: > Hi, > > good work, but I miss the point where it is mentioned that there must be > a link to the installsets for the QA. This should not be a "nice to > have" but a "must", otherwise the QA representative has to ask the cws > owner for the installsets (with the delay which maybe occurs because of > different timezones etc.) or find someone who can build the installsets > locally.
This, IMHO, is a little overkill for those who work outside of Hamburg. For instance, if the QA rep is located in Hamburg, and the developer is located remotely in his own home (like myself), there are several hurdles that need to be overcome. 1) Broadband connection, especially the uplink speed. Most residential ADSL has a very limited uplink speed, and it's designed such that, when the uplink bandwidth is fully utilized, the download bandwidth becomes close to nill. This means that, when he's uploading the installation set, or someone is downloading them from a server located from his location, his net connection is effectively down, which affects his other business. 2) Server availability to upload the installation set(s). This may not be a problem for those who work within a large organization. But for a single community member from his/her own home, this can be a huge overhead. I understand that many OO.o community members are devoted enough to take care of it themselves, but we should still not take their service granted. 3) Last, but not least, if the cws in question affects only a small part of the OO.o codebase (e.g. one small-ish patch), why make this process this heavyweight? If the issue involves only one or two patches for one or two modules based on an existing milestone (e.g. SRC680_m218), it should be easy to re-use an existing build to create installation set. If we have an automated buildbot that provides an installation set, it's a different story, though. Just my 2 cents. Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
