Hi Jürgen, * On Mon, Oct 08, 2012 at 04:58:03PM +0200, Jürgen Schmidt wrote: > The build bots are still not build the same as we do for the binary > releases (please correct me if I am wrong). Means as long as we don't > have build bots which are building with the same configuration we should > provide the builds manually in the same way we did it for the release. > > @Ariel, would that be ok for you fro now until we have a better solution?
Yes, I will apply the set up described in https://issues.apache.org/ooo/show_bug.cgi?id=119385 , that is, decreasing Linux system requirements to glibc 2.5 Any one is welcome to take any of the two architectures (building on Linux is multiplied by 4: rpm/deb, 32 and 64 bits; this counts on building time and uploading the packages); if not, I will take care of both. > > I will take care of Windows and MacOS. > > > > (2) How many language support can we get for this milestone build? Not > > necessary to be 100% translated, but can be a base for volunteers to verify > > the translation. > > We should include the languages that we have released and add all > languages where we notice active volunteers who help us to support these > further languages (eg. Polish, Danish, Scots Gaelic, ...) > > > > (3) The current development snapshot naming [a] is a little confusing to > > me. I wonder if we can change the naming to reflect the date of the build? > > I am not sure if understand you correct. The revision is a unique > identifier and makes it clear what went in the snapshot. We probably > upload the builds not all on the same day. Means I am not sure how a > date can help here. I guess that besides the revision, milestone builds can be identified by their milestone number, which should be increased in every milestone build: AOO350m1 AOO350m2 etc just like in OOo times there was DEV300m105 DEV300m106 etc http://www.openoffice.org/development/releases/DEV300m106_snapshot.html it could start now from DEV350m1 Regards -- Ariel Constenla-Haile La Plata, Argentina
pgprRw7ua3bj9.pgp
Description: PGP signature
