Hello

I'm new to Silverstripe and just checking its features and extensions.

The low version numbers for modules are worrying - for example: "Embargo & Expiry (v0.2)". When I see v0.2, I don't imagine that the code would be ready for the production environment - but as this seems like a fairly straightforward feature - and is on the 'official' modules page, I guess that it must be OK.

However, I cannot find any details about the module - testing, bugs etc.

So my question is - what should I think when I see v0.2?

I guess I'd like to see the numbering indicate how ready the module is for production use, and not how close it is to a full feature set.

Thanks

Thanks for the reply. I don't mean to pick on your very useful module - I'm just using it as an example. But to continue with that example - when you say

"The 0.2 status is because it isn't finished..."

where do I find out what is not finished?

From the point of view of a developer, v0.2 may make good sense - indicating that more is to come.

From the point of view of someone trying to evaluate Silverstripe and its modules, it does not build confidence in the product.

If (for example again) Embargo & Expiry works correctly - even with a small feature set - and is stable, has no major bugs etc., then I'd prefer to see it at v1.0.

One question about the comment about the patch - in the CHANGELOG for E&E v0.2 it says:

No longer needs patches as both have been commited to SS 2.2.2

- which is correct - patches needed or not?

Thanks

Martin

The version numbers are low because most modules are quite young - this might or might not correlate to their production usefulness, but is generally a good indicator.

> and is on the 'official' modules page, I guess that it must be OK.
Thats a misperception that we're just addressing (more on that soon) - not all modules that are listed on silverstripe.com are endorsed (or created/reviewed) by SilverStripe the company or the SilverStripe core team.