So what does "version58 mean?"  Where did that come from?

If it is fixed in another build, how is that identified?

I can make it up too.  It doesn't help for collaborative understanding.

I don't care what the scheme is, so long as I can find out what it is and 
follow it.  I mainly don't want to waste mine or anyone else's time retesting 
and also have devs to be able to tell if something is against something already 
repaired later.

(I am not talking about CTR/JFDI versus RTC, I am seeking something that can be 
consistently relied upon, that's all.)

 - Dennis

-----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

-- 
/tj/

Reply via email to