Hoi,
A minor point, i18n updates will be available through the
localisationupdate extension.
Thanks,
GerardM
On 25 February 2013 16:02, Mark A. Hershberger m...@everybody.org wrote:
After the discussion last week, I want to scope out a release policy so
that we'll all know what to
I'm fine either way with this change. I was just hesitant because I wasn't
sure whether HTMLForm was designed in a matter where front-end developers
were expecting all divs.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com |
Hoi,
I googled for IcuCollation and found this on their website ... Starting in
release 1.8, the ICU Collation Service is updated to be fully compliant to
the Unicode Collation Algorithm (UCA) (
http://www.unicode.org/unicode/reports/tr10/ ) and conforms to ISO 14651.
My question, will we use a
IcuCollation is the name of the mediawiki class. The actual underlying code
is from a software project called Icu (or more specificly icu4c). Which
version used depends on which version mediawiki is compiled against.
Version 1.8 is really really old (which makes me think you got the wrong
software
True. But I believe the vast majority of third party users do not have that
extension installed.
-bawolff
On 2013-03-02 7:30 AM, Gerard Meijssen gerard.meijs...@gmail.com wrote:
Hoi,
A minor point, i18n updates will be available through the
localisationupdate extension.
Thanks,
GerardM
Hoi,
With the software now packaged with functionality for language support, it
is well worth it to always mention how MediaWiki does REALLY support
languages.
It is a really strong argument for MediaWiki and, it is a best practice we
can be proud of.
Thanks,
GerardM
On 2 March 2013
Le 01/03/13 14:37, Yuri Astrakhan wrote:
The
proposalhttp://www.mediawiki.org/wiki/Requests_for_comment/RELEASE-NOTES_botis
for a bot to parse commit message for special commands to add some
text to specific sections of the release-notes file. When bot detects a
master merge, it will pull
On 01/03/13 23:59, Daniel Friesen wrote:
On Fri, 01 Mar 2013 14:45:14 -0800, Nischay Nahata wrote
I also prefer it in the header. The bug report is the best description :)
Is it not possible for Gerrit to search if its in the header? or make
it so
+1
Tools should be coded around people.
On Sat, Mar 2, 2013 at 9:08 AM, Antoine Musso hashar+...@free.fr wrote:
Le 01/03/13 14:37, Yuri Astrakhan wrote:
The
proposalhttp://www.mediawiki.org/wiki/Requests_for_comment/RELEASE-NOTES_botis
for a bot to parse commit message for special commands to add some
text to specific sections of
I don't like the idea of a bot doing this. Nor do I think writing release
notes at commit time works well either (too many stupid conflicts).
What's the issue with a bot appending a few lines to a release-notes
section if it sees it the commit message? But yes, release-notes conflicts
are a
On Sat, 02 Mar 2013 18:35:06 +0100, Chad innocentkil...@gmail.com wrote:
Most other groups using Gerrit that I know of tend to write their
release notes right before releases. Sometime shortly before
a release, they'll go through a full change of putting the release
notes together. Then if any
On 02/03/13 19:13, Bartosz Dziewoński wrote:
So you're volunteering to write release notes for my commits? By all
means, if so.
But I'm afraid this would end with simply no release notes being written.
Who would want to read and deeply understand 2000 commit messages per
release to note
- Original Message -
From: Ryan Lane rlan...@gmail.com
I wrote up some quick documentation on OpenID as a provider. Feel free to
modify it, especially for inaccurately used terminology. It's also likely a
good time to start bikeshed discussions on the urls, as I think it'll
end up
You would at least need some release-notes marker added by the commiter
so that you can skip non-RL-worthy ones.
That marker is exactly what I am proposing - if we
formalizehttp://www.mediawiki.org/wiki/Requests_for_comment/RELEASE-NOTES_botthe
commit messages, the release notes write
Yuri Astrakhan yuriastrak...@gmail.com wrote:
I don't like the idea of a bot doing this. Nor do I think writing release
notes at commit time works well either (too many stupid conflicts).
What's the issue with a bot appending a few lines to a release-notes
section if it sees it the commit
On Sat, 02 Mar 2013 21:17:29 +0100, Tim Landscheidt t...@tim-landscheidt.de
wrote:
As I wrote at
http://www.mediawiki.org/wiki/Talk:Git/Workflow#Release_notes_conflicts_20763,
this can be easily re-streamlined with a merge driver. As
release notes for MediaWiki are probably mostly additions,
Is anybody else seeing this when running 'git submodule update' in a
checkout of the extensions repo?
fatal: reference is not a tree: beead919cac17528f335d9409dfcada12e606ebd
Unable to checkout 'beead919cac17528f335d9409dfcada12e606ebd' in
submodule path 'MaintenanceShell'
Seems like the
On Sun, Mar 3, 2013 at 5:50 AM, Brion Vibber br...@pobox.com wrote:
Is anybody else seeing this when running 'git submodule update' in a
checkout of the extensions repo?
fatal: reference is not a tree: beead919cac17528f335d9409dfcada12e606ebd
Unable to checkout
On Sat, Mar 2, 2013 at 9:56 PM, Jeremy Baron jer...@tuxmachine.com wrote:
On Sun, Mar 3, 2013 at 5:50 AM, Brion Vibber br...@pobox.com wrote:
Is anybody else seeing this when running 'git submodule update' in a
checkout of the extensions repo?
fatal: reference is not a tree:
19 matches
Mail list logo
