Welcome, Guest. Please login or register.

Author Topic: Anyone working on PFS3 ??  (Read 18146 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: Anyone working on PFS3 ??
« Reply #104 from previous page: June 30, 2011, 02:24:02 PM »
Quote from: Cosmos;647725
When coders add some new changes on some sources, they bump the version or the revision numbers...

The source committed to SVN was for earlier PFS3 version (iirc PFS3 5.2 aka 18.4), since the very last src were lost. The source code has since been brought up to date and the current SVN should match the PFS3 5.3 (18.5) in features. See here: http://sourceforge.net/tracker/?func=detail&aid=3285730&group_id=532591&atid=2163218

The SVN "trunk" version is work in progress (and as such the revision hasn't been touched yet). The SVN trunk version isn't guaranteed to be stable at any given moment. Obviously there's nothing we can do to prevent anyone from releasing snapshot builds, but I would appreciate it if any such release would be accompanied with a warning about it being only a snapshot build.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: Anyone working on PFS3 ??
« Reply #105 on: June 30, 2011, 02:26:01 PM »
Quote from: Cosmos;647730
Pfs3 versions uploaded on Aminet in 2011 :

- binaries => v18.3
- sources => v18.4

http://aminet.net/package/disk/misc/PFS3_53 contains v18.5 though.
 

Offline x303

Re: Anyone working on PFS3 ??
« Reply #106 on: June 30, 2011, 06:53:01 PM »
Quote from: Piru;647735
The source committed to SVN was for earlier PFS3 version (iirc PFS3 5.2 aka 18.4)


Well, you might wanna bring RELNUM up-to-date. Currently it's still at 5.0.

Quote
The SVN "trunk" version is work in progress (and as such the revision hasn't been touched yet). The SVN trunk version isn't guaranteed to be stable at any given moment. Obviously there's nothing we can do to prevent anyone from releasing snapshot builds, but I would appreciate it if any such release would be accompanied with a warning about it being only a snapshot build.
So why not add an alpha or beta definition in the svn, like #define RELNUM "5.2 Beta" (or Alpha), which I did in my copy (unreleased though).