Skip to content

Commit f7ac776

Browse files
authored
Move Project status lower in the README (#70)
* Move Project status lower in the README * Update README.md
1 parent 761912f commit f7ac776

File tree

1 file changed

+23
-23
lines changed

1 file changed

+23
-23
lines changed

README.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -4,29 +4,6 @@
44
[![codecov.io](http://codecov.io/github/JuliaGraphs/Graphs.jl/coverage.svg?branch=master)](http://codecov.io/github/JuliaGraphs/Graphs.jl?branch=master)
55
[![](https://img.shields.io/badge/docs-latest-blue.svg)](https://juliagraphs.org/Graphs.jl/dev/)
66

7-
## Current Project Status
8-
9-
The Graphs project is a reboot of the now-archived LightGraphs
10-
package, which remains available on GitHub at
11-
[sbromberger/LightGraphs.jl](https://github.com/sbromberger/LightGraphs.jl). If
12-
you don't need any new features developed since the fork, you can continue to
13-
use older versions of LightGraphs indefinitely. New versions will be released
14-
here using the name Graphs instead of LightGraphs. There was an older package
15-
also called Graphs. The source history and versions are still available in
16-
this repository, but the current code base is unrelated to the old Graphs code
17-
and is derived purely from LightGraphs. To access the history of the old Graphs code,
18-
you can start from [commit 9a25019](https://github.com/JuliaGraphs/Graphs.jl/commit/9a2501948053f60c630caf9d4fb257e689629041).
19-
20-
**Transition from LightGraphs to Graphs:**
21-
22-
LightGraphs and Graphs are functionally identical, still there are some steps involved making the change:
23-
24-
* Change `LightGraphs = "093fc24a-ae57-5d10-9952-331d41423f4d"` to `Graphs = "86223c79-3864-5bf0-83f7-82e725a168b6"` in your Project.toml.
25-
* Update your `using` and `import` statements.
26-
* Update your type constraints and other references to `LightGraphs` to `Graphs`.
27-
* Increment your version number. Following semantic versioning, we suggest a patch release when no graphs or other `Graphs.jl`-objects can be passed through the API of your package by those depending on it, otherwise consider it a breaking release. "Passed through" entails created outside and consumed inside your package and vice versa.
28-
* Tag a release.
29-
307
## Overview
318

329
Graphs offers both (a) a set of simple, concrete graph implementations -- `Graph`
@@ -77,6 +54,29 @@ for guidance on development and bug reporting.
7754

7855
JuliaGraphs development subscribes to the [Julia Community Standards](https://julialang.org/community/standards/).
7956

57+
## Project Status
58+
59+
The Graphs project is a reboot of the LightGraphs
60+
package (archived in October 2021), which remains available on GitHub at
61+
[sbromberger/LightGraphs.jl](https://github.com/sbromberger/LightGraphs.jl). If
62+
you don't need any new features developed since the fork, you can continue to
63+
use older versions of LightGraphs indefinitely. New versions will be released
64+
here using the name Graphs instead of LightGraphs. There was an older package
65+
also called Graphs. The source history and versions are still available in
66+
this repository, but the current code base is unrelated to the old Graphs code
67+
and is derived purely from LightGraphs. To access the history of the old Graphs code,
68+
you can start from [commit 9a25019](https://github.com/JuliaGraphs/Graphs.jl/commit/9a2501948053f60c630caf9d4fb257e689629041).
69+
70+
**Transition from LightGraphs to Graphs:**
71+
72+
LightGraphs and Graphs are functionally identical, still there are some steps involved making the change:
73+
74+
* Change `LightGraphs = "093fc24a-ae57-5d10-9952-331d41423f4d"` to `Graphs = "86223c79-3864-5bf0-83f7-82e725a168b6"` in your Project.toml.
75+
* Update your `using` and `import` statements.
76+
* Update your type constraints and other references to `LightGraphs` to `Graphs`.
77+
* Increment your version number. Following semantic versioning, we suggest a patch release when no graphs or other `Graphs.jl`-objects can be passed through the API of your package by those depending on it, otherwise consider it a breaking release. "Passed through" entails created outside and consumed inside your package and vice versa.
78+
* Tag a release.
79+
8080
# Citing
8181

8282
We encourage you to cite our work if you have used our libraries, tools or datasets, refer to `CITATION.bib`.

0 commit comments

Comments
 (0)