Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[blog] New versioning/release pattern
#1
From 0.9.5 onward PCSX2 has been a mostly open SVN revisioning process, where beta builds are SVN-marked and are widely built and distributed to users. 0.9.5 itself was never released as an official 'stable' build, and after the release of 0.9.6 we just called all subsequent SVN builds of PCSX2 "betas." (mostly because we were too lazy and/or busy to bother worrying of version numbers). This lackadaisical version pattern was a source of confusion for users and developers alike.

So starting with our next release of PCSX2 we'll be using an established versioning pattern (which likely won't be for some time -- implementing a new GUI is a complicated ordeal). The new patter will be based on some standard Open Source convention, where odd-numbered versions denote SVN/devel builds (and will have SVN numbers affixed to the version) and even numbered versions denote stable releases. By chance this is already how things have been playing out since 0.9.5, so mostly it just means we're making a conscious effort to continue to apply the pattern in the future. Thus, the past-present-future will look something like this:

Past:
0.9.4 - Official stable release
0.9.5 - Development build (SVN)

Present:
0.9.6 - Official stable release
0.9.7 - Development build (SVN) [wx-enhanced!]

Future:
0.9.8 - Official stable release
0.9.9 - Development build (SVN)
1.0.0 - Official stable release
1.1.0 - Development build (SVN)

This way when people file bug reports we can know from the main version number alone if the report is regarding a stable release or an SVN build, and furthermore users can have a clearer guide to the status of versions being released and such. Furthermore, odd versions will have the SVN revision appended to them by default, like 0.9.7.r1880.

... and yes the hope is that we're going to go to 1.0.0 after 0.9.9, and use a 1.0, 1.1, 1.2, 1.3, etc version pattern, shortening the primary version numbers from three digits to two. But that's a long way down the road yet, and anything could happen between now and then. Wink
Jake Stine (Air) - Programmer - PCSX2 Dev Team
Reply

Sponsored links

#2
This should clear up some of the naming convention confusion. I fully support this ^_^
[Image: 2748844.png]
Reply
#3
yeah a good system indeed
Reply
#4
I like the 3 digit format, which makes it feel unique from other emus Tongue2 (sorry for necroposting btw)
Windows 7 64bit
Intel Pentium Dual-Core E5200 OC to 3.6GHz, Intel GMA x4500, 1GB DDR2

NinjaMight just work on next guideNinja
Reply
#5
Time to necropost some more I'm afraid. Why is the stable release right now 1.2.1 and not 1.2.0? I would imagine it's because 1.2.0 got released as stable but had a showstopper bug so it had to be pulled and replaced by 1.2.1. If that's the case why don't I see 1.2.0 in the archive?

P.S. When do you think the Git builds will be stable enough to release 1.4? Laugh
[Image: pNm13X9.gif]
Windows 8.1 x64 | Intel Core i5 4670K @ 4.10GHz | Sapphire HD 7950 w/Boost 3GB | G.SKILL Ares 8GB (2x4GB) DDR3 1600 RAM | Crucial M500 120GB SSD | Toshiba 7200RPM SATA III 2TB HDD

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#6
(02-25-2015, 12:41 PM)karasuhebi Wrote: Time to necropost some more I'm afraid. Why is the stable release right now 1.2.1 and not 1.2.0? I would imagine it's because 1.2.0 got released as stable but had a showstopper bug so it had to be pulled and replaced by 1.2.1. If that's the case why don't I see 1.2.0 in the archive?

P.S. When do you think the Git builds will be stable enough to release 1.4? Laugh

Ref forgot to include somethingin 1.2.0, so they fixed it and named it 1.2.1
[Image: KHsig.png]
Reply
#7
take a look here for more details.
Intel I7 3970X|GTX 750TI|16gb ram| Samsung 850 EVO | Intel DX79TO

Low budget PC building guide for PCSX2

Reply
#8
Got it. Thanks Smile
[Image: pNm13X9.gif]
Windows 8.1 x64 | Intel Core i5 4670K @ 4.10GHz | Sapphire HD 7950 w/Boost 3GB | G.SKILL Ares 8GB (2x4GB) DDR3 1600 RAM | Crucial M500 120GB SSD | Toshiba 7200RPM SATA III 2TB HDD

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply




Users browsing this thread: 1 Guest(s)