Releases in the future
36 views
Skip to first unread message
Lego3
Jan 28, 2012, 5:55:01 AM1/28/12
to CorsixTH Development
Hi people!
I would like to change a few things when it comes to releases:
1. We change the naming convention to 0.xx, similar to OpenTTD letting
the next release be called 0.01.
2. A week for testing with no new features added.
3. A specific test procedure testing different aspects of the game on
different platforms.
Small things, but important. What do you think?
/Lego3
I would like to change a few things when it comes to releases:
1. We change the naming convention to 0.xx, similar to OpenTTD letting
the next release be called 0.01.
2. A week for testing with no new features added.
3. A specific test procedure testing different aspects of the game on
different platforms.
Small things, but important. What do you think?
/Lego3
Message has been deleted
Edvin Linge
Jan 28, 2012, 1:53:30 PM1/28/12
to corsix...@googlegroups.com
2. I mean major releases.
3. Yes, it would require a test procedure, one part platform specific, and
one part game specific. But I’d say it wouldn’t take too long. Special cases are
of course hard to think of, but a rudimentary procedure testing all “normal”
aspects like buttons and standard game play should be fairly easy to write
down.
/Edvin
1:
Nothing wrong with that.
2: Do you mean we should test every patch for one week? No matter how small they are? Or do you mean that "releases" are major releases like the betas?
I'm not really into how OpenTTD release their patches, I have just downloaded the versions sporadically.
3: This is a good idea, since all the testing up to now is just "random play". But the problem is to write a test procedure that covers all aspects that could go wrong.
2: Do you mean we should test every patch for one week? No matter how small they are? Or do you mean that "releases" are major releases like the betas?
I'm not really into how OpenTTD release their patches, I have just downloaded the versions sporadically.
3: This is a good idea, since all the testing up to now is just "random play". But the problem is to write a test procedure that covers all aspects that could go wrong.
Message has been deleted
Edvin Linge
Jan 29, 2012, 7:00:22 AM1/29/12
to corsix...@googlegroups.com
It would of course be very nice to have such a big new feature in the next
release, but I’m not against a release without it. More important in that case
is to get the test procedures going. Are the “VIP stopping doors” problems
completely gone?
If you want to and have the time for it you can start a new wiki page with
an in-game test procedure.
/Edvin
I
think it all sounds great then.
The game is pretty stable right now (much more stable than beta 8), but maybe you want the epidemics to be in the next release?
I have talked to "sadgur" in the IRC channel, who said he was partly working on the epidemics, so maybe it can soon be ready for testing.
-- Grimdoc
The game is pretty stable right now (much more stable than beta 8), but maybe you want the epidemics to be in the next release?
I have talked to "sadgur" in the IRC channel, who said he was partly working on the epidemics, so maybe it can soon be ready for testing.
-- Grimdoc
Message has been deleted
Lego3
Mar 4, 2012, 3:13:03 AM3/4/12
to CorsixTH Development
Ok, I think it's time to start preparing for a new release. :-)
How about March the 24th? That would mean a feature freeze and start
of test period the 17th.
/Lego3
On Jan 29, 11:04 pm, Ola Skogrand <grim...@gmail.com> wrote:
> Having something "new" in the next release would also please the crowd and
> attract more people. But if we are going to release something big and new,
> then we should at least be sure it's stable (which is done by testing it
> for a week, and running the test procedures, as you proposed).
>
> If something new is around the corner, then I say we should wait for it.
> But that relies on "sadger". He has a crude version ready, but people could
> get infected across rooms for example (did not take walls into account for
> the contagion distance), so it's not ready for testing I guess.
>
> I think we should make it much clearer and easier for people to download
> the latest revision (of course with a warning telling them it's a test
> version and may be unstable).
> Having more people testing new versions would help us getting more relevant
> error reports and maybe take a little some work off our shoulders for
> testing.
>
> I can start writing a new routine soon. Maybe I can get really into it
> tomorrow.
>
> -- Grimdoc
> > *Sent:* Sunday, January 29, 2012 2:24 AM
> > *To:* corsix...@googlegroups.com
> > *Subject:* Re: Releases in the future
> >> *Sent:* Saturday, January 28, 2012 6:42 PM
> >> *To:* corsix...@googlegroups.com
> >> *Subject:* Re: Releases in the future
How about March the 24th? That would mean a feature freeze and start
of test period the 17th.
/Lego3
On Jan 29, 11:04 pm, Ola Skogrand <grim...@gmail.com> wrote:
> Having something "new" in the next release would also please the crowd and
> attract more people. But if we are going to release something big and new,
> then we should at least be sure it's stable (which is done by testing it
> for a week, and running the test procedures, as you proposed).
>
> If something new is around the corner, then I say we should wait for it.
> But that relies on "sadger". He has a crude version ready, but people could
> get infected across rooms for example (did not take walls into account for
> the contagion distance), so it's not ready for testing I guess.
>
> I think we should make it much clearer and easier for people to download
> the latest revision (of course with a warning telling them it's a test
> version and may be unstable).
> Having more people testing new versions would help us getting more relevant
> error reports and maybe take a little some work off our shoulders for
> testing.
>
> I can start writing a new routine soon. Maybe I can get really into it
> tomorrow.
>
> -- Grimdoc
>
>
>
>
>
>
>
> On Sun, Jan 29, 2012 at 1:00 PM, Edvin Linge <edvin.li...@gmail.com> wrote:
> > It would of course be very nice to have such a big new feature in the
> > next release, but I’m not against a release without it. More important in
> > that case is to get the test procedures going. Are the “VIP stopping doors”
> > problems completely gone?
>
> > If you want to and have the time for it you can start a new wiki page with
> > an in-game test procedure.
>
> > /Edvin
>
> > *From:* Ola Skogrand <grim...@gmail.com>
>
>
>
>
>
>
> On Sun, Jan 29, 2012 at 1:00 PM, Edvin Linge <edvin.li...@gmail.com> wrote:
> > It would of course be very nice to have such a big new feature in the
> > next release, but I’m not against a release without it. More important in
> > that case is to get the test procedures going. Are the “VIP stopping doors”
> > problems completely gone?
>
> > If you want to and have the time for it you can start a new wiki page with
> > an in-game test procedure.
>
> > /Edvin
>
> > *Sent:* Sunday, January 29, 2012 2:24 AM
> > *To:* corsix...@googlegroups.com
> > *Subject:* Re: Releases in the future
>
> > I think it all sounds great then.
> > The game is pretty stable right now (much more stable than beta 8), but
> > maybe you want the epidemics to be in the next release?
> > I have talked to "sadgur" in the IRC channel, who said he was partly
> > working on the epidemics, so maybe it can soon be ready for testing.
>
> > -- Grimdoc
>
> > I think it all sounds great then.
> > The game is pretty stable right now (much more stable than beta 8), but
> > maybe you want the epidemics to be in the next release?
> > I have talked to "sadgur" in the IRC channel, who said he was partly
> > working on the epidemics, so maybe it can soon be ready for testing.
>
> > -- Grimdoc
>
> > On Sat, Jan 28, 2012 at 7:53 PM, Edvin Linge <edvin.li...@gmail.com>wrote:
>
> >> 2. I mean major releases.
>
> >> 3. Yes, it would require a test procedure, one part platform specific,
> >> and one part game specific. But I’d say it wouldn’t take too long. Special
> >> cases are of course hard to think of, but a rudimentary procedure testing
> >> all “normal” aspects like buttons and standard game play should be fairly
> >> easy to write down.
>
> >> /Edvin
>
> >> *From:* Ola Skogrand <grim...@gmail.com>
>
> >> 2. I mean major releases.
>
> >> 3. Yes, it would require a test procedure, one part platform specific,
> >> and one part game specific. But I’d say it wouldn’t take too long. Special
> >> cases are of course hard to think of, but a rudimentary procedure testing
> >> all “normal” aspects like buttons and standard game play should be fairly
> >> easy to write down.
>
> >> /Edvin
>
> >> *Sent:* Saturday, January 28, 2012 6:42 PM
> >> *To:* corsix...@googlegroups.com
> >> *Subject:* Re: Releases in the future
>
> >> 1: Nothing wrong with that.
>
> >> 2: Do you mean we should test every patch for one week? No matter how
> >> small they are? Or do you mean that "releases" are major releases like the
> >> betas?
> >> I'm not really into how OpenTTD release their patches, I have just
> >> downloaded the versions sporadically.
>
> >> 3: This is a good idea, since all the testing up to now is just "random
> >> play". But the problem is to write a test procedure that covers all aspects
> >> that could go wrong.
>
> >> 1: Nothing wrong with that.
>
> >> 2: Do you mean we should test every patch for one week? No matter how
> >> small they are? Or do you mean that "releases" are major releases like the
> >> betas?
> >> I'm not really into how OpenTTD release their patches, I have just
> >> downloaded the versions sporadically.
>
> >> 3: This is a good idea, since all the testing up to now is just "random
> >> play". But the problem is to write a test procedure that covers all aspects
> >> that could go wrong.
>
Lego3
Mar 18, 2012, 4:45:03 AM3/18/12
to CorsixTH Development
I've made a branch for the upcoming release. Will continue preparation
work when I get home tonight.
/Lego3
work when I get home tonight.
/Lego3
Message has been deleted
Edvin Linge
Mar 18, 2012, 4:17:52 PM3/18/12
to corsix...@googlegroups.com
Yes, I would really like it if we could get as many language updates as
possible before the release. Could you make a new thread in the translator group
and urge everyone to give updates to their languages?
/Lego3
Subject: Re: Releases in the future
Ok,
so then it will be bug fixing and test runs for a week? And then a release the
upcoming weekend?
I guess translation updates can be added though, since that has no impact on the stability (as long as the code isn't broken, but that's easy to see).
-- Grimdoc
I guess translation updates can be added though, since that has no impact on the stability (as long as the code isn't broken, but that's easy to see).
-- Grimdoc
Message has been deleted
Edvin Linge
Mar 18, 2012, 6:25:11 PM3/18/12
to corsix...@googlegroups.com
Are you sure? I saw that you made a thread in the forum about additional
strings, but I can’t find anything in the translators google group.
Hehe.
I did that two days ago :)
Reply all
Reply to author
Forward
Message has been deleted
0 new messages