On Mon, May 18, 2015 at 10:12:21AM +0200, Raphael Hertzog wrote:
> On Sat, 16 May 2015, Craig Small wrote:
> > > I mean, instead of using 4.2.x to extract the patches and backport, isn't
> > > it
> > > easier to extract them from 4.1.x for stable ? Or just do a "new upstream
> > > release" based on 4.1.5 ?
> > The stable track is basically whatever version was there with security
> > patches so going to 4.1.5 isn't really an option. Again the 4.1.5
> > changesets use terrible comments.
>
> That's the general case. But with wordpress, the security team is rather
> open to integrate new upstream releases. We did it multiple times already.
Then, IMHO, using the new upstream release 4.1.5 is the best thing for stable.
And to do it like that until they drop support for 4.1.x seems reasonable IMHO.
What do you think, Craig ?
Also, Craig, if you want to continue the "cherry-pick" of patches way, I can
look at them if you need. I found an official git mirror at:
git://develop.git.wordpress.org/
The 4.1 branch there seems the best way to move the patches to quilt IMHO. But
I'm not sure how are you managing it now, are you backporting patches from 4.2.x
and 4.1.x? The debian changelog gives me that idea, but not sure. Can I ask
what are you
doing now ?
Thanks a lot,
Rodrigo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
