Hello!
On Sun, May 18, 2014 at 12:09 AM, Tatsuhiko Kubo wrote:
> Before OpenResty project provided two releases(mainline and stable) as far
> as I remember.
> But it seems that a single Latest release and Legacy releases are provided
> now.
>
OpenResty now no longer distinguishes formal releases via the
"mainline" and "stable" categories. Now there is only "formal
releases". (In the past, "mainline" releases were not considered
"unstable" at all while "stable" releases often contain known bugs
because they almost always lagged behind the latest "mainline" release
quite a bit. So it was quite a burden for me without real gains.)
Before each formal release, several release candidates are announced
for community testing, like RC1, RC2, and etc.
> Should we use Latest release basically?
Yes.
Before each formal release is out (and even each RC release), it is
usually deployed to CloudFlare's global network. So formal releases
are considered stable enough for production use.
> And when should we use Legacy
> release?
>
When the latest formal release contains some regressions that have not
yet been fixed or some of your own 3rd-party modules require older
nginx cores' API. But for the former, it's recommended to report the
issue here so that I can fix it as soon as possible :)
Best regards,
-agentzh
