Was going to check something in the source regarding the Rails 3 beta, but it''s not tagged on GitHub. Would be awesome if someone could push the tag. /Jonas -- 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-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Sun, Feb 7, 2010 at 3:08 AM, jnicklas <jonas.nicklas@gmail.com> wrote:> Was going to check something in the source regarding the Rails 3 beta, > but it''s not tagged on GitHub. Would be awesome if someone could push > the tag.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. If you want to see what code you are running on your system, you can checkout the unpacked gem, or you can run your test app using the --dev option. Mikel -- 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-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Sat, Feb 6, 2010 at 23:29, Mikel Lindsaar <raasdnil@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-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
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.marohnic@gmail.com> wrote:> On Sat, Feb 6, 2010 at 23:29, Mikel Lindsaar <raasdnil@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-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@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-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Jonas, Little did you know, but tags are a non-renewable resource. We must conserve our tags or soon there will be none left! In all seriousness, the tag is pushed ;) Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 On Sun, Feb 7, 2010 at 7:46 AM, Jonas Nicklas <jonas.nicklas@gmail.com>wrote:> 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.marohnic@gmail.com> wrote: > > On Sat, Feb 6, 2010 at 23:29, Mikel Lindsaar <raasdnil@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-core@googlegroups.com. > > To unsubscribe from this group, send email to > > rubyonrails-core+unsubscribe@googlegroups.com<rubyonrails-core%2Bunsubscribe@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-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com<rubyonrails-core%2Bunsubscribe@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-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.