Re: VOTE JCS RELEASE [3 days, ends 8/25 midnight EST]

[Martin van den Bemt <ml...@mvdb.net>]

Can we do anything with Apachecon regarding the release, or aren't you going to make that ?

Mvgr,
Martin

Aaron Smuts wrote:
> I would like to hold a vote for a JCS release.  The
> previous vote was all in favor but it was mismanaged. 
> Please take the time to vote again.
> 
> Just recently, there have been several significant
> improvements.  Most notably the Indexed Disk Cache has
> in place optimization, the MySQL Disk Cache has
> scheduled optimization, and the remote cache has
> Zombie queuing.  There have been several other bug
> fixes.  
> 
> We have come to embrace JIRA for bug tracking and we
> are trying to get the test coverage up.  The live
> coverage is now above 54% and the branch coverage is
> significantly higher.
> 
> All of the major auxiliaries are in heavy production
> use.  At Travelocity alone we use every plugin.  The
> remote cache server is used in cluster mode backed by
> the MySQL Disk Cache and receives over 15 million
> insertions a day.  The Indexed Disk Cache is receiving
> hundreds of millions of retrievals a day.. . . .
> 
> The code is stable.  The features are rich.  We have a
> great bug tracking system in place.  And the code is
> production hardened in one of the world's biggest
> ecommerce sites.  
> 
> It's time for a formal release.  Please reply with
> your +1 to release what is in head as JCS 1.3.0.
> 
> Cheers,
> 
> Aaron Smuts
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org

Re: VOTE JCS RELEASE [3 days, ends 8/25 midnight EST]

[Martin van den Bemt <ml...@mvdb.net>]

You have all the votes in place and if I recall correctly also some pointers (in the release 
threads) to how to release it. A good thing would be to create the release, let others have a quick 
look at to see if something is missing and then make it official :)

One tip : don't drown :)

Mvgr,
Martin

Aaron Smuts wrote:
> I have a tag.  In fact head is so close, with just a
> simple bug fix, I may cut another.  I just need to
> figure out exactly what needs to be done to formally
> release the jar.  I've been under water recently . . .
> 
> --- Martin van den Bemt <ml...@mvdb.net> wrote:
> 
>> Can we do anything with Apachecon regarding the
>> release, or aren't you going to make that ?
>>
>> Mvgr,
>> Martin
>>
>> Aaron Smuts wrote:
>>> I would like to hold a vote for a JCS release. 
>> The
>>> previous vote was all in favor but it was
>> mismanaged. 
>>> Please take the time to vote again.
>>>
>>> Just recently, there have been several significant
>>> improvements.  Most notably the Indexed Disk Cache
>> has
>>> in place optimization, the MySQL Disk Cache has
>>> scheduled optimization, and the remote cache has
>>> Zombie queuing.  There have been several other bug
>>> fixes.  
>>>
>>> We have come to embrace JIRA for bug tracking and
>> we
>>> are trying to get the test coverage up.  The live
>>> coverage is now above 54% and the branch coverage
>> is
>>> significantly higher.
>>>
>>> All of the major auxiliaries are in heavy
>> production
>>> use.  At Travelocity alone we use every plugin. 
>> The
>>> remote cache server is used in cluster mode backed
>> by
>>> the MySQL Disk Cache and receives over 15 million
>>> insertions a day.  The Indexed Disk Cache is
>> receiving
>>> hundreds of millions of retrievals a day.. . . .
>>>
>>> The code is stable.  The features are rich.  We
>> have a
>>> great bug tracking system in place.  And the code
>> is
>>> production hardened in one of the world's biggest
>>> ecommerce sites.  
>>>
>>> It's time for a formal release.  Please reply with
>>> your +1 to release what is in head as JCS 1.3.0.
>>>
>>> Cheers,
>>>
>>> Aaron Smuts
>>>
>>>
>>>
> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>> jcs-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>> jcs-dev-help@jakarta.apache.org
>>>
>>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-dev-help@jakarta.apache.org
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org

Re: VOTE JCS RELEASE [3 days, ends 8/25 midnight EST]

[Aaron Smuts <as...@yahoo.com>]

I have a tag.  In fact head is so close, with just a
simple bug fix, I may cut another.  I just need to
figure out exactly what needs to be done to formally
release the jar.  I've been under water recently . . .

--- Martin van den Bemt <ml...@mvdb.net> wrote:

> Can we do anything with Apachecon regarding the
> release, or aren't you going to make that ?
> 
> Mvgr,
> Martin
> 
> Aaron Smuts wrote:
> > I would like to hold a vote for a JCS release. 
> The
> > previous vote was all in favor but it was
> mismanaged. 
> > Please take the time to vote again.
> > 
> > Just recently, there have been several significant
> > improvements.  Most notably the Indexed Disk Cache
> has
> > in place optimization, the MySQL Disk Cache has
> > scheduled optimization, and the remote cache has
> > Zombie queuing.  There have been several other bug
> > fixes.  
> > 
> > We have come to embrace JIRA for bug tracking and
> we
> > are trying to get the test coverage up.  The live
> > coverage is now above 54% and the branch coverage
> is
> > significantly higher.
> > 
> > All of the major auxiliaries are in heavy
> production
> > use.  At Travelocity alone we use every plugin. 
> The
> > remote cache server is used in cluster mode backed
> by
> > the MySQL Disk Cache and receives over 15 million
> > insertions a day.  The Indexed Disk Cache is
> receiving
> > hundreds of millions of retrievals a day.. . . .
> > 
> > The code is stable.  The features are rich.  We
> have a
> > great bug tracking system in place.  And the code
> is
> > production hardened in one of the world's biggest
> > ecommerce sites.  
> > 
> > It's time for a formal release.  Please reply with
> > your +1 to release what is in head as JCS 1.3.0.
> > 
> > Cheers,
> > 
> > Aaron Smuts
> > 
> > 
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jcs-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> jcs-dev-help@jakarta.apache.org
> > 
> > 
> > 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-dev-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org