# Rubygems/rubyforge question - release, package, group?

**URL:** <https://www.ruby-forum.com/t/rubygems-rubyforge-question-release-package-group/122208>\
**Category:** Ruby\
**Created:** [December 5, 2007, 4:27pm UTC](https://www.ruby-forum.com/t/rubygems-rubyforge-question-release-package-group/122208 "2007-12-05T16:27:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsanheim](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@rsanheim](https://www.ruby-forum.com/u/rsanheim)\
**Post date:** [December 5, 2007, 4:27pm UTC](https://www.ruby-forum.com/t/rubygems-rubyforge-question-release-package-group/122208/1 "2007-12-05T16:27:44Z")

</div>

Hi

Could someone please explain the difference between a release, a  
package, and a group when releasing gems to rubyforge (via  
rubyforge/hoe)?

What is the convention for a gem in rubyforge when its the ‘only’  
thing in that project?

thanks,  
Rob

> **[Home](https://robsanheim.com/)**
>
> Just another WordPress site

> **[Cognitect, a Nu Holdings, Ltd. Company](https://cognitect.com/)**

---

<div class="post-metadata">

**Author:** ![rsanheim](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@rsanheim](https://www.ruby-forum.com/u/rsanheim)\
**Post date:** [December 5, 2007, 5:18pm UTC](https://www.ruby-forum.com/t/rubygems-rubyforge-question-release-package-group/122208/2 "2007-12-05T17:18:50Z")

</div>

> Could someone please explain the difference between a release, a  
> package, and a group when releasing gems to rubyforge (via  
> rubyforge/hoe)?
> 
> What is the convention for a gem in rubyforge when its the ‘only’  
> thing in that project?

My hackariffic guesstimate is, I just released the gem file and that  
was that. But then again this was just a test release, to see if I  
could get the release process working, and I only used Hoe for setting  
up the initial dirs etc.

–  
Giles B.

Podcast: [http://hollywoodgrit.blogspot.com](http://hollywoodgrit.blogspot.com)  
Blog: [http://gilesbowkett.blogspot.com](http://gilesbowkett.blogspot.com)  
Portfolio: [http://www.gilesgoatboy.org](http://www.gilesgoatboy.org)  
Tumblelog: [http://giles.tumblr.com](http://giles.tumblr.com)

---

<div class="post-metadata">

**Author:** ![rsanheim](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@rsanheim](https://www.ruby-forum.com/u/rsanheim)\
**Post date:** [December 5, 2007, 5:37pm UTC](https://www.ruby-forum.com/t/rubygems-rubyforge-question-release-package-group/122208/3 "2007-12-05T17:37:39Z")

</div>

On Thu, Dec 06, 2007, Rob S. wrote:

> Could someone please explain the difference between a release, a  
> package, and a group when releasing gems to rubyforge (via  
> rubyforge/hoe)?

IIRC, and I’m sure someone will correct me if I’m wrong:

- group: the project name
- package: the “subproject” in that group
- release: the actual release that the files go into

This is best illustrated with an example:

[http://rubyforge.org/projects/laika](http://rubyforge.org/projects/laika)

The group is “laika”, and there are two packages, athenaeum and linen.  
If you click the download link for Linen, you’ll see that there are a  
number of releases, each of which has 3 files.

> What is the convention for a gem in rubyforge when its the ‘only’  
> thing in that project?

Call the package the same as the group.

Ben