CHANGELOG
A changelog is a log or record of all notable changes made to a project. The project is often a website or software project, and the changelog usually includes records of changes such as bug fixes, new features, etc. Some open-source projects include a changelog as one of the top-level files in their distribution.
CHANGELOG
A changelog has historically included all changes made to a project. The "Keep a Changelog" site instead advocates that a changelog not include all changes, but that it should instead contain "a curated, chronologically ordered list of notable changes for each version of a project" and should not be a "dump" of a git log "because this helps nobody".[1]
Although the GNU (Automake) canonical naming convention for the file is ChangeLog,[2] it is sometimes alternatively named as CHANGES or HISTORY (NEWS is usually a different file reflecting changes between releases, not between the commits). Another convention is to call it a CHANGELOG.[1] Some project maintainers will append a .txt suffix to the file name if the changelog is plain text, a .md suffix if it is in Markdown, or a .rst suffix if it is in reStructuredText.
Note that between the date and the name, and again between the name and the email address, there are two spaces each. It is common to enclose the email address in . The Emacs editor creates such entries when creating additional changelog entries.
Most wiki software includes changelogs as a fundamental feature (often called history in this context). For example, the "View history" link at the top[5] of a Wikipedia entry links to that page's changelog. This feature is vital for complying with the attribution requirements of some copyright licenses.[citation needed]
The root of all Liquibase changes is the changelog file. Liquibase uses a changelog to sequentially list all changes made to your database. Think of it as a ledger. Liquibase uses this changelog record to audit your database and execute any changes that are not yet applied to your database. You can store and version your changelog in any source control tool.
An individual unit of change in your changelog is called a Changeset. When you want to modify your database, simply add a new changeset and specify its operation as a Change Type. For example, you may add a changeset to create a new table, and another changeset to drop a primary key.
When you run a database update, the Liquibase migrator parses the changelog tag. The migrator first checks any preconditions specified. If any of the preconditions fail, Liquibase exits with an error message explaining what failed. Preconditions can be typically used for both documenting and enforcing expectations or assumptions. For example, you can specify the DBMS to be run against the changelog or the user you should log in to run changes.
Preconditions required to execute the changelog. Must be passed before the changeset is run. It is typically used for doing a data sanity check before doing something unrecoverable such as a dropTable. Since 1.7
An exhaustive changelog would be unreasonably long, but one can always see our entire development history in github. For the core Server repository, see for example here the 762 pull requests merged for Milestone 21.
An exhaustive changelog would be unreasonably long, but one can always see our entire development history in github. For the core Server repository, see for example here the 783 pull requests merged for Milestone 20.
As this is a major release, the changelog is too long to put here. Users can look on github milestones to find what has been merged. Find an overview of what has been improved in this series of blog posts:
Note: Some websites such as Keep A Changelog explain that you shouldn't make a changelog only by copying and pasting your git commits (refer to the simple way). Indeed, I recommend trying to avoid this way if you are working on a professional product.
Historically, change logs were maintained on specially formattedfiles. Nowadays, projects commonly keep their source files under aversion control system (VCS), such as Git,Subversion, or Mercurial. If the VCS repository is publiclyaccessible, and changes are committed to it separately (one commit foreach logical changeset) and record the authors of each change, thenthe information recorded by the VCS can be used to producethe change logs out of VCS logs, and to answer the abovequestions by using the suitable VCS commands. (However, theVCS log messages still need to provide some supportinginformation, as described below.) Projects that maintain suchVCS repositories can decide not to maintain separate changelog files, and instead rely on the VCS to keep the changelogs.
So glad they adopted this, thanks cmr. Like many I've been having a difficult time reading through switch firmware changelogs. As someone who isn't using a MS390, it's been challenging to try and just focus on the details relevant to my networks because of how much MS390 content has been in the changelogs lately.
qBittorrent v4.5.0 was released.A lot of work has gone into this release which isn't necessarily reflected in the changelog below (code improvements, rewritings and refactorings). Special thank you to people that were helpful in other useful areas like testing and bug hunting: @thalieht, @xavier2k6, @PriitUring, @oorzkwsNotable features: New icon theme, new color theme and better startup time when using many torrents.WINDOWS: Only 64-bit builds will be offered from now on.NOTE: The default builds for all OSs switched to libtorrent 1.2.x from 2.0.x. Builds for libtorrent 2.0.x are also offered and are tagged with lt20. The switch happened due to user demand and perceived performance issues. If until now you didn't experience any performance issue then go ahead and use the lt20 builds.
qBittorrent v4.5.0beta1 was released.This is the first beta release for the upcoming 4.5.x series. More beta releases will follow.At this point, no changelog is provided. Also no source tarballs. If you want build from source then just use the relevant git tag.
qBittorrent v4.3.6 and v4.4.0beta1 were released.The v4.3.x releases will continue strictly with important fixes only and until the v4.4.0 is properly tested to be released as stable.In the meantime there will be a few beta releases of v4.4.0 until it hits stable status. If you use the betas then keep checking back for new betasbecause you won't get a program notification for them. Check once per week.The v4.4.0beta1 uses the libtorrent 2.0.x series. A more detailed changelog may be filled later.
qBittorrent v4.3.4.1 was released.WINDOWS: Windows Defender is being incredibly annoying lately marking us as unwanted software/malicious/trojan/virus. If you experience problems with the installer not starting or not finishing, check that Defender hasn't silently deleted it or the files it extracts. See this, this and this.Read the v4.3.4 changelog too because this is a hotfix release.
qBittorrent v4.3.0.1 was released.This is a minor release to address crashes on Windows related to torrents with URL seeds (HTTP Sources in the qbittorrent window). These crashes were exposed due to boost 1.74. Boost 1.73 doesn't have this problem. However, libtorrent also fixed the issue on their end so the Windows installers use the newer libtorrent code.The rest of the release is almost the same as v4.3.0 (see changelog). Since other platforms weren't affected only Windows builds will be made available for this version.
qBittorrent v4.2.5 was released.It contains fixes for two crashes.ATTENTION WINDOWS USERS: There's a "qBittorrent" app on the Windows Store which costs money. It isn't an official release nor it is coming from us. The person publicizing it doesn't have permission to use the qBittorrent name/logo.v4.2.5 changelog:
qBittorrent v4.2.4 was released.It contains various qbittorrent and libtorrent networking fixes. Now most issues with VPNs and SOCKS5 proxies should be fixed.ATTENTION WINDOWS USERS: There's a "qBittorrent" app on the Windows Store which costs money. It isn't an official release nor it is coming from us. The person publicizing it doesn't have permission to use the qBittorrent name/logo.v4.2.4 changelog:
qBittorrent v4.2.3 was released.It contains various fixes from v4.2.2 regarding scaling on HiDPI monitors, some VPN issues and UNC path handling. Torrents with broken UNC paths will be fixed when you run this release.On Windows, Qt 5.13.2 is used because of a regression regarding VPNs that affects RSS and Search functionality. Due to this, the scaling behavior on HiDPI monitors will be the same as in v4.2.1 too.ATTENTION WINDOWS USERS: There's a "qBittorrent" app on the Windows Store which costs money. It isn't an official release nor it is coming from us. The person publicizing it doesn't have permission to use the qBittorrent name/logo.v4.2.3 changelog:
qBittorrent v4.2.2 was released.ATTENTION WINDOWS USERS: There's a "qBittorrent" app on the Windows Store which costs money. It isn't an official release nor it is coming from us. The person publicizing it doesn't have permission to use the qBittorrent name/logo.v4.2.2 changelog:
qBittorrent v4.2.1 was released.Due to libtorrent fixes, UDP through proxies should work again. In some cases it also caused crashes.ATTENTION: There's a slight change in the way network interfaces are configured. If you have a specific network interface/local address set in the Advanced Settings, go and make sure that your settings have stayed the same. The extra setting for Listen on IPv6 address has been removed.v4.2.1 changelog:
qBittorrent v4.2.0 was released.There were no significant user facing changes since the previous RC release. The full v4.2.0 changelog follows.ATTENTION: This release uses the libtorrent 1.2.x series. It saves fastresumes a bit differently than the 1.1.x series, which are used so far in the previous versions. If you run it and then downgrade to a previous qBittorrent version then your torrents will probably start rechecking. 041b061a72