Towards 1.0.0 or 1.6.0 or ??

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Towards 1.0.0 or 1.6.0 or ??

LightGuard
Administrator
First order of business, what do we call the next major version bump, 1.0.0, 1.6.0, something else?

When I say next major version bump, here's what I'm thinking we'll have in it:

* A revamp of pages and handlers, mostly removing handlers and pages do all the work
* Allowing awestruct to work correctly in a multithreaded environment (jRuby, Rubinus)
* Fixing up dependencies so it picks up changes in partials, metadata, and config

Also possibly allowing for full configuration via a ruby script (you're welcome Max) akin to Rack or Sinatra.

What are everyone's thoughts?

--
Reply | Threaded
Open this post in threaded view
|

Re: Towards 1.0.0 or 1.6.0 or ??

mojavelinux

The plan looks good. I'd also add that we want to address the most pressing usability issues such as superfluous warnings and oversensitivity to unknown content, but perhaps those improvements were implied.

As for the version, my vote is for 1.0.0. There's no perception that Awestruct has had a 1.0 release, so the jump to 1.6 would look perplexing. Let's just get to 3 version numbers so we can use them the way they're supposed to be used.

-Dan