|
|
| Author |
Message |
|
| Guest |
 Posted: Sun Oct 18, 2009 9:01 pm |
 |
|
|
Guest
|
Hi all!
Here are a few FAQs for you:
Why are all the releases of RabiitMQ "beta"?
What does "beta" mean in this context?
Should I NOT use RabbitMQ in a production environment?
What are the criteria for a "final" release of RabbitMQ?
Feel free to answer directly or post a link |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Oct 18, 2009 9:17 pm |
|
|
|
Guest
|
Uwe
Great questions. We seek advice on how to make this clearer. Please
take a look at this first, and let us know what you think:
http://www.trapexit.org/forum/viewtopic.php?p=49591&sid=20d06e54360b9122cd625eb6e459cfeb
alexis
On Sun, Oct 18, 2009 at 10:00 PM, Uwe Kubosch <uwe@datek.no> wrote:
> Hi all!
> Here are a few FAQs for you:
> Why are all the releases of RabiitMQ "beta"?
> What does "beta" mean in this context?
> Should I NOT use RabbitMQ in a production environment?
> What are the criteria for a "final" release of RabbitMQ?
> Feel free to answer directly or post a link |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Oct 20, 2009 7:17 am |
|
|
|
Guest
|
Hi Alexis!
Thank you for the quick reply.
My initial thoughts:
'beta' implies 'unfinished' and 'unstable'
'release candidate' better reflects your description of the status of the release.
Make an event of declaring a release "final", and announce this event in the initial release announcement. |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Oct 21, 2009 7:23 pm |
|
|
|
Guest
|
Uwe
We are still discussing this. The current proposal we are looking at,
is to radically simplify the release status descriptions. We may
provide an orthogonal statement concerning 'which version to use' that
politely explains that each release - while QAd to a high standard -
is still ipso facto novel, in order to ward conservative adopters off
being among the very first to use it.
alexis
On Tue, Oct 20, 2009 at 8:16 AM, Uwe Kubosch <uwe@datek.no> wrote:
> Hi Alexis!
> Thank you for the quick reply.
> My initial thoughts:
> 'beta' implies 'unfinished' and 'unstable'
> 'release candidate' better reflects your description of the status of the
> release.
> Make an event of declaring a release "final", and announce this event in the
> initial release announcement. |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
