ant elder wrote:
On Sun, Feb 6, 2011 at 10:36 PM, Simon Nash <n...@apache.org> wrote:
I do agree good quality samples are important for users though. Maybe
if we have this more strict quality approach then we also need to do
some vetting of what goes into samples so there isn't so many of them
and try to include just a few main ones in the releases, perhaps with
others available in SVN which we document as available?
...ant
That's exactly what I was suggesting. Quality is more important than
quantity. Let's be selective and only include samples in a release if
they are working and have some documentation saying how to run them.
For those that make the cut, I think there is a requirement to keep
them working in future releases (both major and minor), so let's make
the selection with that in mind.
That wasn't quite what i was suggesting, I meant a include only a
small and controlled set of samples of samples. I don't think it
scales with everyone able to add any old sample they happen to like
and have that require for ever more that it is manually reviewed by
everyone at every release time and any issues be release blockers.
...ant
I think we're in violent agreement here! Let's pick a small and
useful set of high-quality samples to include in the release, then
make sure (by automated tests as far as possible) that these samples
continue to work in future releases. All other samples would go
somewhere else in svn (unreleased/samples?) which would be much more
of a mixed bag. Newly created samples would be added to the mixed bag.
In future major releases, we could (if we want to) take carefully
chosen samples out of the mixed bag and "promote" them to be added
to the release. The reverse is also possible, where we could "retire"
a released sample that no longer seems to be serving much of a useful
purpose, by moving it from the released samples to the mixed bag.
Simon
