Re: [DISCUSS] Do we want download links for Dev Builds on a usual webpage?
On Thu, Nov 15, 2012 at 2:44 AM, Andrea Pescetti pesce...@apache.org wrote: On 11/11/2012 Kay Schenk wrote: On 11/11/2012 04:22 AM, Andrea Pescetti wrote: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds (they are also called with/without system integration respectively). OK, I see this note and I confess I don't pay much attention to it, and typically install in parallel for these. But, I keep the same user profile if you will, and this doesn't seem to cause problems for me. Right now this note says: This week's builds are built without system integration. Is the the normal? What is normal highly depends on the status of the builds we are providing. For ordinary snapshots, without system integration is normal because they will co-exist with a stable version and be updated frequently; this would be the case for a beta release too, but as we approach release we will want to test system integration too and the normal snapshot will have system integration enabled. This is agreed on a case-by-case basis when we start building. Question: the bugs that we're seeing related to profile conversion/upgrading, is that something that would only have been caught when testing with system integration enabled? Hopefully my point is obvious -- we can't test and find system integration bugs unless we have system integration builds. Real testers today are using virtual machines. So the install side-by-side problem is not a real problem. But not having something that is as-close-as-possible to what we plan to ship -- that is a real problem. -Rob Regards, Andrea.
Re: [DISCUSS] Do we want download links for Dev Builds on a usual webpage?
On 11/11/2012 Kay Schenk wrote: On 11/11/2012 04:22 AM, Andrea Pescetti wrote: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds (they are also called with/without system integration respectively). OK, I see this note and I confess I don't pay much attention to it, and typically install in parallel for these. But, I keep the same user profile if you will, and this doesn't seem to cause problems for me. Right now this note says: This week's builds are built without system integration. Is the the normal? What is normal highly depends on the status of the builds we are providing. For ordinary snapshots, without system integration is normal because they will co-exist with a stable version and be updated frequently; this would be the case for a beta release too, but as we approach release we will want to test system integration too and the normal snapshot will have system integration enabled. This is agreed on a case-by-case basis when we start building. Regards, Andrea.
Re: [DISCUSS] Do we want download links for Dev Builds on a usual webpage?
[top posting] I think the setup we ahve right now -- linking to the wiki that then links to developer areas (possibly) is fine. We might think about moving the developer editions to SourceForge but maybe an additional step we don't need. ok for this, see below... On 11/11/2012 04:22 AM, Andrea Pescetti wrote: On 09/11/2012 jan iversen wrote: Well I might have misunderstood it, but when I do a build --all, I end up with packages that I can install (at least for ubuntu), and they do not seem so different from an official release package ? We have two different kinds of builds, the OpenOffice builds and the OOo-Dev builds. See the note in red at https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds (they are also called with/without system integration respectively). OK, I see this note and I confess I don't pay much attention to it, and typically install in parallel for these. But, I keep the same user profile if you will, and this doesn't seem to cause problems for me. Right now this note says: This week's builds are built without system integration. Is the the normal? If it is, maybe we could just omit the explanations altogether so as not to confuse anyone. And as I understand it, snapshot build (which is also a kind of developer version) is made like an installation. The package layout does not change, but the idea is that an OOo-Dev build (and 350m1, the one at the URL above, is an OOo-Dev build) can be installed alongside an existing version of OpenOffice, so you can install it on your machine and keep running your stable OpenOffice together with it. This makes it ideal for testing. In the case of an OpenOffice build, you can still do the same, but it's a bit trickier, like needing to use setup /a on Windows (again, see the page and linked resources for all details). Regards, Andrea. -- MzK “How wrong is it for a woman to expect the man to build the world she wants, rather than to create it herself?” -- Anais Nin
Re: [DISCUSS] Do we want download links for Dev Builds on a usual webpage?
On Fri, Nov 9, 2012 at 3:55 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Hi all, a quick question as I don't know the status of this request: Do we (still) want to have download links for Dev Builds that refer to the respective people's dir? IMHO we don't want pages in www.openoffice.org/dowload/* to point to anything other than actual releases. Links from Dev, L10n or QA pages are fine. Then I would create a webpage that can be included in the usual download website - as it was in the former times with OOo. At the moment there is just a link to the Wiki page. Marcus
Re: [DISCUSS] Do we want download links for Dev Builds on a usual webpage?
Hi. In order to make life easier (more stable) for translators, I think it would be a good idea to isolate developer builds on dev. When we have langauge packs integrated, then we could point to them from l10n, with a thick note, stating they are only there for testing the language. In order to make sure they dont get distributed as released, would it be an idea (and is it possible) to e.g. disable the actual save (not the button, but the final write call). With such a feature anybody can test (which is the purpose) but it cannot be used as a product. Jan. On 9 November 2012 22:05, Rob Weir robw...@apache.org wrote: On Fri, Nov 9, 2012 at 3:55 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Hi all, a quick question as I don't know the status of this request: Do we (still) want to have download links for Dev Builds that refer to the respective people's dir? IMHO we don't want pages in www.openoffice.org/dowload/* to point to anything other than actual releases. Links from Dev, L10n or QA pages are fine. Then I would create a webpage that can be included in the usual download website - as it was in the former times with OOo. At the moment there is just a link to the Wiki page. Marcus
