[Meta] Updating the proposal template to prompt backward compatibility concerns


(Joe Groff) #1

With the end of Swift 3 drawing near, we'll need to start designing with an eye toward backward compatibility. To that end, I think we should update the "Impact on existing code" proposal template to start asking writers to consider backward compatibility concerns. Here's some draft verbage to that effect:

https://github.com/jckarter/swift-evolution/blob/4bdd1b875a8402ec6bbabb3f37151262f130af2b/0000-template.md#backward-compatibility

Any concerns, revisions, or objections?

-Joe


(Charlie Monroe) #2

I agree that the concern of future proposals should be backward compatibility, though I personaly think that Swift 4 will be full of breaking changes anyway (not as many as Swift 3, but there will be quite a few). In that matter, I'm not sure that stressing backward compatibility is better than stressing better desing for the years to come.

···

On Jul 21, 2016, at 6:05 PM, Joe Groff via swift-evolution <swift-evolution@swift.org> wrote:

With the end of Swift 3 drawing near, we'll need to start designing with an eye toward backward compatibility. To that end, I think we should update the "Impact on existing code" proposal template to start asking writers to consider backward compatibility concerns. Here's some draft verbage to that effect:

https://github.com/jckarter/swift-evolution/blob/4bdd1b875a8402ec6bbabb3f37151262f130af2b/0000-template.md#backward-compatibility

Any concerns, revisions, or objections?

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


(Brent Royal-Gordon) #3

The section title should be sentence-case. Other than that, I think it's a good move.

···

On Jul 21, 2016, at 9:05 AM, Joe Groff via swift-evolution <swift-evolution@swift.org> wrote:

With the end of Swift 3 drawing near, we'll need to start designing with an eye toward backward compatibility. To that end, I think we should update the "Impact on existing code" proposal template to start asking writers to consider backward compatibility concerns. Here's some draft verbage to that effect:

https://github.com/jckarter/swift-evolution/blob/4bdd1b875a8402ec6bbabb3f37151262f130af2b/0000-template.md#backward-compatibility

Any concerns, revisions, or objections?

--
Brent Royal-Gordon
Architechies