On 07/02/2011 12:05, ant elder wrote:
On Mon, Feb 7, 2011 at 8:51 AM, Simon Nash<n...@apache.org> wrote:
<snip>
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
I see, ok well i guess i'd be willing to give that a try. We've not
been very good at finding consensus in the past which is one of the
reasons we've ended up with this "anyone can do anything" approach so
i can see there may be problems, but it will be an interesting
experiment.
...ant
Folks,
Let me make a proposal that we can implement right now for Beta2.
Remove all samples from the build EXCEPT for the following, which we make work "out
of the box":
getting-started\helloworld-contribution
getting-started\helloworld-webapp
I think that for the moment, we can put in an HTML file which then points at all the other samples,
but back in the repo, with a brief explanation as to what they do and what they show.
Over time, we can add back more samples into the build, but only once they are
brought up to scratch.
Something we need to concentrate on is to make sure that any documentation is correct and especially
any suggested ways of running the samples actually work - at the moment, the READMEs for the
helloworld samples simply don't work if you follow the instructions in the READMEs.
I think that this minimal approach allows us to make quick progress while improving the experience
for end users.
Yours, Mike.
