Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Plumed AlphaFold
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Martin Kurečka
Plumed AlphaFold
Commits
e566918a
There was an error fetching the commit references. Please try again later.
Commit
e566918a
authored
8 years ago
by
Giovanni Bussi
Browse files
Options
Downloads
Patches
Plain Diff
Added doc about release pace
I think this closes #146 [makedoc]
parent
24eb510d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
user-doc/Intro.txt
+19
-1
19 additions, 1 deletion
user-doc/Intro.txt
with
19 additions
and
1 deletion
user-doc/Intro.txt
+
19
−
1
View file @
e566918a
...
...
@@ -80,7 +80,25 @@ or enhanced sampling calculations.
\page Changelog Change Log
Here you can find a history of changes across different PLUMED versions.
We mostly add new features without breaking exising ones.
The future releases are expected to follow more or less the pace
of the old release. This means:
- Approximately once per year, after summer, a new release (2.X). These releases
typically group together all the features that were contributed during the
year.
- Approximately every three month, we announce a patch (e.g. 2.2.X).
This typically contains bug fixes, and could occasionally contain a new feature.
A few months before each new release we provide a beta release.
We typically maintain release branches until the fifth patch release (2.X.5),
which should come out approximately 15 month after the original release (2.X).
After that, branches are not supported anymore.
Notice that occasionally we publish patches on the mailing list.
These patches are always included in the following release, but we encourage
users that want to be up to date to follow the mailing list.
Below you can find change logs for all the published releases.
We mostly add new features without breaking existing ones.
However, some of the changes lead to incompatible behavior.
In the Change Log we try to give as much visibility as possible to these changes
to avoid surprises.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment