Version lifecycle/bn

মিডিয়াউইকি একটি "continuous integration" ডেভেলপমেন্ট মডেলে কাজ করে, যেখানে সফ্টওয়্যার পরিবর্তনগুলি নিয়মিতভাবে উইকিমিডিয়া ওয়েব সাইট যেমন উইকিপিডিয়াতে সরাসরি ঠেলে দেওয়া হয়।

তাত্ত্বিকভাবে, নতুন বড় রিলিজগুলি অর্ধ-বছরের ভিত্তিতে জারি করা হয় এবং রিলিজ শাখাগুলি প্রথম প্রকাশের হিসাবে এক বছর পর্যন্ত নিরাপত্তা আপডেটগুলি পেতে থাকে। সময়ের সীমাবদ্ধতা এবং কোড বেসের দ্রুত রিফ্যাক্টরিংয়ের কারণে, আমরা অপ্রচলিত রিলিজগুলিকে চিরতরে সমর্থন করতে পারি না, এবং সুরক্ষা এবং সমালোচনামূলক আপডেটগুলি সেই রিলিজে প্রয়োগ করা হয় না যেগুলি তাদের জীবনের শেষ অবস্থায় পৌঁছেছে।

রিলিজ ম্যানেজার দৃঢ়ভাবে সুপারিশ করেন যে উইকি অপারেটররা  মেইলিং লিস্টে সাবস্ক্রাইব করুন, যা সমস্ত রিলিজের বিজ্ঞপ্তি পায় এবং নিশ্চিত করে যে তাদের উইকি সফ্টওয়্যারটির সর্বাধিক আপ টু ডেট সংস্করণ চালায়। এই ঘোষণা   এবং   পোস্ট করা হয়.

সংস্করণ এবং তাদের জীবনের শেষ
Versions included in the above table that are marked as obsolete as well as versions not listed at all will not receive any security fixes. They may contain critical security vulnerabilities and other major bugs, including the threat of possible data loss and/or corruption. The release manager has also issued a strong recommendation that only versions listed above as the current “stable version”, "legacy version" or “long-term support version” be used in a production environment.

Release policy

 * Every point release will include updated i18n files as well as any bug fixes. No new features will be back-ported to point releases and support does not necessarily include in general.
 * A major release will be made every six months.
 * A minor release (including security patches, message translation back-ports, and general bugfixes) will be made every quarter.
 * A long-term support release (LTS) will be made every two years. There will be a one-year overlap in LTS support. For example, 1.23 was supported until May 2017. 1.27 was released the year before, so that people have it available as an LTS to move to and a year to make the transition.
 * Release notes will continue to be the basis for seeing what has changed. Because of the nature of a volunteer-driven project, it isn't possible to say with any certainty what will happen in the next 6-12 months.

Release schedule
This timeline is a schedule for what needs to happen before the release of a new version. The date of the actual release is given here as T (for "time" of release) and the suffix -# (for “number of weeks prior to release”).

Extension lifecycle management
Most MediaWiki installations include a significant number of extensions (Wikimedia wikis often have around 140). Managing the maintenance bug fixing of extensions and choosing the right version of an extension in cases where the HEAD development version relies on features not yet available in stable or oldstable MediaWiki core, can be challenging.

Extension maintainers are therefore strongly encouraged to maintain a git branches for each extension version corresponding to a MediaWiki version. (See for details.) For extensions hosted in Wikimedia's git repos, such branches (with names such as  for MediaWiki 1.30) are created automatically from master when a new MediaWiki version is branched (on the assumption that the extension master is compatible with MediaWiki master at all times). However, it's preferable for the extension maintainer to fix bugs not only in HEAD but also in the oldstable and stable versions (by backporting the fix to the old branches if necessary).

The goal of these rules is that people or organizations installing MediaWiki can rely on installing the newest release of a version and matching extensions by a simple method, e.g. for 1.20.x core by referring to  in git. And it avoids tarballs and zip files with non-relevant and unpredictable names.

Since Version 1.36, MediaWiki only commits to supporting upgrades from two major long-term support releases (LTS) ago (see T259771). Upgrades from older versions of MediaWiki will have to be performed in multiple steps.