Re: [PEPr] +1 for Structures::DataGrid

On 8 Mar 2004 at 12:51, Andrew S. Nagy wrote: > Jean-Michel Poure wrote: > > Le Friday 05 March 2004 10:08, PEPr a écrit : > > > >>Proposal information: > >>http://pear.php.net/pepr/pepr-proposal-show.php?id=26 > >>Vote information: > > >>>>http://pear.php.net/pepr/pepr-vote-show.php?id=26&handle=neufeind > > > > > > Great proposal. I have been using http://www.phplens.com > > for a long > > time now and was looking for a replacement with access to source > > code. > > > > When can we start using the grid in PEAR? > > > > As soon as it is marked as approved by the PEAR QA Team I guess. > > Actually, I was wondering this myself, can any let me know what > happens after the voting process? After a successful voting you may create the package on the PEAR website and upload a first release. However, please note that a first release should be in state "alpha" or even "devel". > > Many of us would be delighted to add features. > > What is your roadmap for the grid? > > The datagrid is fully functioning however it needs more indepth > testing. > Once it is accepted, I plan on releaseing it as beta to receive > feedback and testing. I would love to have other contribute and work > on it along with me! If you say that you would like others to contribute etc. then maybe work is not really finished from your side? In that case a release as state "devel" would be the way to go. Otherwise, if you feel the package is already in a "good" condition (that's up to you to decide) you might also go for an alpha-release. However, be sure to move on to beta-state *only* when the API is fixed and there are hopefully just quite a few bugs still in the package. But no API breaks or big changes / improvements should be done in beta (small improvements inside the package are surely okay ... but don't plan to do too much once a package is beta). Beta means "almost finished, please test". The latest step would then be to go for a "RC1" (release candidate). Normally this should be the version as you would normally want to release it. A RC is currently still defined with a state of "beta" (we're currently talking about adding a separate RC-state and if this is necessary). So usually expect to release exactly the same package (with only changed version number and packaged again) that you released as RC1 a short while after as the final package. Hope this explanation helped you a bit. Otherwise, please refer to the PEAR manual and feel free to ask again on the mailinglist. Regards, Stefan