+1 for clarifying. We're not dropping support for 1.2.1 yet, but (and obviously) the support will manifest as a fix in 1.2.3 (etc).
B. On 12 April 2013 09:14, Noah Slater <[email protected]> wrote: > Thinking about this, we might want to clarify the difference between a > release not being supported, and a release being archived. Obviously, it > makes no sense to keep around two bugfix versions of the same minor release > line. (In this case, 1.2.1 and 1.2.2.) But 1.2.1 was released in January, > so I think we'll probably want to "support" it for 12 months, as we've > previously discussed. I am not exactly sure what "support" means in this > context. I guess when we talk about supporting releases, what we actually > mean is that we support major/minor release lines. So, in this case, we > "support" 1.2.x, in so much as we will continue to apply bugfixes to that > branch. > > Do I have this right? (I will update the current release page and my email > template if I get confirmation.) > > > On 12 April 2013 13:58, Noah Slater <[email protected]> wrote: > >> Dear community, >> >> I would like to archive Apache CouchDB 1.2.1 >> >> Reasons: >> >> * CouchDB 1.2.1 has been superseded by CouchDB 1.2.2 >> >> Archiving this release means that we no longer support it, and we will >> remove any references to it from our website and our wiki. However, the >> original files will still be available to anyone browsing the release >> archives. >> >> For more information, see: >> >> http://wiki.apache.org/couchdb/CurrentReleases#Archived_Releases >> >> You do not need to respond if you are in agreement. If there is no >> response in 72 hours, I will assume lazy consensus. >> >> If we reach consensus, I archive the release. >> >> Thanks, >> >> -- >> NS >> > > > > -- > NS
