[glotpress-updates] [GlotPress] #283: Don't use BackPress as an external

GlotPress noreply at wordpress.org
Tue Feb 25 22:03:07 UTC 2014

#283: Don't use BackPress as an external
  Reporter:  markoheijnen  |      Owner:
      Type:  enhancement   |     Status:  reopened
  Priority:  normal        |  Milestone:
 Component:  general       |    Version:
Resolution:                |   Keywords:  dev-feedback
Changes (by markoheijnen):

 * status:  closed => reopened
 * resolution:  invalid =>


 I'm reopening this because this isn't something that can be closed in 5
 minutes. I need a better solution then this to make GlotPress more stable.
 So that means that the current committers need to merge the fixes from
 WordPress to BackPress or give me commit access. And from last time, the
 latter option is not going to happen.

 I'm currently thinking about to copy/paste the unit tests from WordPress
 into a BackPress folder to make it more clear which tests are failing for
 code that GlotPress uses. This is something we should not have to do since
 it's an external library but I guess on the other side it does make sense.
 I would love to see failing tests when something gets broken.

Ticket URL: <https://glotpress.trac.wordpress.org/ticket/283#comment:5>
GlotPress <https://glotpress.trac.wordpress.org>
Easy comin', easy goin'

More information about the glotpress-updates mailing list