Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
ffbs-gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
darkbit
ffbs-gluon
Commits
e3f28058
Commit
e3f28058
authored
5 years ago
by
Martin Weinelt
Committed by
Martin Weinelt
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
docs, README: Gluon v2018.2.3
parent
d10c28c8
No related branches found
Branches containing commit
Tags
v2018.2.3
Tags containing commit
No related merge requests found
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
README.md
+1
-1
1 addition, 1 deletion
README.md
docs/conf.py
+1
-1
1 addition, 1 deletion
docs/conf.py
docs/site-example/site.conf
+1
-1
1 addition, 1 deletion
docs/site-example/site.conf
docs/user/getting_started.rst
+2
-2
2 additions, 2 deletions
docs/user/getting_started.rst
with
5 additions
and
5 deletions
README.md
+
1
−
1
View file @
e3f28058
...
...
@@ -21,7 +21,7 @@ the future development of Gluon.
Please refrain from using the
`master`
branch for anything else but development purposes!
Use the most recent release instead. You can list all releases by running
`git tag`
and switch to one by running
`git checkout v2018.2.
2
&& make update`
.
and switch to one by running
`git checkout v2018.2.
3
&& make update`
.
If you're using the autoupdater, do not autoupdate nodes with anything but releases.
If you upgrade using random master commits the nodes
*will break*
eventually.
...
...
This diff is collapsed.
Click to expand it.
docs/conf.py
+
1
−
1
View file @
e3f28058
...
...
@@ -52,7 +52,7 @@ copyright = '2015-2019, Project Gluon'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
version
=
release
=
'
2018.2.
2
'
version
=
release
=
'
2018.2.
3
'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
...
...
This diff is collapsed.
Click to expand it.
docs/site-example/site.conf
+
1
−
1
View file @
e3f28058
--
This
is
an
example
site
configuration
for
Gluon
v2018
.
2
.
2
--
This
is
an
example
site
configuration
for
Gluon
v2018
.
2
.
3
--
--
Take
a
look
at
the
documentation
located
at
--
https
://
gluon
.
readthedocs
.
io
/
for
details
.
...
...
This diff is collapsed.
Click to expand it.
docs/user/getting_started.rst
+
2
−
2
View file @
e3f28058
...
...
@@ -8,7 +8,7 @@ Gluon's releases are managed using `Git tags`_. If you are just getting
started with Gluon we recommend to use the latest stable release of Gluon.
Take a look at the `list of gluon releases`_ and notice the latest release,
e.g. *v2018.2.
2
*. Always get Gluon using git and don't try to download it
e.g. *v2018.2.
3
*. Always get Gluon using git and don't try to download it
as a Zip archive as the archive will be missing version information.
Please keep in mind that there is no "default Gluon" build; a site configuration
...
...
@@ -44,7 +44,7 @@ Building the images
-------------------
To build Gluon, first check out the repository. Replace *RELEASE* with the
version you'd like to checkout, e.g. *v2018.2.
2
*.
version you'd like to checkout, e.g. *v2018.2.
3
*.
::
...
...
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