Migration notes
See original GitHub issue@hynekcer, @philchristensen maybe it would make sense (if at all possible), to include on the release notes all (or at least noticeable) api changes?
Like backends.driver
has been moved to dbapi.driver
, stuff like that so people updating from an existing 0.7.2 release knows what needs to be updated in their code?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Introduction to Human Migration | National Geographic Society
Students discuss types of migration and people who migrate. Then they brainstorm reasons for migrating. Grades. 6 - 8. Subjects. Geography, Human Geography....
Read more >Migration | The Geography Study School
Migration is the movement of people from one place to another. Net migration is the number of immigrants minus (-) the number of...
Read more >Notes to Exchange Migration | Binary Tree Migrator for Notes
Notes to Exchange migration – Binary Tree Migrator for Notes supports migrations from Notes and Domino to Microsoft Exchange, both online and on-premises....
Read more >Migration - the United Nations
Since the earliest times, humanity has been on the move. Some people move in search of work or economic opportunities, to join family,...
Read more >Migration and Its Effects: Causes, Migrants, Impacts ... - Toppr
Migration is a way to move from one place to another in order to live and work. Movement of people from their home...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I vow to report whatever I come across 😄
I wrote a CHANGELOG file (#228) after your issue. That is a more universal basic text useful for non trivial upgrades.
(Maybe I can remember a new requirement for a future refactoring of tests, that an old test project with some subset of old simple tests should work also with a new version of framework. If it will not work then upgrade notes will be necessary. Currently I’m testing the public API together with internals of the framework in order to minimize the number of necessary tests, because a test setUp/tearDown is relative slow with Salesforce. A small subset of tests would cover probably only a basic usage, not issues similar to this one.)
I vote for close.