Aspen 1.0 bumped to June 3

31 views
Skip to first unread message

Chad Whitacre

unread,
May 4, 2012, 9:32:05 PM5/4/12
to aspen-users
Folks,

The Aspen 1.0 release, which was scheduled for tomorrow, May 5, is now scheduled for Sunday, June 3.

Aspen saw major progress towards 1.0 over the past two months. The request/response API, unicode support, and hooks and configuration systems have all seen great improvements. Additionally, Aspen added two significant new features in the past two weeks: content negotiation, and pluggable renderers. Both of these are great features for Aspen to have, and I'm quite happy with how they turned out and also the team effort that went into them. Thanks especially to Paul Jimenez for doing the design, architecture, and initial implementation. !m pjz

You can read about these features here:


Also, there is a $5.37 bounty out on pull requests for new template language shims:


However, we're still not where we need to be in terms of level of polish on the request API, the configuration API, and documentation. I've waited six years for 1.0, and I've decided to wait a little bit longer to make sure we release something we can all feel really proud of.



chad

Jussi Arpalahti

unread,
May 6, 2012, 3:25:30 PM5/6/12
to aspen-users
Hi.

I was not even aware there was a date for 1.0. Is there a roadmap or something on what should happen before June 3?

And is there something you would like us to test? I looked through open issues, but there didn't seem to be anything too serious (that I had an opinion on..). Though it would help, if issues were tagged for 1.0 or beyond.

Anyways, I'm testing a couple of app concepts with Aspen during May, so what oddities or such I meet, I will report. Do you prefer them as Github issues or the mailing list?


Jussi





chad
--
You received this message because you are subscribed to the Google Groups "aspen-users" group.
To post to this group, send email to aspen...@googlegroups.com.
To unsubscribe from this group, send email to aspen-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/aspen-users?hl=en.


Chad Whitacre

unread,
May 8, 2012, 9:03:01 AM5/8/12
to Jussi Arpalahti, aspen-users
Jussi,

 
Is there a roadmap or something on what should happen before June 3?

Here are the "big rocks" that need to land before 1.0. These affect API.


 
And is there something you would like us to test? I looked through open issues, but there didn't seem to be anything too serious (that I had an opinion on..). Though it would help, if issues were tagged for 1.0 or beyond.

Here are some smaller tickets that are mostly bugfixes. If these are done before 1.0 then great, otherwise they can be fixed in a point release (no API changes).


 
Anyways, I'm testing a couple of app concepts with Aspen during May, so what oddities or such I meet, I will report.

Sweet! If/when you have a public link, pass it along and I'll add it to the homepage.

 
Do you prefer them as Github issues or the mailing list?

Well, the classic pattern of course is to discuss on the mailing list and then make tickets for agreed-upon issues. I'm not going to be too strict though. :)

For the record, we are pretty active in IRC as well:





chad

Jussi Arpalahti

unread,
May 9, 2012, 3:27:54 PM5/9/12
to aspen-users
On 8 May 2012 16:03, Chad Whitacre <ch...@zetaweb.com> wrote:
Jussi,

 
Is there a roadmap or something on what should happen before June 3?

Here are the "big rocks" that need to land before 1.0. These affect API.


 
And is there something you would like us to test? I looked through open issues, but there didn't seem to be anything too serious (that I had an opinion on..). Though it would help, if issues were tagged for 1.0 or beyond.

Here are some smaller tickets that are mostly bugfixes. If these are done before 1.0 then great, otherwise they can be fixed in a point release (no API changes).



Thanks. I must have missed the milestone filter. Will see if there is anything I might have insight on.
 
 
Anyways, I'm testing a couple of app concepts with Aspen during May, so what oddities or such I meet, I will report.

Sweet! If/when you have a public link, pass it along and I'll add it to the homepage.


Well, the first app is a rewrite of a Django based content creation system (simpler thing than a content management system, I should think) which is in production. It gives me a chance to use a JavaScript framework and CoffeeScript to develop a more general and customizable CRUD interface. App will go to Github, but I don't know if it will get production approval.

The other app is inhouse only, but I will try to write about my experiences on developing it.
 
 
Do you prefer them as Github issues or the mailing list?

Well, the classic pattern of course is to discuss on the mailing list and then make tickets for agreed-upon issues. I'm not going to be too strict though. :)


Well, just about only thing that was odd is Aspen webserver (I was not using thrash) swallowed stdout when tracebacks occur. This made tracking down a bug more difficult since I could not rely on the time honored method of adding print statements everywhere...

Might be the time to finally learn how to use pdb ;)
 
For the record, we are pretty active in IRC as well:




There is quite a time difference between Finland and US, but I shall check it out if I get stuck on somethng. I work on Aspen stuff in the evenings anyways.


Jussi

Chad Whitacre

unread,
May 15, 2012, 2:00:45 PM5/15/12
to Jussi Arpalahti, aspen-users
 Jussi,
 
Well, just about only thing that was odd is Aspen webserver (I was not using thrash) swallowed stdout when tracebacks occur. This made tracking down a bug more difficult since I could not rely on the time honored method of adding print statements everywhere...

Can you help me reproduce this behavior? I haven't seen it before. I use print statement all the time when developing/debugging with Aspen. 

 
Might be the time to finally learn how to use pdb ;)

Hmmm ... the behavior I *have* seen is that if Aspen restarts while I'm in pdb, *then* I lose stdout:




chad
 

Chad Whitacre

unread,
May 22, 2012, 10:31:58 AM5/22/12
to Jussi Arpalahti, aspen-users
Jussi,
 
 Well, I did not succeed in inserting pdb in the Aspen process. Could you share your debugging strategies, perhaps?

I have a shortcut in vim that inserts this:

import pdb; pdb.set_trace()

I put that in a simplate or python module and I get a (pdb) prompt in the console the next time that code path is run.



chad
Reply all
Reply to author
Forward
0 new messages