search

jeremyis78 / JBookTrader

A Java ATS for market-depth-based trading strategies
BSD 3-Clause "New" or "Revised" License
6 stars 6 forks source link

Move the releases in historical_releases/ to github releases #6

Closed jeremyis78 closed 6 years ago

jeremyis78 commented 6 years ago

To follow more of the github way of doing releases, Click 'Draft a new release' on this page: https://github.com/jeremyis78/JBookTrader/releases and do this for each release in historical_releases. Once done historical_releases/ can be deleted.

jeremyis78 commented 6 years ago

github ties the uploaded zip to your source code so doing 'Draft a new release' with an old zip file isn't what we want as the bundled sources it creates would be for current master, not the sources from the time of the release. If we had the commit ids of each release that might be a way to do it (Create the tag manually and then specify that tag when drafting a new release). Would that even be worth it? Maybe we just leave it as is and only new JBookTrader versions (after v9.01) are released this way.

jeremyis78 commented 6 years ago

deleted historical_releases to keep new/upcoming releases small