[sldev] Fixed Internally resolution.

Soft soft at lindenlab.com
Mon Jul 28 08:52:02 PDT 2008


If the release notes for each server or viewer release could include a
list of merged branches, volunteers would have enough information to
close or reopen fixed-internally issues on their own.

On Fri, Jul 25, 2008 at 4:07 PM, Joshua Bell <josh at lindenlab.com> wrote:
> This should be indicated by setting the Fix Version as soon as it's in an
> RC. No Fix Version should imply that it's not folded into any particular
> release yet. That's how we track fixes internally.
>
> Odds are there will be some lag, since correct representation of issue
> status in JIRA is important but not a blocker for releases.
>
> (Once I get that cloning machine up and running for my team, though...)
>
> Matthew Dowd wrote:
>>
>> Is it possible to (easily) distinguish between a "fixed pending" which is
>> in the RC cycle, and a "fixed pending" which is still in some internal
>> branch yet to be folded into the RC cycle at some  as yet undecided stage?
>> Matthew
>>
>>
>> > Date: Thu, 24 Jul 2008 15:54:44 -0700
>> > From: ramzi at lindenlab.com
>> > To: monkowsk at watson.ibm.com
>> > Subject: Re: [sldev] Fixed Internally resolution.
>> > CC: sldev at lists.secondlife.com; rdw at lindenlab.com
>> >
>> > Yes, it's probably not being applied well uniformly. Another wrinkle is
>> > that the reporter may Resolve/Close the issue of their own accord, the
>> > very moment that a fix appears in an RC build. (Mike- I think this
>> > explains much of that number.)
>> >
>> > 1. My operative has been to set the status as (still) "Fixed Pending"
>> > while the fix is propagating through the RC cycle. (Depending on the
>> > person changing it, only some of these have their 'Fix Version' is set
>> > too.)
>> > 2. When the bug fix appears in an official viewer (to ALL residents),
>> > its status can be moved to "Fixed." (And if it has no Fix Version at
>> > this point, I'm sure to set it then.)
>> >
>> > With the official release of viewer 1.20 today, it was on my list to
>> > move Fixed Pending->Fixed for the tasks in the 1.20 release notes. I
>> > just accomplished this, but the delta was only 28 issues from their
>> > status as of this morning... So I may not have made such a big dent in
>> > the number Jason mentions at the top of the thread.
>> > -Ramzi
>> >
>> >
>> > Mike Monkowski wrote:
>> > > I don't think that's being done uniformly. There are 166 VWR bugs
>> > > with Fix Version "1.20 Release Candidate". Only six of those have
>> > > Status "Fix Pending".
>> > >
>> > > Mike
>> > >
>> > >
>> > > Ryan Williams (Which) wrote:
>> > >> Jason Giglio wrote:
>> > >>
>> > >>> "Fixed Internally" number is ballooning again. Is there a process to
>> > >>> reconcile shipped code?
>> > >>>
>> > >>> Is code that is released in a RC branch considered fixed, or fixed
>> > >>> internally?
>> > >>
>> > >> I've been treating RC as fixed internally. Perhaps that's wrong?
>> > > _
>> >
>> > _______________________________________________
>> > Policies and (un)subscribe information available here:
>> > http://wiki.secondlife.com/wiki/SLDev
>> > Please read the policies before posting to keep unmoderated posting
>> > privileges
>>
>> ------------------------------------------------------------------------
>> Get Hotmail on your Mobile! Try it Now!
>> <http://clk.atdmt.com/UKM/go/101719965/direct/01/>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/SLDev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting
> privileges
>


More information about the SLDev mailing list