Re: Problem releasing File_Find

Helgi Þormar wrote:

On Wed, 2004-12-15 at 13:06, Mika Tuupola wrote:

I just tried to upload a new release of File_Find which i gave the version number 0.3.0. The problem is File_Find is an old package created before the new rules and it was already marked as stable by Sterling. I would not like to bump the version number to 1.0.0 yet since there are a couple of things I'd like to change first (such as get rid of the non-standard FileFindException extends PEAR_Error error handling). The question is. Should i release it as File_Find 0.3.0 beta, which allow me to make the small BC break regarding the error handling later?

*sigh* I thought that thing was made with the grandfather rule in mind ... but yes release it as beta I'd say... IMHO in cases like this a BC should be okey, but well I doubt some other people would like that.

I could modify the code to check the latest stable and if it is < 1.0 ignore any version mods, if you would like. I thought the whole point was to make all future releases conform to the versioning? If things need to be changed in old packages, I would say it isn't truly stable, but I would be speaking hypothetically, of course. The users of File_Find would probably disagree with me. Greg