1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

New Publish Process

Discussion in 'Announcements' started by Toriad, Mar 14, 2014.

  1. Toriad
    Offline

    Toriad Shard Owner

    Joined:
    Mar 4, 2013
    Messages:
    86
    Likes Received:
    35
    Today the ServUO Developers would like to announce a new publish model. We have just been winging it for a long while. However, starting with this upcoming publish, we will start to follow a set release schedule. We hope that with this we will be far more predictable in what is getting released and when.

    My wife put together this beautiful info graphic for us. Check it out and I will explain it below.
    acloudup_com_czODikTCWNL__.png

    Let's start with the Publish. This part of the process should start at the end of the month when we make this next small publish. After we release a publish, we will then start planning the next publish. This process will span about 14 days, and will involve gathering data from the community on what they would like to see done, as well as making sure any flagged bugs from the last cycle get put in there to be fixed.

    Once the next publish is defined, we will announce to the community what we will be working on, and what to expect in the next publish. After this has been announced work will begin on the features and big bugs. This process is currently planned to take approximately 28 days, or 4 weeks.

    At the end of this big work phase we will take 14 days to go through whats left of the bug fixes on the forums, fix the simple ones and move the harder ones into a future publish. Once we have finished this we should be able to release the publish, with zero bugs in the report section.

    This 8 week cycle then will repeat with the next publish. Our primary goal is to, once again, create a predictable and easy to understand pattern of work!
     
    • Two Thumbs Up x 4
    • Winner x 3
    • Like x 1
    • Bravery Award x 1
    • Optimistic x 1
  2. m309
    Offline

    Admin Moderator ServUO Developer

    Joined:
    Mar 3, 2013
    Messages:
    1,243
    Likes Received:
    130
    Good stuff man!
     
  3. Ce Jayce
    Offline

    Ce Jayce Member

    Joined:
    Jan 24, 2014
    Messages:
    140
    Likes Received:
    14
    Awesome stuff!
    8 week release cycle will be interesting to see it in action. Will you be pushing bugs to the repo as and when they're fixed? Or will you only update it at the end on the cycle?
     
  4. Toriad
    Offline

    Toriad Shard Owner

    Joined:
    Mar 4, 2013
    Messages:
    86
    Likes Received:
    35
    Bug fixes and Minor contributions will still be pulled into master as they come in, but the dev team's focus will become making sure the features get done on time for that publish.
     
    • Two Thumbs Up Two Thumbs Up x 1
  5. Milva
    Offline

    Admin Moderator

    Joined:
    Mar 3, 2013
    Messages:
    3,425
    Likes Received:
    385
    Excellent News! So happy to see this happening :)
     
  6. NullDC
    Offline

    NullDC New Member

    Joined:
    Jan 22, 2014
    Messages:
    11
    Likes Received:
    0
    Hope someday, EC support be in basic build included. GJ & Good Luck!
     
    • Useful Useful x 1
  7. king
    Offline

    king New Member

    Joined:
    Feb 21, 2014
    Messages:
    10
    Likes Received:
    0
    Great news! A structured approach will only benefit the publish process :)
     
  8. Vorspire
    Offline

    Vorspire Vita-Nex: Core
    Admin ServUO Developer

    Joined:
    Jul 29, 2013
    Messages:
    845
    Likes Received:
    157
    This would be the perfect opportunity to work with repository branches, so that commits that are being worked can still be pushed to the repository and users can optionally merge those changes to test them.
    When the publish comes around, we merge the branch into the master and release it as an official publish.

    Just an idea... it's basically so that the community can still help with fixes/bugs and won't have to wait for a publish to happen before they can test it all.
     
  9. Punkte
    Offline

    Punkte Shard Owner

    Joined:
    Jun 13, 2014
    Messages:
    106
    Likes Received:
    25
    Aye, you guys should definitely be working with something like Git Gui + Bitbucket.

    We use it for our own server development process and it allows each person to work on stuff, commit changes in different branches, and when those updates are included and bug tested, merge them into the master branch and release the master as the a new publish.

    Definitely a great tool to be able to see all the changes that are going on, include or exclude them, etc.
     
    • Agree Agree x 1
Similar Threads: Publish Process
Forum Title Date
General Discussion Publish 98 - Real UO - 8/10/2017 Aug 11, 2017
Archived Bug Reports Publish 59: Champion Spawn Login Logout Jul 16, 2017
Archived Bug Reports Bulk Ordeds (Publish 95) Jun 24, 2017
Custom Releases Publish 97 - New Doom Stealables Jun 18, 2017
Custom Releases Publish 96's Wedding Items May 13, 2017
ServUO Discussion New pet training system on real UO publish 97. Apr 15, 2017
General Discussion Check out new real UO publish - Doom revamp. Jan 20, 2017