George Niculae
2012-10-22 14:30:50 UTC
If you're reading this email, then chances are there's a subset of
features in sipxecs that are critical for you in sipXecs. The scope
of features in sipXecs is enormous and eZuce engineering is crowd
sourcing an effort to ensure 4.6 is a rock solid release. The 4.6
release has been delayed mostly because we're finding release blockers
bugs at a slower pace then we'd like largely due to the scope of 4.6
and the amount of changes that went into 4.6 release.
We could use your help on these two fronts:
1.) Help generating a functional test coverage list
2.) Help testing against this coverage list (or documenting that
you've already recently tested these areas)
For the functional test coverage list, we've started the process by
creating this document
https://docs.google.com/spreadsheet/ccc?key=0Am3t0sbUXCjsdFlYUWRiZnlmc2VkZzYwQ05YMFBHX2c
While the document is getting flushed out, testing can get started.
Test results will be recorded in this document.
NOTES:
1.) It's fine to discuss missing features you think of on the mailing
list, but try to keep that discussion separate from 4.6 release
process. i.e. we're not considering adding features to 4.6
2.) Just because you find a bug doesn't mean it will be fixed in 4.6.
We're only fixing release stoppers. We will consider each bug again
for each update to 4.6 however.
3.) This is similar to an approach we did for release 4.4 and we
should have started this approach for release 4.6 months ago. My
apologies for not doing so.
4.) If you're using OpenUC (eZuce's commercial derivative of sipXecs)
you can still report testing results that affect sipXecs. If you're
not sure if a feature is specific to OpenUC, just ask any eZuce
employee and we'll get you the answer.
Thanks
features in sipxecs that are critical for you in sipXecs. The scope
of features in sipXecs is enormous and eZuce engineering is crowd
sourcing an effort to ensure 4.6 is a rock solid release. The 4.6
release has been delayed mostly because we're finding release blockers
bugs at a slower pace then we'd like largely due to the scope of 4.6
and the amount of changes that went into 4.6 release.
We could use your help on these two fronts:
1.) Help generating a functional test coverage list
2.) Help testing against this coverage list (or documenting that
you've already recently tested these areas)
For the functional test coverage list, we've started the process by
creating this document
https://docs.google.com/spreadsheet/ccc?key=0Am3t0sbUXCjsdFlYUWRiZnlmc2VkZzYwQ05YMFBHX2c
While the document is getting flushed out, testing can get started.
Test results will be recorded in this document.
NOTES:
1.) It's fine to discuss missing features you think of on the mailing
list, but try to keep that discussion separate from 4.6 release
process. i.e. we're not considering adding features to 4.6
2.) Just because you find a bug doesn't mean it will be fixed in 4.6.
We're only fixing release stoppers. We will consider each bug again
for each update to 4.6 however.
3.) This is similar to an approach we did for release 4.4 and we
should have started this approach for release 4.6 months ago. My
apologies for not doing so.
4.) If you're using OpenUC (eZuce's commercial derivative of sipXecs)
you can still report testing results that affect sipXecs. If you're
not sure if a feature is specific to OpenUC, just ask any eZuce
employee and we'll get you the answer.
Thanks