AFAIK, the code seems to be ready for this. 

Re: alpha / beta

The side of me that knows what great work Thomas F has done says:  Yes, the 
features/code quality is beta ready.  It will not be unstable, which alpha 
implies, and is close to feature complete.  In addition, more folks will 
probably be willing to start testing with this if it's beta..

The semantic side says:  This should be alpha because it needs to be tested by 
others and there may be a few more features/missing 3.x capabilities that come 
out of this.  And that is the definition of alpha.

That said, I'm leaning towards calling it a beta release... as long as missing 
3.x capabilities requests that could come out of others testing it are 
considered before RC1/beta2.

Greg

-----Original Message-----
From: Thomas Fox [mailto:[email protected]] 
Sent: Sunday, May 13, 2012 4:29 AM
To: [email protected]
Subject: ready for 4.0-alpha1 ?


Hi,

I am wondering whether we are ready for an alpha1 release of Torque 4.
Personally, my impression is that there are the following open points
- check whether the TORQUE-177 implementation is ok
- Decide whether we still need SummaryHelper and CountHelper
- Build process needs to be updated (current build installs also tars and zips 
to the maven repo)
- documentation needs to be revised(needs this to be complete before alpha1 
release ?)

Perhaps you have other open points. I will be offline for 2-3 weeks from the 
middle of next week on, so there's some time to check for other open issues

     Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

DukeCE Privacy Statement:
Please be advised that this e-mail and any files transmitted with
it are confidential communication or may otherwise be privileged or
confidential and are intended solely for the individual or entity
to whom they are addressed. If you are not the intended recipient
you may not rely on the contents of this email or any attachments,
and we ask that you please not read, copy or retransmit this
communication, but reply to the sender and destroy the email, its
contents, and all copies thereof immediately. Any unauthorized
dissemination, distribution or copying of this communication is
strictly prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to