Hi everyone,
We would like the release branches which are automatically created (such as
REL1_25) for our extensions to point to the most recent stable version of
our code available. Would it cause problems if we were to simply update
(likely a fast forward merge) those branches ourselves as
Great! Thank you so much!
Kevin
On Thu, Oct 15, 2015 at 10:21 AM, Chad wrote:
> As long as the branch still works with that given MW then go for it.
>
> -Chad
>
> On Thu, Oct 15, 2015, 5:10 AM Kevin Ji wrote:
>
> > Hi everyone,
> >
> > We would
As long as the branch still works with that given MW then go for it.
-Chad
On Thu, Oct 15, 2015, 5:10 AM Kevin Ji wrote:
> Hi everyone,
>
> We would like the release branches which are automatically created (such as
> REL1_25) for our extensions to point to the most
There should probably be a bug raised in Phab about this.
On 16 October 2015 at 03:25, Bartosz Dziewoński wrote:
> On 2015-10-14 16:44, shirish wrote:
>
>> Hi all,
>>
>> A temporary way to generate Table of Contents (TOC) is to write
>> __FORCETOC__ or _TOC_ before starting
On 2015-10-14 16:44, shirish wrote:
Hi all,
A temporary way to generate Table of Contents (TOC) is to write
__FORCETOC__ or _TOC_ before starting the page but what if we don't want
that. Let's say we want to have all and any pages that has more than 2
sections should have a TOC. Is there a way
Hi all,
Tomorrow we will be issuing a security release to all supported
branches of MediaWiki.
The new releases will be:
1.25.3
1.24.4
1.23.11
Fixes will be available in these respective release branches, the
unreleased 1.26.x branch, and master. Tarballs will be available
for the above