[PLANNING] Release 0.1.0: Runner

26 views
Skip to first unread message

Davey Shafik

unread,
May 16, 2012, 4:08:16 AM5/16/12
to frap...@googlegroups.com
Hey,

In an effort to push forward with the FRAPI project, I want to start the discussions around pushing out an actual [downloadable] release.

The current state of FRAPI releases, is that we have a pre-beta release, with no version number. We have a roadmap (https://github.com/frapi/frapi/wiki/Roadmap) that was written a long time ago, but has most of the items for a 0.1.0 release completed.

I would like to ditch the PEAR package item from the roadmap (for 0.1.0), as I think it is a very large task given the complexity of the frapi installation (and the fact we currently include all dependencies as part of our repo). I'd also like to remove the memcache item; we have no configuration along these lines yet, and I don't want to add it just yet.

Otherwise, I have no issues with the current list (CLI is completed, I just submitted a PR for gzip compression) and it is fact completed if we agree to the changes above.

I would like to add one new item to the roadmap, which is support for RFC 6570 URI templates. Because this potentially has BC breaks (I think we can automatically update legacy routes however), and because I think it's pretty core to the application, I want to get it in at this early stage.

With that said, I have created a Release: Runner 0.1.0 Milestone on github and have included a number of bug fixes I would like to include. I have set a tentative completion date by the end of May, however, that was fairly arbitrary (though I think, completely feasible). 

If anyone is willing to take on any of the outstanding bugs, please simply assign the ticket to yourself: any help is appreciated.

Looking beyond Runner, I feel that the roadmap for 0.2.0 (Jumper) is also a good plan, and falls in line with the UI/UX work I am already working on.

One more thing: release names. Originally they were: Runner, Jumper and Skipper, I don't think it's a great naming scheme and has limited expansion opportunities. I'd like to recommend we switch to something with more options, such as the table of elements (possibly skipping Lithium? :) or using something like the list of presidential secret service code names? What about olympic events/gold medalists? Roman emperors?

Thoughts?

- Davey

Trevor Morse

unread,
Jun 13, 2012, 11:59:30 AM6/13/12
to frap...@googlegroups.com
Hey Davey,

Now that you've gotten 0.1 out (nice work btw!) should we start
discussing 0.2? I've been MIA on frapi for a long time but am back now
and ready to rock and roll.

I'll start by looking at RFC 6570. Is there any new/changed items in
the 0.2 release? We could also review outstanding issues and see what
we want to included in 0.2.

Maybe an IRC meeting makes sense?

-tm
Reply all
Reply to author
Forward
0 new messages