2021 is here - and Bitcoin is touching all time highs. For us at tipxmr the last months have been full of change and of little progress. However, there is still some exciting developments on the horizen that we want to share with you.

Personal changes and a professional workflow

The month of december 2020 has seen little activity on our GitHub. This has been due to personal events going on in all of our lives. AlexAnarcho has moved countries, mghny is finishing up his studies and hundehausen has taken up a role as a junior frontend developer. Nevertheless our passion for Monero and tipxmr stands unimpinged.

We aim to finish the project and CCS proposal as soon as possible, but take no shortcuts and make the code and the infrastructure as robust as possible. Further, we take the opportunity of hundehausens real job experience to structure our workflow in a more professional way. More concretely, we have moved away from the old trello board and implemented a jira canban board that integrates better with Git and allows a better organisations.

For all the interested developers out there: The tipxmr code now lives close to the jira board. New branches ought to be named according to ticket number. Hundehausen has created a new project and implemented the system there. See here our new GitHub Repo with the workflow explained.

How to code for tipxmr

  1. Look for a ticket in Jira from the backlog
    • Tickets with higher priority are considered to be chosen first
    • Assign ticket to yourself and move it to in progress
  2. Create new branch from develop branch for smaller tasks (hotfix, bugfix, story, subtask) or use master branch for epics
    • Naming: feature/[ticket-no.]-description or hotfix/[<ticket-no.>]-<description>
    • Example: feature/1234-Fixing-Style-Upload-Button
    • The No. of the feature branch is always from the “highest” ticket-layer like epic -> story -> subtask
    • The same number and name is used for different repositories (frontend / backend) if it is the same task
  3. Write code, test it properly.
  4. Commit your changes, comment in the ticket, add the URL to the merge request and move it to dev approval
    • Commit messages on the other hand have the smallest ticket no. like from a subtask for example
    • Example: feature/1234-meaningful-name
  5. Don’t loose track of your ticket, keep an eye on it until it is merged and done.
  6. If your branch gets merged, please delete the branch.
  • The master branch is always working, no unfinished features are merged into it
  • Work on a dev approval before you start a new story
  • Changes that differ from the ticket description must be documented in the ticket and commit message
  • If new tasks arise, wirte a ticket and save it to the backlog
  • A ticket has fields like prioriry, frontend or backend

Next steps

So to conclude: We are on track to get back on the road, work smarter and harder than before and release our first version of tipxmr.live to the world. Stay tuned.