> On Oct 12, 2016, at 9:52 AM, Alex Blewitt via swift-corelibs-dev
> <email@example.com> wrote:
> I have a couple of Calendar related fixes into swift-corelibs-foundation
> How do I go about cherry-picking these to be in the next release? There are
> several remote branches that have the 'swift-3' moniker including several
> 'preview' ones:
> Why are we representing previews as branches, instead of tags? If I wanted to
> submit a pull request for one of these previews, it's not clear which one(s)
> I should target.
I agree this is a bit confusing.
Right now, swift-3.0-branch is the one that is used as the “development” branch
for any updates to swift 3.0.
> There are also a number of branches that are old (in many cases, over a
> Can we get these cleaned up if they are no longer necessary?
Yes, I think we should delete these. I’ll do that for a bunch of these.
swift-corelibs-dev mailing list