Merge the multi-deployment branch to master finally, so we can continue development on master! #43

New Issue

Closed

opened 2019-06-10 09:41:45 +00:00 by b3yond · 1 comment

b3yond commented

2019-06-10 09:41:45 +00:00

Author: @b3yond Posted at: 06.10.2018 07:22

Our version 2.0 development has come so far. I'm fucking proud. We are close to release 2.0.

What is missing

resolve conflicts
fix the latest bugs: https://github.com/b3yond/ticketfrei/issues?q=is%3Aissue+is%3Aopen+label%3Abug
test the latest fixes, before we release this: https://github.com/b3yond/ticketfrei/issues?q=is%3Aissue+is%3Aopen+label%3A%22wait+to+be+tested%22
make an own repository for promotion material #21
what a good opportunity to move the 3 ticketfrei repos to an own organization
organize a release party ;)

Future git workflow

But it would be nice to have branches for different versions etc. So we develop on branches, merge them into master, and from there we merge it to stable1 or stable2, where it gets released.

As soon as we implement tests, this will be useful or so.

@git-sid can you open an issue about writing tests, so we can write down our thoughts and track the process?

Author: @b3yond Posted at: 06.10.2018 07:22 Our version 2.0 development has come so far. I'm fucking proud. We are close to release 2.0. ## What is missing * [x] resolve conflicts * [x] fix the latest bugs: https://github.com/b3yond/ticketfrei/issues?q=is%3Aissue+is%3Aopen+label%3Abug * [x] test the latest fixes, before we release this: https://github.com/b3yond/ticketfrei/issues?q=is%3Aissue+is%3Aopen+label%3A%22wait+to+be+tested%22 * [x] make an own repository for promotion material #21 * [x] what a good opportunity to move the 3 ticketfrei repos to an own organization * [x] organize a release party ;) ## Future git workflow But it would be nice to have branches for different versions etc. So we develop on branches, merge them into master, and from there we merge it to stable1 or stable2, where it gets released. As soon as we implement tests, this will be useful or so. @git-sid can you open an issue about writing tests, so we can write down our thoughts and track the process?