On 10/31/06, Dave <[EMAIL PROTECTED]> wrote:
I don't disagree with that, but I'll point out two issues in my mind:
1) we don't publicly announce the RC releases except here on the dev list
2) many other FOSS projects have releases in various stages of production
Regarding #1, should we make a bigger deal of our RC releases -- i.e.
blog about them and announce them on the Roller project blog?
It depends on how many folks you want to use them. I think Roller is
a bit different than most "libraries". It's unlikely you're going to
use Roller until there's an official release, because it's not
something you just download and upgrade - like you can with Spring or
Hibernate. For this reason, I don't think it gets a whole lot of
testing until there's a "real" release. AppFuse experiences the same
issue - that's why I typically don't do RCs or Betas, because I don't
think folks will use them. However, it is probably important to do
RCs for Roller because we are dealing with people's data and we don't
want to blow it away for any reason.
Matt
- Dave
On 10/31/06, Matt Raible <[EMAIL PROTECTED]> wrote:
> I think we should release 3.0, wait a day and then announce the 3.1
> RC. If we announce an RC for the next version before the previous
> version is released, my guess is it'll cause confusion.
>
> Matt
>
> On 10/31/06, Dave <[EMAIL PROTECTED]> wrote:
> > Now that we've branched, let's release an RC for 3.1.
> >
> > Any objections to doing that now?
> > Any fixes you want to get in before I do so?
> >
> >
> > - Dave
> >
>
>
> --
> http://raibledesigns.com
>
--
http://raibledesigns.com
