Create an script to automate releases

changed milestone to %sbws: unspecified

Trac:
Parent Ticket: #29953 (moved)

added 10-proposed actualpoints::1 component::core tor/sbws easy milestone::sbws: unspecified no-changes-version owner::juga parent::29953 points::1 priority::medium reviewer-was-teor-20190422 sbws-11x-final-removed-20190312 severity::normal status::needs-revision type::defect version::sbws 1.0.2 labels

Moved to 1.0 milestone so that it can be used to actually release 1.0.3.

Trac:
Milestone: sbws: 1.1.x-final to sbws: 1.0.x-final

Trac:
Points: N/A to 0.2

Minimum points is 1. Assign to myself.

Trac:
Points: 0.2 to 1
Status: new to assigned
Owner: N/A to juga

https://github.com/torproject/sbws/pull/332 Putting into needs_review, though this doesn't affect the functionality of the scanner. I'll merge it in any case if it's not reviewed in 1 week.

Trac:
Keywords: N/A deleted, easy added
Status: assigned to needs_review

Trac:
Reviewer: N/A to teor

Merged in a branch with current master and current needs_review tickets and tested a whole loop with the public Tor network

I did a quick review on the pull request.

Trac:
Status: needs_review to needs_revision

I replied to your question. Regarding the changelog changes, if you have a graphical diff tool (like meld), you can compare the .rst and the .md, and see that the changes are only the format and the section [Unreleased].

Trac:
Status: needs_revision to needs_review

Also created #29582 (moved).

Answering juga's question from IRC:

you prefer i rm the script and add doc, or just leave it like it is now?

It's up to you.

It is weird to have a script that just prints instructions.

It is good that the script shows the right versions in the instructions. Can you add a comment explaining that the script shows the right versions?

Do you plan on modifying the script so it automates more tasks in future releases? Can you add a comment explaining that the script will get better?

Trac:
Status: needs_review to needs_revision

Moving to milestione 1.1 tickets which we don't know if they need to be implemented after 1.0.3 has been released or that can only be done after 1.0 has been released

Trac:
Keywords: N/A deleted, 10-proposed added
Milestone: sbws: 1.0.x-final to sbws: 1.1.x-final

ok, now i made an actual script

Trac:
Status: needs_revision to needs_review

Trac:
Keywords: N/A deleted, network-team-roadmap-2019-Q1Q2 added

Seems good to me, but I think it needs a changes file?

(I don't need to review your changes file, because we have an automated script for that! So feel free to flip it into merge_ready when you're done.)

Trac:
Status: needs_review to needs_revision

Replying to teor:

Seems good to me, but I think it needs a changes file?

You mean a changelog?. There's the one in markdown. I added an extra changelog file in .rst because i need to convert the .md one to .rst, but there's now in master a .rst one generated this way. The master doesn't have yet this script nor the templates.

(I don't need to review your changes file, because we have an automated script for that!

The changelog is semi-automated. I left one line per feature/bug and removed the extra commit lines.

So feel free to flip it into merge_ready when you're done.)

I'm going to assume that this is still ready to merge.

Trac:
Status: needs_revision to merge_ready
Actualpoints: N/A to 1

Replying to juga:

Replying to teor:

Seems good to me, but I think it needs a changes file?

Sorry, I put this comment on the wrong ticket.

I'm going to assume that this is still ready to merge.

I made some comments on the pull request. There are some changes that would make it easier for other people to use.

Trac:
Status: merge_ready to needs_revision

Made the changes you commented.

Trac:
Status: needs_revision to needs_review

I left questions on the pull request about using GitHub's tarball.

Trac:
Status: needs_review to needs_revision

Add keyword to help planify releases/milestones. Tickets that doesn't imply a change of version are tickets which do not affect the code (docs, tests) and some time of refactors.

Trac:
Keywords: N/A deleted, no-changes-version added

Remove tickets from 11x-final that can be implemented next month

Trac:
Milestone: sbws: 1.1.x-final to sbws: unspecified
Keywords: N/A deleted, sbws-11x-final-removed-20190312 added

Assign parent to easy, no-changes-version tickets to better track them

Trac:
Parent: N/A to #29953 (moved)

If these tickets go back in to needs_review, and I am on leave, they will need another reviewer.

Trac:
Reviewer: teor to N/A
Keywords: N/A deleted, reviewer-was-teor-20190422 added

Trac:
Keywords: network-team-roadmap-2019-Q1Q2 deleted, N/A added

changed time estimate to 8h

added 8h of time spent

mentioned in issue #29582 (moved)

mentioned in issue #29953 (moved)

moved to tpo/network-health/sbws#29294 (closed)

mentioned in issue tpo/network-health/sbws#29582 (closed)