Re: Fwd: jessie backport for Wordpress
On Wed, Jun 17, 2015 at 05:56:48PM +0100, Rodrigo Campos wrote:
> On Fri, Jun 12, 2015 at 04:17:14PM +0100, Rodrigo Campos wrote:
> > On Fri, Jun 12, 2015 at 09:03:05PM +1000, Craig Small wrote:
> > > On Wed, Jun 10, 2015 at 04:25:19PM +0100, Rodrigo Campos wrote:
> > > > > Craig, the backports team will feel more comfortable if the backport does not
> > > > > depend on only one person, and it would be best if someone in the regular
> > > > > package maintenance is involved too.
> > > > >
> > > > > My plan, of course, is to do the backport in a timely fashion. Where I work we
> > > > > are using it for a whole site (not just as a blog) in production, so of
> > > > > course my plan is not to disappear. But, would you like to take care of it in
> > > > > the unlikely case I "disappear"?
> > > > >
> > > > > I can continue to provide a backport even if I change my job. When jessie
> > > > > becomes oldstable, as I tend to upgrade the servers quickly, I will not have
> > > > > where to test it, though.
> > > >
> > > >
> > > > Ping Criag?
> > > I'm happy to work with Rodrigo or others on the backports. I think
> > > there has been confusion about what the current state of the various
> > > versions of wordpress but the more the merrier I think.
> >
> > Great, thanks! I've created the package with cowbuilder, just added myself to
> > the Uploaders field in debian/control and added a changelog entry with "dch
> > --bpo".
> >
> > Any comments on the package ? Or is it ready for inclussion in jessie backports ? :)
> >
> > I'm using it in production without any problems :)
>
> Ping ?
>
> Not sure what the next step should be. Craig ? Rhonda ?
Sorry to disturb again. But is there a concensus to accept a WP package in
backports ?
If so, what is the next step ? Is the current package I did not following some
desired rule or something ?
Thanks a lot,
Rodrigo
Reply to: