>>>>>Why are the recent changes included into the release so selectively?
>>>>>For instance, why are r18739, r18742, r19155, r19171 changes not present?
>>>>>Will they ever be included?
>>>>http://tortoisesvn.tigris.org/faq.html#releases
>>> Does this mean those changes will never be merged into the stable branch?
>>Yes.
> I don't get it. Having multiple branches is a well-known practice. I understand that
> you don't want to commit untested stuff into the stable release branch immediately.
> But why will those changes never be merged?
Don't worry. All new functionality will be included with the next 1.x release. On 1.6.x there will be only fixes, on 1.7 all the new good stuff will be included. (And when 1.7 is released it will become the new stable, with only fixes being merged to it.)
http://tortoisesvn.net/status
Hans-Emil
(Btw, 1.6.7 is listed as the current stable on the status page...)
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2590411
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-20 14:00:03 CEST