Am 12/26/2011 10:33 PM, schrieb Dennis E. Hamilton:
So what does "version58 mean?" Where did that come from?
This is the default value when you create new issues. Maybe an BZ admin
could change this to "OOo 3.3"?
If it is fixed in another build, how is that identified?
And if she/he is already working on it, please create a new item like
"AOO 3.4" or similar. "OOo 3.4 Beta" is out of the game and - with the
new nightly and dev builds - we need now a new version entry in that list.
Marcus
-----Original Message-----
From: TJ Frazier [mailto:[email protected]]
Sent: Monday, December 26, 2011 13:11
To: [email protected]
Subject: Re: Early User-QA Engagement (was RE: Ip Clearance: 1st version of Svg
replacement available)
On 12/26/2011 15:06, Dennis E. Hamilton wrote:
I think that is a good idea with regard to a lot of feature adjustments, and
especially the SVG one. It would be useful to blog or wiki both a view of how
it is brought along and a view of how folks can participate in confirming the
operation of features and other changes in these early technology builds.
Are bug reports going to be accepted against nightlies and technology/developer
builds that are now being made available to those who know where to find them?
There are the builds that Ariel has made and there are the builds that Raphael
makes available as well.
If so, how will they be identified? One suggestion is to use the latest SVN
update number applicable to the working copy when the build was made. That
seems like a simple enough procedure. There are recommendations for additional
details (such as a build date), but anything that gets us a non-decreasing
unique identifier between builds will work.
[ ... ]
Hi, Dennis,
For a peek at how the devs are JFDI, see:
https://issues.apache.org/ooo/show_bug.cgi?id=118698