My team has been closely following things here and has been looking forward
with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer
expected to ship in "late 2016" as currently reflected on the Swift
Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up with
different reads of what, exactly, "3.x" means in context.
The date I can submit my Swift 3 app to the App Store has significant
impact on my life at the moment. I think Chris' meaning was actually fairly
clear, but I'd also appreciate if the team could spell out an ETA again in
black and white. I'd like to be 100% sure I didn't misunderstand.
···
On Sat, Jul 30, 2016 at 6:38 PM, Robert Hedin via swift-evolution < swift-evolution@swift.org> wrote:
My team has been closely following things here and has been looking
forward with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer
expected to ship in "late 2016" as currently reflected on the Swift
Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up
with different reads of what, exactly, "3.x" means in context.
There is no way Swift 3 doesn't ship with iOS 10 in September.
I think he meant point releases after 3.0 (3.*) will be in 2017 (3 vs 3.* vs 4 was trying to convey this I believe).
Swift 3 has to ship with iOS 10 because lots of us are building and updating to iOS 10 and using swift 3. Apple would have a lot of angry developers come iOS 10 if they couldn't submit their apps...
But of course, Chris can clarify :)
Brandon
···
On Jul 30, 2016, at 9:38 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org> wrote:
My team has been closely following things here and has been looking forward with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer expected to ship in "late 2016" as currently reflected on the Swift Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up with different reads of what, exactly, "3.x" means in context.
Thanks!
rob.
--
Robert Hedin |Dir Software Engineering
w: 770-226-2650 e: robert.hedin@weather.com
I thought Chris was pretty clear as well; but what was said was:
"Over the next year, the core team expects to ship two major releases of
Swift: *Swift 3.x in Spring 2017* and *Swift 4 in Fall 2017*."
I'm know I'm being pedantic, but since 3.0 hasn't been released yet, it
sounds like it should be one of the "two major releases". While I'd love to
have Swift 3 for this year, I'm fine if it's slipping. Honestly, I'm not a
fan of tying what are huge language changes to an arbitrary annual ship
schedule anyway.
All that said, I'm just looking for clarity one way or the other so that I
can plan our app migration strategy over the near term.
rob.
···
On Sat, Jul 30, 2016 at 11:13 PM, Brandon Knope <bknope@me.com> wrote:
There is no way Swift 3 doesn't ship with iOS 10 in September.
I think he meant point releases after 3.0 (3.*) will be in 2017 (3 vs 3.*
vs 4 was trying to convey this I believe).
Swift 3 has to ship with iOS 10 because lots of us are building and
updating to iOS 10 and using swift 3. Apple would have a lot of angry
developers come iOS 10 if they couldn't submit their apps...
But of course, Chris can clarify :)
Brandon
On Jul 30, 2016, at 9:38 PM, Robert Hedin via swift-evolution < > swift-evolution@swift.org> wrote:
My team has been closely following things here and has been looking
forward with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer
expected to ship in "late 2016" as currently reflected on the Swift
Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up
with different reads of what, exactly, "3.x" means in context.
I thought Chris was pretty clear as well; but what was said was:
"Over the next year, the core team expects to ship two major releases of Swift: Swift 3.x in Spring 2017 and Swift 4 in Fall 2017."
I'm know I'm being pedantic, but since 3.0 hasn't been released yet, it sounds like it should be one of the "two major releases". While I'd love to have Swift 3 for this year, I'm fine if it's slipping. Honestly, I'm not a fan of tying what are huge language changes to an arbitrary annual ship schedule anyway.
All that said, I'm just looking for clarity one way or the other so that I can plan our app migration strategy over the near term.
Swift 3.0 will still ship in “late 2016”. That has not changed.
Chris was referring to a point release in Spring 2017. We don’t know if it will be Swift 3.1, or 3.2, or whatever.
- Doug
···
On Jul 30, 2016, at 9:19 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org> wrote:
rob.
On Sat, Jul 30, 2016 at 11:13 PM, Brandon Knope <bknope@me.com <mailto:bknope@me.com>> wrote:
There is no way Swift 3 doesn't ship with iOS 10 in September.
I think he meant point releases after 3.0 (3.*) will be in 2017 (3 vs 3.* vs 4 was trying to convey this I believe).
Swift 3 has to ship with iOS 10 because lots of us are building and updating to iOS 10 and using swift 3. Apple would have a lot of angry developers come iOS 10 if they couldn't submit their apps...
But of course, Chris can clarify :)
Brandon
On Jul 30, 2016, at 9:38 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
My team has been closely following things here and has been looking forward with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer expected to ship in "late 2016" as currently reflected on the Swift Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up with different reads of what, exactly, "3.x" means in context.
On Jul 30, 2016, at 9:46 PM, Douglas Gregor via swift-evolution <swift-evolution@swift.org> wrote:
On Jul 30, 2016, at 9:19 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
I thought Chris was pretty clear as well; but what was said was:
"Over the next year, the core team expects to ship two major releases of Swift: Swift 3.x in Spring 2017 and Swift 4 in Fall 2017."
I'm know I'm being pedantic, but since 3.0 hasn't been released yet, it sounds like it should be one of the "two major releases". While I'd love to have Swift 3 for this year, I'm fine if it's slipping. Honestly, I'm not a fan of tying what are huge language changes to an arbitrary annual ship schedule anyway.
All that said, I'm just looking for clarity one way or the other so that I can plan our app migration strategy over the near term.
Swift 3.0 will still ship in “late 2016”. That has not changed.
Chris was referring to a point release in Spring 2017. We don’t know if it will be Swift 3.1, or 3.2, or whatever.
So no final Swift 3.0 for Xcode 8 / iOS launch (late 2016 speaks like late November or December 2016 while iOS 10 feels like September timeframe).
···
Sent from my iPhone
On 31 Jul 2016, at 05:46, Douglas Gregor via swift-evolution <swift-evolution@swift.org> wrote:
On Jul 30, 2016, at 9:19 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org> wrote:
I thought Chris was pretty clear as well; but what was said was:
"Over the next year, the core team expects to ship two major releases of Swift: Swift 3.x in Spring 2017 and Swift 4 in Fall 2017."
I'm know I'm being pedantic, but since 3.0 hasn't been released yet, it sounds like it should be one of the "two major releases". While I'd love to have Swift 3 for this year, I'm fine if it's slipping. Honestly, I'm not a fan of tying what are huge language changes to an arbitrary annual ship schedule anyway.
All that said, I'm just looking for clarity one way or the other so that I can plan our app migration strategy over the near term.
Swift 3.0 will still ship in “late 2016”. That has not changed.
Chris was referring to a point release in Spring 2017. We don’t know if it will be Swift 3.1, or 3.2, or whatever.
- Doug
rob.
On Sat, Jul 30, 2016 at 11:13 PM, Brandon Knope <bknope@me.com> wrote:
There is no way Swift 3 doesn't ship with iOS 10 in September.
I think he meant point releases after 3.0 (3.*) will be in 2017 (3 vs 3.* vs 4 was trying to convey this I believe).
Swift 3 has to ship with iOS 10 because lots of us are building and updating to iOS 10 and using swift 3. Apple would have a lot of angry developers come iOS 10 if they couldn't submit their apps...
But of course, Chris can clarify :)
Brandon
On Jul 30, 2016, at 9:38 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org> wrote:
My team has been closely following things here and has been looking forward with great anticipation to using Swift 3 in our production systems.
To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer expected to ship in "late 2016" as currently reflected on the Swift Evolution GitHub repo but will rather ship in "Spring 2017".
Over the past 24 hours I've got different members of my team coming up with different reads of what, exactly, "3.x" means in context.
Thanks!
rob.
--
Robert Hedin |Dir Software Engineering
w: 770-226-2650 e: robert.hedin@weather.com
On Jul 31, 2016 at 9:51 am, <Goffredo Marocchi via swift-evolution (mailto:swift-evolution@swift.org)> wrote:
So no final Swift 3.0 for Xcode 8 / iOS launch (late 2016 speaks like late November or December 2016 while iOS 10 feels like September timeframe).
Sent from my iPhone
On 31 Jul 2016, at 05:46, Douglas Gregor via swift-evolution <swift-evolution@swift.org (mailto:swift-evolution@swift.org)> wrote:
>
>
>
>
> >
> > On Jul 30, 2016, at 9:19 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org (mailto:swift-evolution@swift.org)> wrote:
> >
> >
> >
> > I thought Chris was pretty clear as well; but what was said was:
> >
> >
> > "Over the next year, the core team expects to ship two major releases of Swift: Swift 3.x in Spring 2017 and Swift 4 in Fall 2017."
> >
> >
> >
> > I'm know I'm being pedantic, but since 3.0 hasn't been released yet, it sounds like it should be one of the "two major releases". While I'd love to have Swift 3 for this year, I'm fine if it's slipping. Honestly, I'm not a fan of tying what are huge language changes to an arbitrary annual ship schedule anyway.
> >
> >
> >
> > All that said, I'm just looking for clarity one way or the other so that I can plan our app migration strategy over the near term.
> >
> >
> >
>
>
>
> Swift 3.0 will still ship in “late 2016”. That has not changed.
>
>
>
> Chris was referring to a point release in Spring 2017. We don’t know if it will be Swift 3.1, or 3.2, or whatever.
>
>
> - Doug
>
>
> >
> >
> >
> >
> >
> > rob.
> >
> >
> >
> >
> >
> > On Sat, Jul 30, 2016 at 11:13 PM, Brandon Knope <bknope@me.com (mailto:bknope@me.com)> wrote:
> >
> > >
> > >
> > >
> > >
> > > There is no way Swift 3 doesn't ship with iOS 10 in September.
> > >
> > >
> > >
> > > I think he meant point releases after 3.0 (3.*) will be in 2017 (3 vs 3.* vs 4 was trying to convey this I believe).
> > >
> > >
> > >
> > > Swift 3 has to ship with iOS 10 because lots of us are building and updating to iOS 10 and using swift 3. Apple would have a lot of angry developers come iOS 10 if they couldn't submit their apps...
> > >
> > >
> > >
> > > But of course, Chris can clarify :)
> > >
> > >
> > >
> > > Brandon
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Jul 30, 2016, at 9:38 PM, Robert Hedin via swift-evolution <swift-evolution@swift.org (mailto:swift-evolution@swift.org)> wrote:
> > >
> > >
> > > >
> > > >
> > > >
> > > > My team has been closely following things here and has been looking forward with great anticipation to using Swift 3 in our production systems.
> > > >
> > > >
> > > >
> > > > To that end, I'd like to confirm (or not) that "Swift 3.0" is no longer expected to ship in "late 2016" as currently reflected on the Swift Evolution GitHub repo but will rather ship in "Spring 2017".
> > > >
> > > >
> > > >
> > > > Over the past 24 hours I've got different members of my team coming up with different reads of what, exactly, "3.x" means in context.
> > > >
> > > >
> > > >
> > > > Thanks!
> > > >
> > > >
> > > >
> > > > rob.
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > > Robert Hedin |Dir Software Engineering
> > > >
> > > > w: 770-226-2650 (tel:770-226-2650) e: robert.hedin@weather.com (mailto:robert.hedin@weather.com)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > swift-evolution mailing list
> > > > swift-evolution@swift.org (mailto:swift-evolution@swift.org)
> > > > https://lists.swift.org/mailman/listinfo/swift-evolution
> > > >
> >
> >
> >
> > --
> >
> >
> > Robert Hedin |Dir Software Engineering
> >
> > w: 770-226-2650 (tel:770-226-2650) e: robert.hedin@weather.com (mailto:robert.hedin@weather.com)
> >
> >
> >
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution@swift.org (mailto:swift-evolution@swift.org)
> > https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org (mailto:swift-evolution@swift.org)
> https://lists.swift.org/mailman/listinfo/swift-evolution
> _______________________________________________ swift-evolution mailing list swift-evolution@swift.org (mailto:swift-evolution@swift.org) https://lists.swift.org/mailman/listinfo/swift-evolution