Community Integrated Version

[2007Alain2007]

This is all so a copy off wleader idea that i have asked and he is ok for me to use

I spent a lot of time the last few days thinking about the various integrated versions that are out there and I think that as a community we can do better if we come up with a plan that will meet the needs of all the interested parties before we just start putting patches together.

What I have in mind is what I am calling a Community Integrated version. The idea is to create a clear set of guide lines or rules for an integrated version. What I have in mind is a version with a manager or integrator who is responsible for the integrating patches that have been selected for inclusion, and creating a publishing builds who works by a clear set of guide lines for determining which patches to include.

Ideally a build will be created periodically perhaps every other month. The process of creating a build will be something like the following:

Phase One - Working with the core developers a recent and mostly stable revision of the trunk will be selected. This revision will be the target revision for all patches that may be included in the build. The purpose here is to make it so all the patch developers are creating their patches against a specific revision to reduce the work on the integrator.

Phase Two - Patch developers will have a period of time perhaps a couple weeks to make their patches compatible with the revision selected in part one. While this adds a little maintenance work for patch developers it has the benefits of keeping the patches nearly current with the trunk, and demonstrates to the core developers that a patch has a maintainer who can help bring that patch into the trunk later.

Phase Three - Patches that have been made compatible with the selected revision and meet quality and security requirements are included in the build and once all qualified patches are integrated, the build is release.

Rinse and repeat. In theory there could be multiply builds at various phases of the cycle at the same time. For example, while the integrator is working on Phase 3 of Build A, Patch developers could be working on Phase 2 of Build B. I think that there could be up to two builds in the pipeline at any given time.

The main goals here are to adopt a rapid release cycle and make integration as easy as possible while providing patch developers clear and simple guide lines for getting their patches included. The reason why I consider this to be a 'Community' version, is that anyone that agrees to the rules can get their patch included.

The only way to get a patch tested in a multi-player game with real players is to have it included in and Integrated version.

I'm ready to volunteer and attempt tobe a integrator , but before I do, I would like to hear what other developers think.

[2007Alain2007]

Bug reporting

If you find a bug or any kind of problem using CIV you should do the following:

* If the problem is not directly related to any of the patches that CIV adds, try to reproduce the problem with latest nightly. If the problem appears in a clean nightly too, then it is not related to CIV but to OpenTTD as a whole.

* If the problem is directly related to one of the patches in CIV, try to reproduce the problem in a build that only has that patch (usually, patch developers provide them). If you can reproduce it, then the bug is related to that patch.

* If you can't reproduce the problem in any of these two tests, you can't find a binary for the related patch, you don't understand what I mean or simply you are too lazy to do these tests, post the bug in this thread and I'll handle it. Patchpacks, by their own nature, create a load of problems that developers (both of patches and OpenTTD) shouldn't need to worry about.

* In short: when in doubt, post your problem here and let me worry about it. Don't expect us to be get back right way

Save game files pictures and bug reports are help full in all cases

Programs

That i myself will be useing TortoiseSVN Version 1.5.9 and MSYS Version 1.0.10

[2007Alain2007]

need for patch list and bug reports and builds

v1
airport-close-v7-r17398(17468) (still a bug here becuse of the show_station_coverage_v1_17250(17491) add in V3 )
chunnelv11_r17206(17468)
diesel_smoke_sz_3-0c_r17352(17450)
no_local authority_r16708(17450)
day_length_r17411(17468)
trafficlights_r17455(17468)



V2
Added
r17288_numbers_on_station_list
random_road_construction_r17455



V3
Added
r17455_more_airport_1_holding_pattern
show_station_coverage_v1_17250(17491)



V4
Added
signaltunnel_V25_r17139
build_while_pause_in_editor-15895
load_face_on_new
default_economy_sustained-pct-affect_sz_r16694



V5
added
r17420_limit_rv_speed
rv_acceleration_v8_r17453
yapf_vehicle_penalty_r17469

V6
add
tracking_viewport_v3_r16242
better_min_profit_rating_r17533

V7
updated
updated signaltunnel_V25 to signaltunnel_V26

V8
update
rv_acceleration_v8_r17453 to rv_acceleration_v9_r17549
add
airport-upgrade-v6-r17481

V9
added
found_town_v14_r17558
minimap_toggle_contours_2-r17533
query_land_shortcut
rating_town_label_v0.71_r17558
station_rating_gui_r17533
transfer_shift_click_r17558

V10
added
no_aircrash_r15812
update
Found a town [v14-r17558] small code change
rv_acceleration_v9_r17549 to rv_acceleration_v10_r17571

V11
added
group_by_property_r17594

[peter1138]

lol

[adf88]

The idea is nice, but realisation sucks. "PM me" is not a way. You would have to crate special web site with accounts, code repository, bug tracker, planned features / realization progress, various reports, suggestions etc ... At least use code.google.com

[Jans]

I think Alain try to make a new patchpack. But he won´t do it alone. In his thread nobody answer for the question of help. So he try something else. He told he have learned something about patching. I think you can see if you read his thread.
Now he want to find some body wich want to help to make a real good patch pack. He try to speak to the developer of the patches and so on. I think it is the normal way if you want some body help you.

And now? Some body you look like to know all thinks in the world would laugh. The told you have to do completly different thinks.
Why you could not explain a bit more. How to make it? Why you only tell him don´t do it like this you have to do another way? Try to help him. Say i would prefer ... maybe you could reach the goal like this. If you do that I can help you.

I hope he could make a good new patchpack. If I have time i like to help you. But at the moment I don´t know how.

[adf88]

Alain, first step is to gather few persons who would participate. Define exact goals and a way they'll be realized. Make a starting plan, prepare a website.
Starting from gathering patches doesn't lead to anything worth of notice.
If this is done properly maybe I would participate.

[2007Alain2007]

Just setting up the http://code.google.com/p/civopenttd/ web site adf88 had the idea so thank you very much for the help there

Now i am waiting to see if any one is welling to participate in the goals so far for Community Integrated Version

[Leanden]

Tbh alain i can't see this getting off the ground, i can't see all the patch developers out there changing what revision they are working to just to suit your patch pack, and i expect you will start delegating all the work out again.

[2007Alain2007]

edit spelling

It's not my patch pack its a Community Integrated Version i'm just letting the developers say they've got a patch they'd like to test with the Community and this is a big goal I set for myself and every one else.

Also i think this will be great for the developers to get their patch out and tested by the Community as a whole.

[Leanden]

"It's not my patch pack its a Community Integrated Version i'm just letting the developers say they've got a patch they'd like to test with the Community and this is a big goal I set for myself and every one else.

Also i think this will be great for the developers to get their patch out and tested by the Community as a whole."

Please, spelling. I'm your friend Alain, so don't take this the wrong way, but i honestly just see this as another of your patch packs, and it won't be all that community driven.

[audigex]

It's a good idea, I just can't see it working out.

It's certainly worth a go though - would it be all that much harder for patch devs to all choose a certain revision once a month (maybe everyone makes their patch compatible with the first nightly of the month); rather than just whatever nightly happens to be there when they make a change.

There's a lot of patches I'd love to see in one build, so if nothing else I hope it works out

[Leanden]

I think a convention should be set that patchers post in the title what build they are most recently compatible with.

[Ammler]

The Idea isn't new, checkout http://wiki.openttd.org/CIV, maybe you can "reuse" something there...

[2007Alain2007]

Hi audigex

were all going to aim for the first nightly of the each month


Hi Ammler

I am reusing A LOT of his ideas for my own

I going now to add a topic in the openTTD for devlelopers to post there pacths that are up to date on the revision that fulls on the 1st of the month

so now were going to look at all the patchs out there and hope fully up date them a bit this week and see if we all can get A LOT of theres patchs to a set revision of openttd and made in to a nice build

1st find patch
2nd update patchs to meet the revision that full on the frist of every month
3rd review all patchs and test on there own
4th work out any bugs
5th join all patchs togiver in one patch file
6th upload to code.google.com
7th make as many builds as we can
8th do it all again

I hope every one likes this idea

[dihedral]

Edit: ""

[Noldo]

Few open questions pop in to my head.

1.1 What does CIV maintainer(s) get out if this?
1.2. What does this require from CIV maintainer?
2.1 What do patch developers get out if this?
2.2 What does this require from patch developers?
3. What's in it for users?
4. What's in it for openttd developers?

[Yexo]

Few open questions pop in to my head.

Let me answer what I can.

2.1 What do patch developers get out if this?

They get their patch tested in a patchpack, which is not really that usefull, since bugs might be due to other patches or integration errors.

2.2 What does this require from patch developers?

To update their patch to a certain revision, and, if Alain is making the patchpack, to integrate it in the patchpack.

3. What's in it for users?

Just another patchpack to play which is savegame incompatible with later trunk.

4. What's in it for openttd developers?

Nothing.

[2007Alain2007]

1.1 What does CIV maintainer(s) get out if this?
larning of C++ there best loved patchs to stay in and up to date

1.2. What does this require from CIV maintainer?
just to try there best to keep there patchs up to date and help out on any bugs that are found

right now i am working on updateing improved-breakdowns-v2.4 r15209

[Terkhen]

2007Alain2007: To have further info about why patch packs don't help as much as you think with development (in addition of what Yexo already posted) you can check this post (which is inmediately next to the post from which you copy pasted your introduction).

Once cleared that patch packs don't help that much with development, I want to add that I share the opinion already posted by a lot of people. You are just doing the same again: this time trying to find a good excuse to get help but still sending PMs spamming people with requests for help and, in general, keeping the same attitude than with KGAT.