Version number changes coming for XOOPS - XOOPS - XOOPS News - XOOPS Web Application System

XOOPS

News

News World of XOOPS Developers Hacks Themes Archive Submit News

XOOPS: Version number changes coming for XOOPS

Posted by: BoobtoobOn 2002/12/4 7:35:00 6161 reads

What started out to be just a simple enhancement of XOOPS by integrating the Smarty templating system has now turned into a major overhaul of the core system. So, the XOOPS team has decided to take the high road on the future versioning of XOOPS.

The RC3.x series has been so stable that we are re-versioning it to 1.x series and the RC4.x to the 2.x series. What this translates to is that RC3.06 will become 1.3.X and the RC4 candidate will be numbered as 2.0.X due to all the major core changes that's been performed. As each version is enhanced/bug fixed, we'll have 1.x.x and 2.x.x to better reflect changes.

With the version changes, the 1.3.x series will go into viability mode (bug and security fixes only) and the 2.x.x series will become the future development platform for the core team

We hope you like the new numbering scheme and the changes coming down the pipe.

Regards,
XOOPS Team

The comments are owned by the author. We aren't responsible for their content.

user

Re: Version number changes coming for XOOPS

kitsou Published 12/04/2002 7:51 Just popping in Joined 03/19/2002 Comments 50

Huh ?????? say it again...

in the meantime I'll start my CHIIOS module (critical higher intelligence operating system) which should enable me to understand to the fullest extend the meaning of these news.

Just a suggestion: Do not change the name Xoops, (makes life easier)

user

Re: Version number changes coming for XOOPS

w4z004 Published 12/04/2002 11:06 XOOPS Advisor Joined 12/13/2001 Comments 340

is simple for understand AMIGO the XOOPS 1.0 rc 3.0.6 got o change to XOOPS 1.3.6 and are only a bug fix version.

the XOOPS 1.0 Rc4 change to XOOPS 2.0 it's all.

user

Re: Version number changes coming for XOOPS

dawilby Published 12/04/2002 12:37 Module Developer Joined 01/03/2002 Comments 31

Dissecting the Release Number
A release number is comprised of 3 components: the major release number, the minor release number, and an optional point release number. Here is a sample release number:

2.0.4

and it can be broken into three parts:

major release: 2
minor release: 0
point release: 4
The next release of this component would increment the appropriate part of the release number, depending on the type of release (major, minor, or point). For example, a subsequent minor release would be version 2.1, or a subsequent major release would be 3.0.

Note that release numbers are composed of three _integers_, not three digits. Hence if the current release is 3.9.4, the next minor release is 3.10.0

Beta Release Numbers
Beta releases are denoted by adding "B" after the release number. For example, if the current release version is 2.0.4, and a developer wished to preview the next major release, the release would be labeled 3.0-B1

Did a googally search and found this doc about versioning on an apache website: Apache & Versioning... not that this has to be a rule. Most programmers use there own system of versioning. The new XOOPS versioning looks a lot like it, but maybe you want add another element.

Example: XOOPS major release new style would look like this -->

Xoops 2.0.0 build 1

I like the build idea because its giving me the idea that there is really something build!

Another example: XOOPS had some bugfixes and a new module/block. That would give:

Xoops 2.1.5 build 5

Explanation: Now you would have:
- major release 2 [ core ]
- minor release 1 [ new module/block ]
- point taken [ 5 bugfixes ]
- build 5 [ the whole package has been zipped 5x times and stored for dowloading... ]

There are so many different versioning styles/idea's, i believe, its hard to make a set of rules and more importantly, use the rules and make XOOPS more stable and robust.

user

Re: Version number changes coming for XOOPS

Boobtoob Published 12/04/2002 12:44 Friend of XOOPS Joined 12/22/2001 Comments 202

Quote:

Example: XOOPS major release new style would look like this -->

Xoops 2.0.0 build 1

We won't get that granular with builds. the most extreme you'll see us get is with the examples we put forth. As far as a name change? I don't remember that being in my post

user

Re: Version number changes coming for XOOPS

chosen Published 12/04/2002 16:17 Just popping in Joined 02/03/2002 Comments 29

So;
1) "RC" statement will not be used anymore,
2) The 1.x series will not have any core changes and be a unique, stable version by themselves and will not face major changes anymore,
3) XOOPS will be developed with the 2.x series, major changes will be made to these series.

If I have understood correctly, this is the new trend with XOOPS.Now people who decide to use the 1.x may stay with it, the others will advance with 2.x.
Hmm..It seems more logical for me to use the 2.x, if you want to advance with the changes?? Right?

user

Re: Version number changes coming for XOOPS

Boobtoob Published 12/04/2002 17:00 Friend of XOOPS Joined 12/22/2001 Comments 202

It depends on your needs whether to stay with 1.x for a while while 2.x matures. The 2.x core has been almost rewritten so, theres going to be a lot of change.

user

Re: Version number changes coming for XOOPS

gstarrett Published 12/04/2002 17:13 Friend of XOOPS Joined 03/12/2002 Comments 174

Quote:

Hmm..It seems more logical for me to use the 2.x, if you want to advance with the changes?? Right?

The decision of if and when to change major releases varies by person / philosophy. If you like to keep up on the latest features, then get onto 2.x right away. If you prefer to be more conservative and let others find the bugs and keep the more stable version until 2.x settles, then stay with 1.x. If you don't have much knowledge of how to troubleshoot and correct problems (or time to do so), then you'll probably want to wait until 2.x stabilizes and has all the modules you need before migrating.

Personally, I plan on grabbing 2.x quickly. I like to tinker, I like to give back to the community what little time I have, and I'm looking forward to seeing how flexible Smarty makes XOOPS!

I'm hoping to do a core replacement of the current site I maintain (AZPuppets.org) with XOOPS once I've customized it and seems stable. Ideally, the look of the current site won't change except for addition of some blocks / fields and a lot of functionallity, but I digress...

Keep up the good work guys. I'm anxiously awaiting 2.x or whatever you decide to call it!

user

Re: Version number changes coming for XOOPS

chosen Published 12/04/2002 18:15 Just popping in Joined 02/03/2002 Comments 29

I have very little time to deal with troubleshooting and bugs, so you're right. Even if I'd love to help with the troubleshooting, I can only do this on my test site, not the real one..So I prefer to wait until 2.x stabilizes.

But it seems, this will take a long long time..In the meantime I still want to use XOOPS on my main site, and plan to use RC3.05 or the upcoming 3.0.6. Shall we be able to upgrade from 1.x to 2.x in the future?

It is said that the code will be almost RE-WRITTEN. After so many changes, will it be possible to upgrade?

user

Re: Version number changes coming for XOOPS

w4z004 Published 12/04/2002 19:16 XOOPS Advisor Joined 12/13/2001 Comments 340

for clarify a little more.

the rc4 (now 2.0) are STABLE and go to have 1 or 2 weeks of full beta testing.

and EVER can upgrade.. we ever have upgrades.

Login

Username

Password

Remember me

Register now! | Lost Password?

Search

Advanced Search

Recent Comments

Re: New Admin Theme for XOOPS (Beta)

Publisher liomj 10/28/2024 23:33
Sanford Pharmacy: Exceptional Pharmacy Services Tailored to You

Publisher donaldjohn 10/16/2024 9:53
Re: New Admin Theme for XOOPS (Beta)

Publisher walkero 10/15/2024 18:30
Re: XOOPS 2.5.12 Beta-2 available for Testing

Publisher cadch 08/30/2024 6:33
Re: XOOPS 2.5.12 Beta-2 available for Testing

Publisher cadch 08/30/2024 6:30

Who's Online

252 user(s) are online (4 user(s) are browsing XOOPS News)

Members: 0

Guests: 252

Donat-O-Meter

Stats
Goal:	$100.00
Due Date:	Nov 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}

{{ record.commit.author.name }} {{ record.commit.author.date | formatDate }}

Archives

News archives