All these projects do not update their localisation to live environments on
a daily basis including environments on a previous release. The localisation
for these projects is very much part of a release strategy and this is not
the practice we have in place for MediaWiki installations.
I
As to Toolserver, this environment and its functionality is deeply flawed.
As the tools are open source, there is no reason why relevant tools cannot
be brought into GIT and upgraded to a level where they are of production
quality. Either GIT is able to cope or its distributed character adds
Hoi,
I brought two arguments, you do not address either. The issue is introducing
GIT, there are production processes that will break. Not addressing this and
not proving that it can provide the goods is at issue. I suggest proving GIT
in an environment where our production will not get broken.
I brought two arguments, you do not address either. The issue is introducing
GIT, there are production processes that will break. Not addressing this and
not proving that it can provide the goods is at issue. I suggest proving GIT
in an environment where our production will not get broken.
Hoi,
Does any of these communities have *daily updates* of its localisations in
some 300 languages to its production environment? If so can you give
references?
Thanks,
GerardM
On 22 March 2011 19:31, Ryan Lane rlan...@gmail.com wrote:
I brought two arguments, you do not address either.
On Tue, Mar 22, 2011 at 1:51 PM, Gerard Meijssen
gerard.meijs...@gmail.com wrote:
Hoi,
Does any of these communities have *daily updates* of its localisations in
some 300 languages to its production environment? If so can you give
references?
Thanks,
GerardM
I dont see how neither the
2011/3/22 Gerard Meijssen gerard.meijs...@gmail.com:
Hoi,
I brought two arguments, you do not address either. The issue is introducing
GIT, there are production processes that will break. Not addressing this and
not proving that it can provide the goods is at issue. I suggest proving GIT
in
Gerard asks:
Does any of these communities have *daily updates* of its localisations in
some 300 languages to its production environment? If so can you give
references?
You can go to http://git-scm.com/ and see git projects for:
Linux Kernel
Perl
Eclipse
KDE
Ruby on Rails
Android
PostgreSQL
Mark Wonsil wrote:
I haven't used git yet but after reading the excellent article that
Rob Lanphier posted (http://hginit.com/00.html), I think I will. That
article also explains why there wouldn't have to be as many updates to
SVN as is done today.
I don't see that conclusion. A DCVS allows
Mark Wonsil won...@4m-ent.com wrote:
I haven't used git yet but after reading the excellent article that
Rob Lanphier posted (http://hginit.com/00.html), I think I will. That
article also explains why there wouldn't have to be as many updates to
SVN as is done today.
The article is about
Hoi,
All these projects do not update their localisation to live environments on
a daily basis including environments on a previous release. The localisation
for these projects is very much part of a release strategy and this is not
the practice we have in place for MediaWiki installations.
11 matches
Mail list logo
