On Nov 19, 2012, at 5:12 PM, Daniel Kinzler wrote:
> On 19.11.2012 17:08, Jeroen De Dauw wrote:
>> +1. Having a script run that makes pretty arbitrary tags in between actual
>> releases for extensions that have real releases and associated
>> tags/branches does not seem helpful at all to me.
>
>
On 19.11.2012 17:08, Jeroen De Dauw wrote:
> +1. Having a script run that makes pretty arbitrary tags in between actual
> releases for extensions that have real releases and associated
> tags/branches does not seem helpful at all to me.
It is, however, extremely helpful for those extensions that d
Hey,
Extension maintainers should be able to decide when and where to
> branch. So that they don't have to backport changes just because
> someone at the foundation decided to branch all extensions.
>
+1. Having a script run that makes pretty arbitrary tags in between actual
releases for extensio
On Nov 8, 2012, at 11:08 PM, Tim Starling wrote:
> All extension branches were removed during the migration to Git. Very
> few extensions have branches for MW core major version support.
> There's no longer a simple way to branch all extensions when a core
> release is updated, and nobody has vol
On Thu, 2012-11-08 at 17:54 -0500, Chad wrote:
> On Thu, Nov 8, 2012 at 5:08 PM, Tim Starling wrote:
> > All extension branches were removed during the migration to Git. Very
> > few extensions have branches for MW core major version support.
> > There's no longer a simple way to branch all extens
Tim Starling wrote:
> All extension branches were removed during the migration to Git. Very
> few extensions have branches for MW core major version support.
> There's no longer a simple way to branch all extensions when a core
> release is updated, and nobody has volunteered to write a script.
9 Ноябрь 2012 г. 2:52:54 пользователь Daniel Friesen
(dan...@nadir-seen-fire.com) написал:
On Thu, 08 Nov 2012 14:08:53 -0800, Tim Starling
wrote:
> All extension branches were removed during the migration to Git. Very
> few extensions have branches for MW core major version support.
> T
On Thu, Nov 8, 2012 at 5:08 PM, Tim Starling wrote:
> All extension branches were removed during the migration to Git. Very
> few extensions have branches for MW core major version support.
> There's no longer a simple way to branch all extensions when a core
> release is updated, and nobody has v
On Thu, 08 Nov 2012 14:08:53 -0800, Tim Starling
wrote:
All extension branches were removed during the migration to Git. Very
few extensions have branches for MW core major version support.
There's no longer a simple way to branch all extensions when a core
release is updated, and nobody has
On 09/11/12 09:43, Platonides wrote:
> It's easy to make a script which creates such branch for each extension,
> but I'm not convinced that's the right thing to do.
>
> Also, did we make Extension:Distributor properly support branches on git
> extensions?
No.
https://bugzilla.wikimedia.org/show
It's easy to make a script which creates such branch for each extension,
but I'm not convinced that's the right thing to do.
Also, did we make Extension:Distributor properly support branches on git
extensions?
In an ideal world we would have perfect tests for all extensions, and
jenkins could aut
All extension branches were removed during the migration to Git. Very
few extensions have branches for MW core major version support.
There's no longer a simple way to branch all extensions when a core
release is updated, and nobody has volunteered to write a script.
So we're back to the situation
12 matches
Mail list logo