Agreed, I can't see any reason why it *shouldn't* be tagged. It's not like tags are a limited resource.
/Jonas On Sun, Feb 7, 2010 at 4:02 PM, Mislav Marohnić <mislav.maroh...@gmail.com> wrote: > On Sat, Feb 6, 2010 at 23:29, Mikel Lindsaar <raasd...@gmail.com> wrote: >> >> Generally release candidates are tagged, but the beta won't be. The >> current state of the beta is what is in the github repository right >> now. > > No. That's the current state of edge Rails. The current state of the > 3.0.0.beta is the code that was pushed to Gemcutter under the same version. > I don't see a reason why a gem release shouldn't be tagged (beta, > prerelease, RC or other). > For isntance, when a beta2 or RC1 comes out, people like me will want to > diff to see what changed. > git diff --stat 3.0.0.beta..3.0.0_RC1 > Without tags corresponding to releases, this operation becomes non-trivial. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-c...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
