Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-08 Thread Per Inge Mathisen
On Sat, Nov 7, 2009 at 7:09 PM, Christian Ohm chr@gmx.net wrote:
 Hey, I didn't decide that exactly. I'd branch 2.3 off from 2.2, and merge
 2.2_net into it. Then we release 2.3 betas/rcs from that, and keep 2.2 and 2.3
 in sync (apart from the netcode) until 2.3.0, accompanied by one last 2.2
 release.

Sounds like a lot of work... but I won't stand in the way if you want to do it.

  - Per

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-08 Thread Christian Ohm
On Sunday,  8 November 2009 at 13:50, Per Inge Mathisen wrote:
 On Sat, Nov 7, 2009 at 7:09 PM, Christian Ohm chr@gmx.net wrote:
  Hey, I didn't decide that exactly. I'd branch 2.3 off from 2.2, and merge
  2.2_net into it. Then we release 2.3 betas/rcs from that, and keep 2.2 and 
  2.3
  in sync (apart from the netcode) until 2.3.0, accompanied by one last 2.2
  release.
 Sounds like a lot of work... but I won't stand in the way if you want to do 
 it.

Well, that's what I would do, but I can't do the actual release builds etc. Not
sure if anyone else wants to keep 2.2 around. But I don't think the 2.3 beta
cycle should be very long, since most people will wait for a real release
anyway, so the parallel 2.2/2.3 phase shouldn't be that much work.

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-08 Thread bugs buggy
On 11/8/09, Christian Ohm chr.xx...@x.net wrote:
 On Sunday,  8 November 2009 at 13:50, Per Inge Mathisen wrote:
   On Sat, Nov 7, 2009 at 7:09 PM, Christian Ohm chr.x...@.net wrote:
Hey, I didn't decide that exactly. I'd branch 2.3 off from 2.2, and merge
2.2_net into it. Then we release 2.3 betas/rcs from that, and keep 2.2 
 and 2.3
in sync (apart from the netcode) until 2.3.0, accompanied by one last 2.2
release.
   Sounds like a lot of work... but I won't stand in the way if you want to 
 do it.


 Well, that's what I would do, but I can't do the actual release builds etc. 
 Not
  sure if anyone else wants to keep 2.2 around. But I don't think the 2.3 beta
  cycle should be very long, since most people will wait for a real release
  anyway, so the parallel 2.2/2.3 phase shouldn't be that much work.


Sorry guys, can't get the newer dev package to work correctly, and I
am out of time for doing a release today.

Thus, it is postponed, until I get back next week. :(

BTW, we would have 2.2_net, 2.2, 2.3.0 b1 (tag made from 2.2_net) and
trunk...right?

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


[warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-07 Thread bugs buggy
It is pretty obvious that we don't really have enough active
developers to test everything ourselves and I think it would be best
for us (and the project overall) if we start the ball rolling with a
new release.

2.2_net is 2.2's code + trunk's netcode which means, people can play
8p games again...
However, there could have been some other issues that crept in during
the merge, and so, we need lots more people to test things.

Should we release 2.2.5 b1, or just release it 2.3.0 b1 or what?

The plan is to push out something by Sunday night to get the testing
pool started.

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-07 Thread Kreuvf
Buginator, cybersphinx and me just decided to label the 2.2_net branch 2.3.0.

- Kreuvf



signature.asc
Description: OpenPGP digital signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-07 Thread Christian Ohm
On Saturday,  7 November 2009 at 18:59, Kreuvf wrote:
 Buginator, cybersphinx and me just decided to label the 2.2_net branch 2.3.0.

Hey, I didn't decide that exactly. I'd branch 2.3 off from 2.2, and merge
2.2_net into it. Then we release 2.3 betas/rcs from that, and keep 2.2 and 2.3
in sync (apart from the netcode) until 2.3.0, accompanied by one last 2.2
release.

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [warzone2100-dev] Pushing out 2.2.5 b 1 (or 2.3.0 b 1)

2009-11-07 Thread Kreuvf
Christian Ohm wrote:
 On Saturday,  7 November 2009 at 18:59, Kreuvf wrote:
 Buginator, cybersphinx and me just decided to label the 2.2_net branch 2.3.0.
 
 Hey, I didn't decide that exactly. I'd branch 2.3 off from 2.2, and merge
 2.2_net into it. Then we release 2.3 betas/rcs from that, and keep 2.2 and 2.3
 in sync (apart from the netcode) until 2.3.0, accompanied by one last 2.2
 release.
/me apologizes for misrepresenting cybersphinx's opinion. ;_;

- Kreuvf



signature.asc
Description: OpenPGP digital signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev