Thanks to Steven Webb's efforts, a number of long-standing JIRA issues
have now been fixed - thank you very much!  I've gone through JIRA and
marked those issues as resolved at this point.  This means that there
are only ~9 issues left in JIRA(LOGCXX-532 can probably be closed at
this point - I'm fairly certain this is invoking undefined behavior
that we just can't fix while still keeping the same features).

The remaining issues shouldn't involve heavy refactoring at all.  This
brings up the question as to what/when should the next release be?  We
can do an 0.13.1 to fix a handful of issues in master that have been
reported, or we could do the next release as a major release(I've been
calling it 1.0.0).

I think there's still work that needs to be done before we do a 1.0.0,
including(but not limited to):
* Making sure the API is clear and stable
* Making sure the ABI is stable(this should be accomplished at this
point, but I want to add some reserved fields to LocationInfo incase
we ever need to expand it
* Any other performance improvements that we can make.  If we can
automate some of these performance tests, that would be great as well.
* Having better error reporting - many exceptions that are thrown are
basically swallowed and just print out to stderr at the moment.  Come
to think of it, do we even want exceptions?  It seems like a bad idea
for the logging framework to throw exceptions

Because of the above, I'm inclined to do an 0.13.1 release before the
end of the year and wait a bit on the next major version before we're
comfortable with it.  Does anybody have any thoughts?

-Robert Middleton

Reply via email to