Merb 1.1.0.pre pushed
Pavel Kunc
We've pushed Merb 1.1.0.pre to Gemcutter on 19th Feb 2019. The push
was all merb-* gems and I've fixed and pushed today also merb-auth-
more 1.1.0.pre so all should work as supposed.
You can find the migration from pre-bundler Merb to 1.1.0.pre on
http://wiki.github.com/merb/merb/
This push is mainly about the Bundler 0.9.x integration. I currently
upgraded to the Bundler 0.9.7, which resulted in the merb-auth-more
fix but apart of that it works.
Approximate Changelog:
[merb-helpers] Allow usage of the namespaced models
[merb-gen] Fake method hidden class fix
[merb-core] Normalize Symbol actions in router to String.
[merb-core] Remove disabling/enabling JSON from Bootloader.
[merb-gen] Generate Bundler 0.9.x friendly applications.
[merb-core] Merb Bundler 0.9.x integration
[merb-core] Fix run_later for clusters
[merb-core] Fixing bundler integration
[merb-action-args] Fixed optional args on jruby
[merb-gen] Try to workaround weird issues on 1.9.1
[merb-assets] Forgot to commit dirty gemspec
[merb-core] More robust dependency loading
[merb-core] Regenerated gemspec
[merb-core] Require Bundler 0.7.2, update Bundler API we use.
[merb-core] Fixing request parameter handling for on ASCII encodings.
This is LAST push of the 1.1.0.pre, next is 1.1 gems. So the pre hell
ends.
There are some pending patches which I'd like to apply such as mongoid
support for merb-auth and some mongrel fixes. Also we want to have
Merb running on Unicorn (which is currently in progress) so we can
retire Cluster in 1.1.1.
Pavel
Jacques Crocker
BTW... did you see that RubyGems 1.3.6 finally fixed that pre dependency bug? Pre gems can now depend on non-pre gems.
> --
> You received this message because you are subscribed to the Google Groups "merb" group.
> To post to this group, send email to me...@googlegroups.com.
> To unsubscribe from this group, send email to merb+uns...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/merb?hl=en.
>
Pavel Kunc
But I think we used pre a bit wrong. It really should be just snapshot
of the master and we should use pre versions such as rc1 ... And tag
these versions so there are exact points to refer in the code.
However I hope that the push of the 1.1 will allow SHORT releases
1.1.x with few features. One two features some bug fixes and do the
release. The 1.1 was too long and become difficult to maintain.
Pavel
MarkMT
BTW, ticket #1304 is still an outstanding issue for me. I've found
that if I pull the latest pre-release I have to manually remove the
old patch that causes my problem in order to be able to use it. I'm
curious whether anyone else has an app that includes a file upload and
checkboxes in a single form and has run into this issue.
Mark.
On Feb 21, 10:27 am, Pavel Kunc <pavel.k...@gmail.com> wrote:
> Hi all,
>
> We've pushed Merb 1.1.0.pre to Gemcutter on 19th Feb 2019. The push
> was all merb-* gems and I've fixed and pushed today also merb-auth-
> more 1.1.0.pre so all should work as supposed.
>
> You can find the migration from pre-bundler Merb to 1.1.0.pre onhttp://wiki.github.com/merb/merb/
Ezra Zygmuntowicz
On Feb 21, 2010, at 8:27 AM, Pavel Kunc wrote:
Thanks Pavel for keeping the merb torch burning. Keep up the good work man!
Cheers-
Ezra Zygmuntowicz
e...@engineyard.com
Tony Mann
Pavel Kunc
@ezra It might be fire again :-) Let's see how all goes, wish list is
long and decision for Big rewrite to Rails 3 is out of question (not
because of religion ;-) ). And apparently quite a few people need Merb
surviving.
@tony Yep, it seems we need more to delete than add :-)
I'm going to put some smaller milestones + fixes for final 1.1 push
once I'm back next Monday. That should allow smaller and more regular
releases which can be actually documented.
However not having power to do much documentation stuff I'll probably
go with Sequel-ish way: verbose commit messages, rdoc, change log and
release notes.
Pavel
On Feb 22, 4:15 pm, Tony Mann <thephatm...@gmail.com> wrote:
> Nice work, Pavel!
>
> I will be *very* happy to see the end of Cluster, as it has caused us
> endless headaches with our project. Let us know how we can help out with the
> switch to Unicorn.
>
> ..tony..
>
> > merb+uns...@googlegroups.com <merb%2Bunsu...@googlegroups.com>.
pedro mg
On Feb 23, 2010, at 12:52 AM, Pavel Kunc wrote:
> @mark I can promise it gets fixed in 1.1
>
> @ezra It might be fire again :-) Let's see how all goes, wish list is
> long and decision for Big rewrite to Rails 3 is out of question (not
> because of religion ;-) ). And apparently quite a few people need Merb
> surviving.
I do ;) Thanks Pavel
pedro mg
http://blog.tquadrado.com