logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git
commit: e540c0f5565cba4acbf81d8eb9ae1d6701cbc92d
parent 3e732f602b3a0a17faf03c97476618fe2b23a807
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Sun, 13 Oct 2019 09:32:59 +0200

badwolf: remove dev activity note, atom feed for releases

Diffstat:

Mprojects/badwolf.shtml4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/projects/badwolf.shtml b/projects/badwolf.shtml @@ -14,8 +14,8 @@ <p>For now it is de-facto is a personnal project but I welcome contributions and could add maintainers and move to a more community-oriented way of doing the development.</p> <p>Features that are not wanted to be present by default will either be done as an option or as a separate branch, this is to avoid having a pile of browsers doing the same thing. Also extensions will try to be independant of the browser.</p> <h2>Releases</h2> - <p>The current development is fairly active and I tag a release about once in a week. The release are stable but I would consider the current stage of development to be in alpha/beta. Badwolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p> - <p>You can get the releases in <a href="https://hacktivis.me/releases/">https://hacktivis.me/releases/</a>, there is only source releases for now but if I can be sure that I can have portable binairies without having to bundle the dependencies I’ll do them too.</p> + <p>The releases are stable but I would consider the current stage of development to be in beta as not everything is present yet. Badwolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p> + <p>You can get the releases tarballs and changelogs at <a href="https://hacktivis.me/releases/">https://hacktivis.me/releases/</a> and <a href="https://gitlab.com/lanodan/badWolf/-/tags">https://gitlab.com/lanodan/badWolf/-/tags</a> (which also provides an <a href="https://gitlab.com/lanodan/badWolf/-/tags?format=atom">Atom feed</a>), there is only source releases for now but if I can be sure that I can have portable binairies without having to bundle the dependencies I’ll do them too.</p> <h3>Packages / Recipes</h3> <ul> <!-- Alphabetically sorted -->