Re: Release 2.12 - 3.0
> Having a nifty new software version with potential bugs is not unique to
> our
> software project. Let's do what other projects do: say "Here's the new
> version. It's in beta. It has a lot of new features, but may have new
> bugs. Please test". That way we're not releasing with a known nasty bug,
> but we're not shutting off access to an already wildly improved next
> release.
What would be point of that? Do we absolutely have to do a release? Just
wait a month to test Matt's new code and release it then. It's either a
RELEASE or it's BETA. It's not the worst thing to happen to a project to
have to delay a release because of a known bug.
討論串 (同標題文章)
完整討論串 (本文為第 16 之 19 篇)：