Version Metodology

[Migrated From Jforum.net]

Hi Guys!!!

What do you think about JForum project to implement a metodology to create newer versions, like Linux kernel does, for example?

2.1.5 a test version, and 2.1.6 the stable version... with freeze date, where no more features will be implemented, just bugs will be fixed until the "liberation" date.

I really don't remember the details of Linux and others free softwares versioning, but shouldn't it be interesting?

[ ]'s
[originally posted on jforum.net by leandro_salvador]

[Migrated From Jforum.net]

I don't think so. It will just confuse the users - it works for geeks, but not for "regular" people

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

Rafael Steil wrote:I don't think so. It will just confuse the users - it works for geeks, but not for "regular" people

Rafael

But with no criteria to create new versions, "never" we will stop to add new features, with some possible new bugs, to the current version...

Why should we stop it (freeze) for sometime? To correct the existing bugs and create a new stablized version...

How it's now, the Project Leader (you ;)) stay overloaded and other contributors can't divide the load... to create new releases...

It's only an idea... I'm not expert in anything related to that... but I feel it's important to share with you this maybe fool idea...

[ ]'s
[originally posted on jforum.net by leandro_salvador]

[Migrated From Jforum.net]

It will only add more overload, as we'll have two (or more) versions to maintain.

What it's possible to do is to provide "weekly builds" in the website, so people won't have to get it directly from the cvs.

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

Rafael Steil wrote:It will only add more overload, as we'll have two (or more) versions to maintain.

What it's possible to do is to provide "weekly builds" in the website, so people won't have to get it directly from the cvs.

Rafael

Rafael,

I think this is a great idea! This will give people a chance to "test" the current build, while still offering a stable release to those that aren't so adventurous.

.... as long as people can easily identify between which download is the stable version and which one is the weekly CVS build.

[originally posted on jforum.net by GatorBait3]

[Migrated From Jforum.net]

Perfect Idea Guys!!!

It's, in my simple opinion, a way to implement easily 2 versions (one stable like 2.1.4 and another in development like 3.0, or something like 2.1.4.1, 2.1.4.2, and so on...).

Maybe, somethink like it: JForum 2.1.4-20051227 version!

Just ideas... ;)

How could I (or anyone) help you?

[ ]'s
[originally posted on jforum.net by leandro_salvador]