rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Gaynor <alex.gaynor@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Upstream Milestone
Date: Wed, 13 Jan 2021 09:09:22 -0500	[thread overview]
Message-ID: <CAFRnB2XcWKrPCBo04iVr9Z4xNvjMw8pFmqCkqB_xsaZJKc_CCw@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=Xh9vSf-pRFOZ73qqhZ9ushKfM1ei-0TqYxNfLyHJmow@mail.gmail.com>

I'm not quite sure how I missed the label... this milestone is clearly
duplicative, I'll remove it. I'll see if I can do something with the
labels to make them stick out more so I don't miss them!

Alex

On Wed, Jan 13, 2021 at 12:20 AM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Wed, Jan 13, 2021 at 3:42 AM Alex Gaynor <alex.gaynor@gmail.com> wrote:
> >
> > I wanted to flag for folks that I've created a milestone for us to
> > track things issues and PRs that we think "absolutely must be
> > completed before this can be submitted to upstream":
> > https://github.com/Rust-for-Linux/linux/milestones?with_issues=no
>
> Initially I did setup a couple milestones and played around with them,
> as well as with "Projects", but then after playing with things around,
> I found labels easier to manage and more powerful than milestones
> (colors, several "categories", several "states" per category, complex
> filtering, etc.).
>
> So, for instance, for the "priority" category, we have "required" and
> "optional", but one can add more states if needed (e.g. "TBD", "very
> low", etc.). To get the equivalent of a "milestone view", one can
> filter on Label.
>
> I am fine with going back to milestones if there is an advantage, but
> I didn't find it... I am curious what they are good for (perhaps to
> get that warm feeling of reading "we are at 90% completion!" ;-),
> which is basically an arbitrary number given how they work...).
>
> Cheers,
> Miguel



-- 
All that is necessary for evil to succeed is for good people to do nothing.

  reply	other threads:[~2021-01-13 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 21:12 Upstream Milestone Alex Gaynor
2021-01-13  5:20 ` Miguel Ojeda
2021-01-13 14:09   ` Alex Gaynor [this message]
2021-01-13 14:38     ` Miguel Ojeda
2021-01-13 14:40       ` Miguel Ojeda

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFRnB2XcWKrPCBo04iVr9Z4xNvjMw8pFmqCkqB_xsaZJKc_CCw@mail.gmail.com \
    --to=alex.gaynor@gmail.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.kernel.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 NNTP newsgroup(s).