The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Cpanel 16448, edge, release, stable ??

Discussion in 'General Discussion' started by nyjimbo, Aug 17, 2007.

  1. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Looking at the change log and the downloadable files we are currently showing 16448
    for all three (edge, release, stable). However significant changes to DNS/BIND and Antirelayd show on the changelog for edge and release.

    How is it possible that these changes are listed in edge and release but not in stable yet all three are 16448 and were posted within hours of each other.

    Anyone know if the 16448 edge is the same as the 16448 stable?. :confused:
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    16448 EDGE is not the same as 16448 STABLE and so forth.
     
  3. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Ok, but in this thread/post : http://forums.cpanel.net/showthread.php?t=69706

    cpanelkenneth
    Staff said:

    For the release of cPanel 11 Stable, we decided not to do a changelog. One reason being the amount fo time it would take to construct such a behemoth. Another reason being the resulting size. Any new Stable releases from this point forward will have change log entries.

    The Stable release at this point has everything that is in Release and Current. You can get a general idea of recent development by reviewing the recent changelogs for those builds.


    So I am confused.... :confused:
     
  4. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Generally, when Release, Current and Stable have the exact same build number (such as 16448), then the majority of the features/fixes are the same. Edge, will always have more features/fixes than the other branches, even when all have the same build number.

    The flow for features and fixes is: Edge -> Current -> Release -> Stable If you examine the change log you will see the following:

    Current 16386 - Added logic to install antirelayd for source if not present, or if exim is reinstalled via /scripts/eximup

    Release 16391 - Added logic to install antirelayd for source if not present, or if exim is reinstalled via /scripts/eximup

    This fix was actually in an earlier build of Edge, but in the build-up (no pun intended) to Stable, the change log for the Edge builds between 16257 and 16448 weren't published, rather they were rolled into the change log for Edge 16448

    The people doing the change log entries are rather new at it and prone to make some mistakes in clarity.

    With that being said, I believe Stable, Release and Current are all the same at this point in time.
     
  5. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Keep in mind that EDGE -> CURRENT -> RELEASE -> STABLE is a trickle-down system of functionality. As functionality is more thoroughly tested, the closer it gets to being placed in STABLE.

    Generally CURRENT and RELEASE are very similar, RELEASE not getting as many updates because functionality in CURRENT must reach a certain quality assurance threshold before being pushed to RELEASE. So, when the CURRENT and RELEASE builds match, there are very many similarities between the builds (virtually identical). The same is the case with RELEASE and STABLE.

    However, EDGE is a completely different entity all-together, hence the differences between the changelog for EDGE vs. CURRENT but the similarities in the changelog of CURRENT vs. RELEASE.

    Personally, if I wanted to know all that was in the latest STABLE build, I'd read the changelog for RELEASE (though CURRENT would contain the same changelog information over this period of time).
     
  6. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Make sense except :

    FreeBSD

    STABLE
    11.10.0-STABLE_16448
    (Thu Aug 16 02:10:29 2007)

    EDGE
    11.11.0-EDGE_16448
    (Wed Aug 15 21:46:22 2007)

    So is it safe to assume that the time stamps do not mean that stable is newer than edge and edge actually has more fixes/updates even though its much older than stable ??

    ps- notice you have 11.10 and 11.11, but 11.10 is newer timestamp across the board on the EDGE cpanel downloads screen ???
     
    #6 nyjimbo, Aug 17, 2007
    Last edited: Aug 17, 2007
  7. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    The time stamps only means that is when that particular build hit that particular server. If one of the build machines happened to be a bit faster in building/publishing then you can have instances like the above.


    As far as determining fixes and features, the timestamps mean very little. It's the build number that gives the proper information.
     
Loading...

Share This Page