From: "NARUSE, Yui" <naruse@airemix.jp>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:100310] Re: How to use backport custom field
Date: Tue, 6 Oct 2020 23:43:43 +0900 [thread overview]
Message-ID: <CAK6Hhspj4mpz_Q0J2Q9Xrm01nFaO-fOa1371gzNS3LA1n10MaA@mail.gmail.com> (raw)
In-Reply-To: <CAHE_3ChUwYj=2a02JDMw5Ek55116mCOisgkbf6w4u0J9wcO=WQ@mail.gmail.com>
"Backport custom field" is only available for tickets whose tracker is "Bug".
I added that description for HowToRequestBackport.
Could you check that?
If you still cannot use it, feel free to ask again.
Since you have enough knowledge and passion to use it, both you and we
will benefit from it.
2020年10月6日(火) 23:31 Jun Aruga <jaruga@redhat.com>:
>
> Please allow my ignorance.
> After years staying in the Ruby project, I am still not sure how to
> use the backport custom field.
> I can not find the custom field UI in my edit page.
> Is it related to a user account [1]'s permission?
> Anyone, could you guide me?
> Thank you.
>
> https://bugs.ruby-lang.org/projects/ruby/wiki/HowToRequestBackport
>
> > Backport custom field
> >
> > If you are expert CRuby developer, you can use Backport custom field.
> > The format of the field is \A(?<branch>\d\.\d(\.0)?: > (UNKNOWN|REQUIRED|DONE|DONTNEED|WONTFIX))(, \g<branch>)*\z.
> > This is useful when you know a ticket affect a released ruby, and note it on the ticket in machine readable format.
>
> [1] my account: https://bugs.ruby-lang.org/users/11018
>
> Thanks.
>
> --
> Jun | He - His - Him
>
>
> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
next prev parent reply other threads:[~2020-10-06 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 14:30 [ruby-core:100309] How to use backport custom field Jun Aruga
2020-10-06 14:43 ` NARUSE, Yui [this message]
2020-10-06 15:08 ` [ruby-core:100311] " Jun Aruga
2020-10-06 17:24 ` [ruby-core:100314] " NARUSE, Yui
2020-10-07 10:44 ` [ruby-core:100322] " Jun Aruga
2020-10-07 11:41 ` [ruby-core:100326] " NARUSE, Yui
2020-10-07 12:56 ` [ruby-core:100327] " Jun Aruga
2020-10-07 13:15 ` [ruby-core:100328] " NARUSE, Yui
2020-10-07 13:30 ` [ruby-core:100330] " Jun Aruga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK6Hhspj4mpz_Q0J2Q9Xrm01nFaO-fOa1371gzNS3LA1n10MaA@mail.gmail.com \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).