search

billyquith / ponder

C++ reflection library with Lua binding, and JSON and XML serialisation.
http://billyquith.github.io/ponder/
Other
633 stars 92 forks source link

Version 2.0 of Ponder is not available anymore. #86

Closed jtschea closed 6 years ago

jtschea commented 6 years ago

Dear developers,

We were using Ponder in version 2.0 which is not available anymore on the GitHub project page. Is there a reason for removing this version? The blog states that version 2.1 is the latest. Where can I find these versions?

Thanks in advance, Jupp

billyquith commented 6 years ago

Apologies. I deleted it as there were issues reported with it. I'd try and use master if I were you. Fixes tend to go straight into master.

TBH I need to adopt a proper release strategy. I've largely just added the versions as a mark of progress.

jtschea commented 6 years ago

Thank you very much, Billy, for explaining this and for the work you've done. Adopting a proper release strategy sounds very promising since Camp/Ponder is a key technology in our quite mature software project that we're using in a professional environment. Using the master branch is a little bit risky for us. We're building our dependencies as a part of our own build process cloning every component from scratch. With this we wouldn't be able to deploy a constant release. For us it would be good to have Ponder releases (2.0, 2.1, ...) even if they are still containing bugs. At least our releases are always containing bugs ;)

Best regards, Jupp

billyquith commented 6 years ago

Thanks for the feedback.

EDIT: This looks a good way to go: http://nvie.com/posts/a-successful-git-branching-model/

I've created a 2.0.1 tag and a release. This adds a few more tweaks after 2.0.0 tag before 2.1. I've only tested it locally. The CI seems to be asleep and I don't have time to wait at the moment.

Generally, the direction is to separate the meta data from users of the meta data. Ponder had heavy coupling between the metadata and "runtime" usage of it, e.g. invocation of functions. This then allows other users of the metadata, e.g. the Lua use that is in master.

jtschea commented 6 years ago

Dear Billy, Thank you very much for working this out so quickly.

The Gitflow Workflow is exactly what we're using together with the excellent Atlassian tool chain. Another good documentation on this topic can be found here.

The first thing I will try out Monday morning is version 2.1 :)

Best regards, Jupp

billyquith commented 6 years ago

Thanks. I'll take a look at the git workflow. This project, and Gwork, started out as an exercise in C++11 and refactoring, but it's interesting developing an open source workflow. Useful for encouraging the correct application of user patches as well.

billyquith commented 6 years ago

Since you haven't got back about 2.1 I'm assuming no news is good news! I'll close this ticket. Please open another if you get any hitches.