Extend minimal time length between a proposal gained enough support and it can be submitted to submission thread to 14 days.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
It's actually 10 days, but I think one week have been rather common lately. I think that was because we all felt Yodamaster was working so rapidly on 1.51 that submission time could end any day.
It happens from time to time that I PM contributors that wait much too short time. Anyhow, what would the immidiate gain be from extending the time? Usually there is time to change a submission for a week or so after it was posted, as it isn't implemented at once.
It happens from time to time that I PM contributors that wait much too short time. Anyhow, what would the immidiate gain be from extending the time? Usually there is time to change a submission for a week or so after it was posted, as it isn't implemented at once.
This forum only show "1/2 week ago", so I think we should make the time length 7/14/21/etc days.
Yes, it should be 10 days but I must admit it is not easy to check after a week, as Kavotruo said (and I wrote it elsewhere). Problem is when a version is almost ready. If we wait even for a week, last submissions will have to wait two months before inclusion in next version. Otherwise, new version is delayed and new submissions could be made in between... and I understand some submissions are useful for balance and without them, version will perhaps miss something "important" only because of just some days too late.
First solution: a new AGCEEP version every month... No problem for me (I did it between 1.41 and 1.42, iirc). In this case, a not controversial submission will wait for 4 weeks max. And someone submitting stuffs after the third week knows submission will not be included in next version but the one after.
Second solution: We can decide and announce the date of next release in advance (at least two weeks before, for example) and it is the same as in first solution: we exactly know which submissions will be included or not.
Both solutions are compatible but we will never avoid rush to submissions before last possible day...
With this, I can't make mistakes or even revert to previous setup/version as I did (submission #650 for example).
OTOH, some submissons are more than obvious and some have already full support because they where discussed long before before final scripting. And difference between bugfix (immediate inclusion) and submission (10 days/week before inclusion) is not always clear.
I don't see where extending time length will change something or could benefit to the mod. We should have enough time between last inclusion and final version to revert if necessary.
That's why "Compiling version" thread is made and betas are available, after all => better information to modders and possibility to check/test/tweak/correct inclusions before final version.
First solution: a new AGCEEP version every month... No problem for me (I did it between 1.41 and 1.42, iirc). In this case, a not controversial submission will wait for 4 weeks max. And someone submitting stuffs after the third week knows submission will not be included in next version but the one after.
Second solution: We can decide and announce the date of next release in advance (at least two weeks before, for example) and it is the same as in first solution: we exactly know which submissions will be included or not.
Both solutions are compatible but we will never avoid rush to submissions before last possible day...
With this, I can't make mistakes or even revert to previous setup/version as I did (submission #650 for example).
OTOH, some submissons are more than obvious and some have already full support because they where discussed long before before final scripting. And difference between bugfix (immediate inclusion) and submission (10 days/week before inclusion) is not always clear.
I don't see where extending time length will change something or could benefit to the mod. We should have enough time between last inclusion and final version to revert if necessary.
That's why "Compiling version" thread is made and betas are available, after all => better information to modders and possibility to check/test/tweak/correct inclusions before final version.