-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releasing 1.8.0 #318
Comments
Please chime in with your thoughts, @nniclausse. What do we need to do in order to get 1.8.0 out of the door? :) |
While trying to make a release for the current develop to check if #276 is fixed or not, I failed setting up a fresh Debian stretch VM so that Is there some documentation available what packages (system, latex, perl, …) are required, @nniclausse? |
Hello dear maintainers, |
I'm just commenting to say I'm also looking forward to a new release. At least to have a release with the commits that have been pushed to |
Yes, you are right, it's really time to publish a new release. I hope we can do it before the end of october |
I'm happy to help as good as I can. But I'm quite swamped in work and also only use and know tsung for the HTTP specific parts. |
Hello @tisba I guess this has long been forgotten? 🙂 any chance this project will be picked up again and release 1.8.0 (and eventually 2.0)? |
1.8.0 has been released: |
Hi there.
I think it's time to think about cutting a 1.8.0 release of tsung! 🎉
As time of writing, we have 43 commits by 11 contributors between master and develop: master...develop. It mainly contains bug fixes and some smallish features.
I created a 1.8.0 milestone which currently only contains three smallish things that would be nice to have covered, but I'm open to add or remove things.
I mainly create this issue to document what needs to be done for a release and make that documentation available.
The text was updated successfully, but these errors were encountered: