• New Horizons on Maelstrom
    Maelstrom New Horizons


    Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!

build 13.1 vs build 14?

B

BelThorne

Freebooter
Storm Modder
Pirate Legend
Just a few thoughts about where we're taking the build versions from here.

Maybe all you pro's have already thought of all this, but anyway:

My thoughts:

Make build 13.1 a bug fix version. no new content, but any fixes to old stuff get added to this.

Build 14 alpha has all the new mods that we can stuff into it.

Not sure how well this would work as someone would need to keep track of the two versions.


If we were going to do that, we'd probably want to start looking at having a source controll system, so people could check in their own changes and such.

What do people think?
 
But what to do with the mods that are already working (almost) right but are not added to Build 13 yet? I had wanted to make these available as an add-on for Build 13 some time soon, so I thought we could add those to Build 13.1. Should all these wait for Build 14?
 
<!--quoteo(post=172827:date=Nov 21 2006, 06:17 PM:name=Pieter Boelen)--><div class='quotetop'>QUOTE(Pieter Boelen @ Nov 21 2006, 06:17 PM) [snapback]172827[/snapback]</div><div class='quotemain'><!--quotec-->
But what to do with the mods that are already working (almost) right but are not added to Build 13 yet? I had wanted to make these available as an add-on for Build 13 some time soon, so I thought we could add those to Build 13.1. Should all these wait for Build 14?
<!--QuoteEnd--></div><!--QuoteEEnd-->

Yeah, maybe we'll just keep going adding fixes and working mods as we go. Probably a lot more appropriate for a project like this. <img src="style_emoticons/<#EMO_DIR#>/yes.gif" style="vertical-align:middle" emoid=":yes" border="0" alt="yes.gif" />
 
Having a stable 13, with 'patches' made that only address bugs, and then a completely untested and unstable 14, with a glob of mods all struggling to work, would be a nice way to do things.

But the way it is, that wont happen.

Two seperate projects usually is how the industry does it. They release to public, a fairly stable version. And then only release to public small patches and fixes for that large point version. In the background, with a bunch of testers, and coders, they are already working on the next big point release.

However due to the nature of how messy a process that is, they dont make it wildly public. Because (and its been proven here many times), people who are not aware of something being 'beta' nor being able to cope with the riggors of testing, tend to bitch and moan and complain to those who do who are working on the 'the next big release'. Its tiresome for coders to deal with that.

Since the "Build Mod" is basically always public, and always in the works, trying to do two seperate projects in this mannor, just doesnt seem feasible.

Persoanlly I would love to see 'bug fix only' patches for Build 13, instead of wait till some 'update' that is filled with a slew of untested and new mods that will introduce more problems than the two or three bug fixes that might also be burried in that update.
 
I am very relieved that we have finally a comparatively stable Build, and i would hate it if this stability would already be destroyed again by adding yet another big bunch of untested stuff. So IF you add those new mods to Build 13.1 then PLEASE keep 13.0 available; for those who, like me, would like to rest on firm ground for a while after swimming for almost two years <img src="style_emoticons/<#EMO_DIR#>/icon_wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="icon_wink.gif" />

I will try to make my future mods as selfcontained, stand alone packs that will work with any future Buildversion. I think that can be done by keeping all code in new seperate files that do not interfere with existing code, and if those seperate files are being left alone by others <img src="style_emoticons/<#EMO_DIR#>/wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" /> I wont have any incompatability problems anymore (please leave me my illusions <img src="style_emoticons/<#EMO_DIR#>/icon_mrgreen1.gif" style="vertical-align:middle" emoid=":cheeky" border="0" alt="icon_mrgreen1.gif" /> ).

Though given the tangled web that the PotC code is that "selfcontained" approach will not work for most projects that are being discussed here.


BTW, "source control system" sounds like something we desperately need <img src="style_emoticons/<#EMO_DIR#>/yes.gif" style="vertical-align:middle" emoid=":yes" border="0" alt="yes.gif" />
 
<!--quoteo(post=172876:date=Nov 22 2006, 01:18 AM:name=IncredibleHat)--><div class='quotetop'>QUOTE(IncredibleHat @ Nov 22 2006, 01:18 AM) [snapback]172876[/snapback]</div><div class='quotemain'><!--quotec-->
Persoanlly I would love to see 'bug fix only' patches for Build 13, instead of wait till some 'update' that is filled with a slew of untested and new mods that will introduce more problems than the two or three bug fixes that might also be burried in that update.
<!--QuoteEnd--></div><!--QuoteEEnd-->

Maybe keep working on new stuff for build 13.1, but in a month or so, someone can just go through the bug list on the bug tracker and pick out the appropriate fixes and make a 13.0.2 build or something.
 
What does everyone think of this idea: We release the new mods in small packs. We then work on fixing the bugs with these new mods and once they're fixed, we add some other new mods. That should work better than just putting ALL new mods together, because doing it that way, you'll never know exactly which mod causes a certain bug, meaning we'd have to check them all, which would be a lot of work. The only problem with this is that it requires a modpack compiler to work on this and I don't have that much spare time anymore. <img src="style_emoticons/<#EMO_DIR#>/unsure.gif" style="vertical-align:middle" emoid=":?" border="0" alt="unsure.gif" />
 
I believe that is a good idea Pieter. It may also be a smart move to release new builds more frequently. That way an extensive bugtesting gets done more frequently so the modders don't have to dig through mods placed on mods to find a bug that was created 1 1/2 years ago. Build 13 added so much new content that it probably could have split into several builds. <img src="style_emoticons/<#EMO_DIR#>/par-ty.gif" style="vertical-align:middle" emoid=":cheers" border="0" alt="par-ty.gif" />
 
I agree, Pieter. Releasing small updates, with a couple of new mods might not be a bad idea at all. Also making sure we get a regular release of patches done until everything we can fix should be a top priority decision/solution.

Something else we should consider is attempting to keep mods separated into thier own individual files if at all possible, making it easier to fix things that pertain to a specific mod.

If unable to keep them in thier own files, we should be sure to add plenty of comments to the additional code, so future modders will have a very good idea of what we were up to with any one mod or changes we made to it.

Cap'n Drow
 
NO NO NO put all new correct working mods in build 13.1
jonathan shut :p its always been this way <i>i guess</i>
I can't and maby some other people 2 to have all the new mods
 
<!--quoteo(post=173436:date=Nov 26 2006, 12:36 PM:name=Pieter Boelen)--><div class='quotetop'>QUOTE(Pieter Boelen @ Nov 26 2006, 12:36 PM) [snapback]173436[/snapback]</div><div class='quotemain'><!--quotec-->
What does everyone think of this idea: We release the new mods in small packs. We then work on fixing the bugs with these new mods and once they're fixed, we add some other new mods. That should work better than just putting ALL new mods together, because doing it that way, you'll never know exactly which mod causes a certain bug, meaning we'd have to check them all, which would be a lot of work. <!--QuoteEnd--></div><!--QuoteEEnd-->
Absolutely right <img src="style_emoticons/<#EMO_DIR#>/yes.gif" style="vertical-align:middle" emoid=":yes" border="0" alt="yes.gif" /> Never bite of more than you can swallow.

<!--quoteo(post=173535:date=Nov 27 2006, 08:00 AM:name=Cap'n_Drow)--><div class='quotetop'>QUOTE(Cap'n_Drow @ Nov 27 2006, 08:00 AM) [snapback]173535[/snapback]</div><div class='quotemain'><!--quotec-->
Something else we should consider is attempting to keep mods separated into thier own individual files if at all possible, making it easier to fix things that pertain to a specific mod.

If unable to keep them in thier own files, we should be sure to add plenty of comments to the additional code, so future modders will have a very good idea of what we were up to with any one mod or changes we made to it.
<!--QuoteEnd--></div><!--QuoteEEnd-->
Absolutely right as well <img src="style_emoticons/<#EMO_DIR#>/yes.gif" style="vertical-align:middle" emoid=":yes" border="0" alt="yes.gif" /> <img src="style_emoticons/<#EMO_DIR#>/yes.gif" style="vertical-align:middle" emoid=":yes" border="0" alt="yes.gif" />
 
You must log in or register to reply here.
Back
Top