|
Delta Czukor
Registered User
Join date: 30 Dec 2004
Posts: 53
|
07-01-2006 23:33
First, I'd like to say that the Lindens have done a good job with these two new releases. Some good stuff here.
But... two versions? Each with something the other doesn't have? How's this gonna work?
Once 1.11 is tested and out on the main grid, will the code in that version be merged with 1.12?
If so, what happens from there? Will 1.12 stay in preview for a bit longer for even more testing before it goes live?
Just slightly confused because we've never had two upcoming versions at the same time before (in the relatively short time I've been with SL). Just wondering how it'll all come together.
|
|
Haravikk Mistral
Registered User
Join date: 8 Oct 2005
Posts: 2,482
|
07-02-2006 03:11
I think 1.12 is going to be in preview for a good while, so once 1.11 is done they will be merged. I don't really understand either though, there's some great functionality in 1.12, but it seems to over-shadow 1.11 which may not got as much testing as it should.
IMO only one release should be active, once 1.11 is properly tested then 1.12 can appear.
I suppose maybe there are two different groups of developers responsible for each release or something, and they both need testing at this stage but group changes and new land options will need MORE testing since they have to cope with money.
_____________________
Computer (Mac Pro):
2 x Quad Core 3.2ghz Xeon
10gb DDR2 800mhz FB-DIMMS
4 x 750gb, 32mb cache hard-drives (RAID-0/striped)
NVidia GeForce 8800GT (512mb)
|
|
Kelly Linden
Linden Developer
Join date: 29 Mar 2004
Posts: 896
|
07-02-2006 08:35
A glimpse into our current internal methodology.
We have several projects, each are seperate and working off a base set of code (what is currently deployed to the main grid). The 1.12 release is actually two such projects - Group Roles and Estate Land Sales - which were already merged.
Projects continually merge changes that go into release into their code.
The 1.11 release is expected to require much less testing, and the 1.12 release is expected to need a LOT of testing. When 1.11 is released then it will be merged into the base code. There-after all projects will merge those changes from the base into their projects code. This includes the 1.12 project.
After this is done a new 1.12 preview will be made with 1.11 features. Because of how this all works, it is actually possible, and maybe even likely, that 1.11 will get merged straight into 1.12 prior to 1.11's release. The 'base' code is only special because we say it is, there is nothing that prevents this kind of merge. The difficulty in this situation is that 1.12 will then have to keep up with any changes that get released (1.10.x) as well as new fixes made during 1.11's preview.
The 1.12 preview *will* continue after 1.11's release - hence why it is 1.12 and the other 1.11.
To be fair I am skeptical about the dual previews as well. I think it divides our base of testing users (you) to our disadvantage. At the same time I have been working on the Groups stuff for a LONG time (by LL development standards) and am very glad to finally see it reach you.
_____________________
- Kelly Linden
|
|
Feynt Mistral
Registered User
Join date: 24 Sep 2005
Posts: 551
|
07-07-2006 01:29
I can see where you're coming from with that, a division of testers makes it less likely that crippling bugs will be spotted and reported. At the same time it's a preview, and really there should be less bug hunting and more enjoyment of the fruits of your labour. I do like the dual release, it lets us see a distant future, but at the same time I have to wonder about why 1.12 doesn't have 1.11's enhancements. It will probably make more sense as 1.11's release grows closer and it's merged into 1.12.
|
|
Zonax Delorean
Registered User
Join date: 5 Jun 2004
Posts: 767
|
07-07-2006 06:32
From: Kelly Linden We have several projects, each are seperate and working off a base set of code (what is currently deployed to the main grid). The 1.12 release is actually two such projects - Group Roles and Estate Land Sales - which were already merged.
Projects continually merge changes that go into release into their code. This seems similar to OpenOffice.org's Child Workspaces development model. Though in that model, CWSes don't get separate version numbers, they have tags. Only the main program (OpenOffice) gets version numbers. From one version of OOo to the next, one or usally more child workspaces get merged. Maybe i would've named the current two previews as: 1.11-Group.1 and 1.11-Camera.1 |