On Fri, Jan 24, 2014 at 4:47 PM, Saint Germain <[email protected]> wrote:

> On Fri, 24 Jan 2014 16:19:47 -0800, Ryan Ollos
> <[email protected]> wrote :
>
> > On Fri, Jan 24, 2014 at 4:14 PM, Apache Bloodhound <
> > [email protected]> wrote:
> >
> > > #694: Translations scaffolding
> > > ------------------------+----------------------
> > >   Reporter:  olemis     |      Owner:  olemis
> > >       Type:  task       |     Status:  assigned
> > >   Priority:  minor      |  Milestone:
> > >  Component:  trac core  |    Version:  0.7.0
> > > Resolution:             |   Keywords:  i18n
> > > ------------------------+----------------------
> > >
> > > Comment (by SaintGermain):
> > >
> > >  Hello Olemis !
> > >
> > >  I agree that the patch can be included as it is, even if there is
> > > room for improvement.
> > >
> > >  As for the bugs you mentionned, I suppose that without any
> > > translation .po /.mo files, no one will see the bugs. ;-)
> > >
> > >  However I do not yet really understand how patch can or cannot be
> > > included (who can decide ?). So I am asking...
> > >
> > >  Thanks !
> > >
> >
> > A committer must decide. You've been invited to be a committer, so
> > one you complete the paperwork, then you will be able to push the
> > patch.
> >
> > Once you are a committer though, the general procedure for major
> > changes, and particularly for someone who is a new committer, is to
> > post the patch and wait a week or so for comments. If the feedback is
> > positive and you feel good about the patch, then you go ahead and
> > push it.
>
> Hello Ryan,
>
> Ok I have done the paperwork last thursday, so as soon as I got the
> rights I will do as you said.
>
> Thanks,
>

Would you kindly point me to where the latest proposed changes are staged?

Reply via email to