A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://www.mail-archive.com/html5lib-discuss@googlegroups.com/msg00042.html below:

Looking to a 0.10 release

On Jun 10, 2007, at 6:53 PM, Sam Ruby wrote:
> Ryan King wrote:
>> On Jun 10, 2007, at 3:43 PM, James Graham wrote:
>>
>>> There has been a lot of improvement in html5lib since the 0.9  
>>> release
>>> including some significant bugfixes, and a whole pile of feature  
>>> work.
>>> Therefore I think we should consider a 0.10 release (a 1.0 release
>>> would
>>> be nice but there are still substantial known issues in the spec  
>>> e.g.
>>> the lack of defined behavior for several elements).
>>>
>>> What work needs to be completed before the next release? Apart from
>>> finishing up code to a consistent state in line with Sam's plan,
>>> the big
>>> issue I see is fixing up the documentation to match.
>>>
>>> Also, there is the issue of the python version v the ruby version. I
>>> think it makes sense to release at the same time with the same  
>>> version
>>> number so that one html5lib version number implies one set of bugs
>>> relative to the latest spec. However I don't think it's wise to
>>> hold up
>>> one port significantly because of issues in the other.
>>
>> I think we should wait a bit on a ruby release. I also don't think we
>> need to keep them perfectly in sync, but I might be a minority on
>> that issue.
>
> Wait for what, precisely?
There some more rubyfying I'd like to do to it. Of course, most of  
that rubyfying could probably wait and shouldn't hold up making  
releases.

However, there is one big of rubyfying I'd like to do before we  
release anything-

I'd like to rename the module 'html5lib' to just 'html5'. This may  
seem extremely picky, but that's because it is extremely picky. But I  
think we should do what we can to make the ruby port a native ruby  
package that fits into the ruby ecosystem both technically and  
aesthetically. Also, the rubyforge project where I volunteered to  
release the code is called 'html5' not 'html5lib', and keeping  
consistency between the package name and module name would be a Good  
Thing (TM).

If you guys think this is reasonable, I can do the work and I can  
also package the ruby port into a gem and release it on rubyforge.

-ryan


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"html5lib-discuss" group.
 To post to this group, send email to html5lib-discuss@googlegroups.com
 To unsubscribe from this group, send email to [EMAIL PROTECTED]
 For more options, visit this group at 
http://groups.google.com/group/html5lib-discuss?hl=en-GB
-~----------~----~----~----~------~----~------~--~---


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4