Refer to my message of Sep. 15:
http://opensimulator.org/pipermail/opensim-dev/2015-September/026045.html
We take back contributions that are deemed important and technically
good, according to our judgement. The Avination donation falls into this
category. Since it is so large, it had to be handled in a special way --
6 weeks in quarantine. We did it because we want it -- vehicles
crossing, for example. We also did it because it could be done -- we
invited a new core developer because of it, Ubit, and he's been doing
the heroic job of removing all the inconsistencies between master and
the avinationmerge. Ubit has been a hero in this process! Large
donations that don't have a core developer to weave them through simply
don't work for us.
Cheers,
Diva
On 11/12/2015 4:18 PM, GarminKawaguichi wrote:
avinationmerge, avination or any avination you want is a fork of the
OpenSimulator Master exactly like MOSES is a fork of the OpenSimulator
Master. And Dev Core have explicitly told the team MOSES: no massive
injection of code into OpenSimulator Master; and that's just fine.
We are therefore entitled to assume that you are going to inject patch
by patch in the master. This is so that each grid manager, each user
of OpenSimulatorcan appreciate if all goes well for their own
interests and check in code that nothing undermine security
OpenSimulator Master.
This is what you intend to do, no?
If the answer is "no", then read everything you can find about open
source.
GCI
Le 13/11/2015 00:43, Melanie a écrit :
That code will be pulled down to master before 0.8.2 is cut, so will
be in the next release. {…}
And, since avinationmerge will become master just after 0.8.2, this
info is actually a head start for viewer devs.
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
