Visibility into timeline for proposals left in "Awaiting Review" for a while?


(E. Maloney) #1

Hello,

Back in April, a proposal PR of mine <https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md> (SE-0079 <https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>) was merged into master that would make the following code legal when in a block where self is weak:

    guard let self = self else { return }

and:

    if let self = self {
        // ...code...

Since then, the proposal has been Awaiting Review.

Because it was a relatively minor and non-controversial change, I had assumed it would go through review somewhat quickly. Now we're getting to the cutoff for Swift 3 and I'm getting the sense that it will not be considered.

I'm sure I'm not the only proposal author who thinks it would be great to have a better sense of the selection criteria for review and some visibility into when a given proposal might come up for review.

I understand how busy the core team is, and therefore I don't mind waiting. But if, for example, there is a "review queue", I'm sure the community would benefit from knowing what's in the pipeline and what sort of proposals are of more immediate interest to the core team. At the very least, it would make the waiting easier.

What do you think?

And, while I have your attention, is there any chance this proposal can be considered in time for Swift 3? :wink:

Have a good weekend,
Evan


(Jacob Bandes-Storch) #2

In the "schedule" document, this proposal is listed under the section
entitled "Merged proposals that are out of scope for Swift 3.0, but will be
scheduled when it is done".

https://github.com/apple/swift-evolution/blob/master/schedule.md
https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d

Jacob

···

On Fri, Jul 15, 2016 at 12:32 PM, Evan Maloney via swift-evolution < swift-evolution@swift.org> wrote:

Hello,

Back in April, a proposal PR of mine
<https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>
(SE-0079
<https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>)
was merged into master that would make the following code legal when in a
block where self is weak:

    guard let self = self else { return }

and:

    if let self = self {
        // ...code...

Since then, the proposal has been Awaiting Review.

Because it was a relatively minor and non-controversial change, I had
assumed it would go through review somewhat quickly. Now we're getting to
the cutoff for Swift 3 and I'm getting the sense that it will not be
considered.

I'm sure I'm not the only proposal author who thinks it would be great to
have a better sense of the selection criteria for review and some
visibility into when a given proposal might come up for review.

I understand how busy the core team is, and therefore I don't mind
waiting. But if, for example, there is a "review queue", I'm sure the
community would benefit from knowing what's in the pipeline and what sort
of proposals are of more immediate interest to the core team. At the very
least, it would make the waiting easier.

What do you think?

And, while I have your attention, is there any chance this proposal can be
considered in time for Swift 3? :wink:

Have a good weekend,
Evan

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution


(E. Maloney) #3

Thanks for the tip, Jacob. Unfortunately, the "schedule" document is a 404 for me, and if I search for "schedule.md" in the repo, nothing comes up. Is the schedule document private somehow? Perhaps something that only the core team can see?

···

On Jul 15, 2016, at 7:15 PM, Jacob Bandes-Storch <jtbandes@gmail.com> wrote:

In the "schedule" document, this proposal is listed under the section entitled "Merged proposals that are out of scope for Swift 3.0, but will be scheduled when it is done".

https://github.com/apple/swift-evolution/blob/master/schedule.md
https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d

Jacob

On Fri, Jul 15, 2016 at 12:32 PM, Evan Maloney via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
Hello,

Back in April, a proposal PR of mine <https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md> (SE-0079 <https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>) was merged into master that would make the following code legal when in a block where self is weak:

    guard let self = self else { return }

and:

    if let self = self {
        // ...code...

Since then, the proposal has been Awaiting Review.

Because it was a relatively minor and non-controversial change, I had assumed it would go through review somewhat quickly. Now we're getting to the cutoff for Swift 3 and I'm getting the sense that it will not be considered.

I'm sure I'm not the only proposal author who thinks it would be great to have a better sense of the selection criteria for review and some visibility into when a given proposal might come up for review.

I understand how busy the core team is, and therefore I don't mind waiting. But if, for example, there is a "review queue", I'm sure the community would benefit from knowing what's in the pipeline and what sort of proposals are of more immediate interest to the core team. At the very least, it would make the waiting easier.

What do you think?

And, while I have your attention, is there any chance this proposal can be considered in time for Swift 3? :wink:

Have a good weekend,
Evan

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org <mailto:swift-evolution@swift.org>
https://lists.swift.org/mailman/listinfo/swift-evolution


(Jacob Bandes-Storch) #4

Hi Evan,
The "proposal status" page I made was just merged into master, so the place
to go is now http://apple.github.io/swift-evolution/ . This replaces the
schedule document. Since your proposal was listed in the schedule under
"Merged proposals that are out of scope for Swift 3.0, but will be
scheduled when it is done", I put it under the "Deferred" section of the
new status page.

Jacob

···

On Mon, Jul 18, 2016 at 12:22 PM, Evan Maloney <emaloney@gilt.com> wrote:

Thanks for the tip, Jacob. Unfortunately, the "schedule" document is a 404
for me, and if I search for "schedule.md" in the repo, nothing comes up.
Is the schedule document private somehow? Perhaps something that only the
core team can see?

On Jul 15, 2016, at 7:15 PM, Jacob Bandes-Storch <jtbandes@gmail.com> > wrote:

In the "schedule" document, this proposal is listed under the section
entitled "Merged proposals that are out of scope for Swift 3.0, but will be
scheduled when it is done".

https://github.com/apple/swift-evolution/blob/master/schedule.md

https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d

Jacob

On Fri, Jul 15, 2016 at 12:32 PM, Evan Maloney via swift-evolution < > swift-evolution@swift.org> wrote:

Hello,

Back in April, a proposal PR of mine
<https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>
(SE-0079
<https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md>)
was merged into master that would make the following code legal when in a
block where self is weak:

    guard let self = self else { return }

and:

    if let self = self {
        // ...code...

Since then, the proposal has been Awaiting Review.

Because it was a relatively minor and non-controversial change, I had
assumed it would go through review somewhat quickly. Now we're getting to
the cutoff for Swift 3 and I'm getting the sense that it will not be
considered.

I'm sure I'm not the only proposal author who thinks it would be great to
have a better sense of the selection criteria for review and some
visibility into when a given proposal might come up for review.

I understand how busy the core team is, and therefore I don't mind
waiting. But if, for example, there is a "review queue", I'm sure the
community would benefit from knowing what's in the pipeline and what sort
of proposals are of more immediate interest to the core team. At the very
least, it would make the waiting easier.

What do you think?

And, while I have your attention, is there any chance this proposal can
be considered in time for Swift 3? :wink:

Have a good weekend,
Evan

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution