What have you been working on?
- We have been working on bug fixes, improving usability and general quality along with introducing the several user requested features
- Linked static data by one user will be visible to all users from now on along with the ability to delete it from source control repository
- Users will have the possibility to add a directory to the repository root in Git and Mercurial source control systems
- We have introduced object filtering feature for all objects that exists only on source control repository only
- Those features will be included in ApexSQL Source Control R9 along with previously implemented working folder feature
What is the ETA to production?
- ApexSQL Source Control R9 will be released around the first week of August
- For a complete schedule of all upcoming releases, please see the Product roadmap
What usability issues have you encountered and overcome?
- Other than previously implemented improvements, R9 release will have completely new approach to project or single object history:
Both features are now share the same form:
- If the View project history is selected, all changesets will be listed, while in Object history will be listed only changesets which contains chosen object without ability to review scripts of other objects from that changeset
Any object can be compared with its current (database) version:
Or with all its other versions:
What are some features planned in the next release(s) and what are their ETAs?
ApexSQL Source Control 2015 R9 – Q3:
- Working folder as a repository for both development models
- Expanded committing changes and object filtering functionalities so now those can be performed on single objects through the Object Explorer pane
- Create a directory in the repository root for Git and Mercurial
- Filtering for source control objects – Exclude objects that exists only in source control repository, so they won’t appear in the Action center tab
ApexSQL Source Control 2015 R10 – Q4:
- Support for migration scripts – Migration scripts are SQL scripts that are attached to a specific schema change and need to be executed before the change is applied in order to preserve data or set the required server settings
- Ability to insert script folders in source control – With this feature users will have the ability to add scripts and/or script folders under source control so that changes can be tracked as for SQL objects
- CLI support for major source control systems – Other than the most popular source control system that are already natively supported, users will have the ability to link the database to any source control system that supports CLI commands
ApexSQL Source Control 2016 R1 – Q4:
- SQL Server 2016 support
- SQL Server Management Studio 2016 integration
- Support for basic branching and merging functionalities – Although we have a workaround for those features, our plan is to allow the users to create a branch or to merge two branches within a simple click
- Support for association with the work item by ID – Other than comments whose main purpose is to inform other users about the reason for changes, we are planning to introduce the ability to associate the specific changes with work items
July 23, 2015