[EMAIL PROTECTED] wrote:
The discussion has shown that
- only formal releases (beta or not) can be exposed to users
Only formal releases can be promoted on the project website, which is
the first place that users look for downloads.
Unless I'm mistaken (anybody feel free to correct me), the goal is to
protect users from naively using (and putting into production) a product
that has not been approved by the PMC.
I see no problem with inviting users to participate in the testing of a
release candidate. Perhaps a good way to handle this might be a post to
derby-user saying "Derby developers are testing a release candidate for
10.4 and we invite you to participate. If you're interested, more
information is available on derby-dev, see <url to derby-dev post>.
Please join us there."
That invites users to consciously test a release candidate, and pulls
them into the derby-dev side.
does anyone see any problems with this approach?
-jean
- releases can only be made formal through a vote
- a vote requires a minimum of 7 days to complete
The current plan is to spin a non-beta release candidate on 2008-04-04
(next Friday) which is only 7 days away, so it does not make much sense to
call for a vote on the beta now.
I plan to keep the beta unofficial with the the disclaimer on the Wiki.
