> 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 t
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.
Thanks,
>> 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.
The article is about Mercurial, no
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 allo
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
2011/3/22 Gerard Meijssen :
> 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 o
On Tue, Mar 22, 2011 at 1:51 PM, Gerard Meijssen
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 number of languages
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 wrote:
> > I brought two arguments, you do not address either. The issue is
> in
> 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,
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.
Tha
> 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 add
11 matches
Mail list logo
