We've put together RC3 for 1.22.0. Please test the tarball and report any bugs you find on Bugzilla: http://bugzilla.wikimedia.org/
Assuming there are no show-stopping bugs reported with this RC, we'll be making a release this Friday, December 6, with only the version number included here changed.
Here are a list of changes made since the last RC. (Links for download follow this list.)
https://gerrit.wikimedia.org/r/95952 Add ar_id and el_id sequences for PostgreSQL -- saper
https://gerrit.wikimedia.org/r/96994 Fix login with temporary password with $wgSecureLogin = true -- Alexandre Emsenhuber
https://gerrit.wikimedia.org/r/96994 Restore Signupstart and Signupend messages for account creation -- Mark A. Hershberger
Full release notes: https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.22.0rc3/RELEASE-NOTES-... https://www.mediawiki.org/wiki/Release_notes/1.22
**********************************************************************
Download: http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0rc3.tar.gz
GPG signatures: http://download.wikimedia.org/mediawiki/1.22/mediawiki-core-1.22.0rc3.tar.gz... http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0rc3.tar.gz.sig
Public keys: https://www.mediawiki.org/keys/keys.html
On 3 December 2013 21:26, Mark A. Hershberger mah@everybody.org wrote:
We've put together RC3 for 1.22.0. Please test the tarball and report any bugs you find on Bugzilla: http://bugzilla.wikimedia.org/
Here's a question: is there a set-out list of steps to enable Visual Editor in this? Or is VE not quite ready for this?
Basically, what would the VE experience be for someone wanting 1.22 on their intranet?
- d.
VE is a BAD idea, its full of holes and bugs
On Tue, Dec 3, 2013 at 4:32 PM, David Gerard dgerard@gmail.com wrote:
On 3 December 2013 21:26, Mark A. Hershberger mah@everybody.org wrote:
We've put together RC3 for 1.22.0. Please test the tarball and report any bugs you find on Bugzilla: http://bugzilla.wikimedia.org/
Here's a question: is there a set-out list of steps to enable Visual Editor in this? Or is VE not quite ready for this?
Basically, what would the VE experience be for someone wanting 1.22 on their intranet?
- d.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Dec 3, 2013 at 4:39 PM, John phoenixoverride@gmail.com wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does not make the software itself a bad idea.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science
Bad idea [to package/install],…
Is what I believe beta was saying Tyler.
On Friday, December 6, 2013, Tyler Romeo wrote:
On Tue, Dec 3, 2013 at 4:39 PM, John <phoenixoverride@gmail.comjavascript:;> wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does not make the software itself a bad idea.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Correct, I see how my words can be taken several ways. Right now VE is a very unstable, bug filled, obnoxious elephant. Given enough time, testing, and maturity it as a lot of promise.
Right now its like trying to use a rocket like http://cdn.instructables.com/F9Y/2ONP/F4TLKVHS/F9Y2ONPF4TLKVHS.LARGE.jpg to land a man on the moon.
I would give VE probably another 18-24 months before its really ready to be switched on as a default editor for any non-testing wiki.
On Thu, Dec 5, 2013 at 9:17 PM, K. Peachey p858snake@gmail.com wrote:
Bad idea [to package/install],…
Is what I believe beta was saying Tyler.
On Friday, December 6, 2013, Tyler Romeo wrote:
On Tue, Dec 3, 2013 at 4:39 PM, John <phoenixoverride@gmail.com
wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does not make the software itself a bad idea.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/wikitech-l
-- Sent from Gmail Mobile on my iPod. _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Dec 6, 2013 3:28 AM, "John" phoenixoverride@gmail.com wrote:
Correct, I see how my words can be taken several ways. Right now VE is a very unstable, bug filled, obnoxious elephant. Given enough time, testing, and maturity it as a lot of promise.
Right now its like trying to use a rocket like http://cdn.instructables.com/F9Y/2ONP/F4TLKVHS/F9Y2ONPF4TLKVHS.LARGE.jpgto land a man on the moon.
I would give VE probably another 18-24 months before its really ready to
be
switched on as a default editor for any non-testing wiki.
In my estimation David is pretty capable of making an informed decision on the merits of deploying VE to his wikis.
On Thu, Dec 5, 2013 at 9:17 PM, K. Peachey p858snake@gmail.com wrote:
Bad idea [to package/install],…
Is what I believe beta was saying Tyler.
On Friday, December 6, 2013, Tyler Romeo wrote:
On Tue, Dec 3, 2013 at 4:39 PM, John <phoenixoverride@gmail.com
wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does
not
make the software itself a bad idea.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/wikitech-l
-- Sent from Gmail Mobile on my iPod. _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Fri, Dec 6, 2013 at 3:23 AM, Martijn Hoekstra martijnhoekstra@gmail.comwrote:
In my estimation David is pretty capable of making an informed decision on the merits of deploying VE to his wikis.
I wouldn't make such assumptions without context. Deploying beta software in a security sensitive environment is never a good idea. It all depends on what type of wikis are being run and what is being stored on them.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science
On 3 December 2013 21:32, David Gerard dgerard@gmail.com wrote:
On 3 December 2013 21:26, Mark A. Hershberger mah@everybody.org wrote:
We've put together RC3 for 1.22.0. Please test the tarball and report any bugs you find on Bugzilla: http://bugzilla.wikimedia.org/
Here's a question: is there a set-out list of steps to enable Visual Editor in this? Or is VE not quite ready for this?
Basically, what would the VE experience be for someone wanting 1.22 on their intranet?
Sadly, not quite ready, and VE already depends on 1.23wmf3 as it is…
J.
On 3 December 2013 21:40, James Forrester jforrester@wikimedia.org wrote:
On 3 December 2013 21:32, David Gerard dgerard@gmail.com wrote:
Here's a question: is there a set-out list of steps to enable Visual Editor in this? Or is VE not quite ready for this? Basically, what would the VE experience be for someone wanting 1.22 on their intranet?
Sadly, not quite ready, and VE already depends on 1.23wmf3 as it is…
That's annoying ... I've been desperate for VE on the intranet wikis I'm responsible for. I've asked casual Wikipedia editors and they love VE. (It's people like me, editing complicated articles, who keep breaking it.) But if you say it's not ready ...
- d.
On 3 December 2013 13:43, David Gerard dgerard@gmail.com wrote:
On 3 December 2013 21:40, James Forrester jforrester@wikimedia.org wrote:
On 3 December 2013 21:32, David Gerard dgerard@gmail.com wrote:
Here's a question: is there a set-out list of steps to enable Visual Editor in this? Or is VE not quite ready for this? Basically, what would the VE experience be for someone wanting 1.22 on their intranet?
Sadly, not quite ready, and VE already depends on 1.23wmf3 as it is…
That's annoying ... I've been desperate for VE on the intranet wikis I'm responsible for. I've asked casual Wikipedia editors and they love VE. (It's people like me, editing complicated articles, who keep breaking it.) But if you say it's not ready ...
"Not ready" means "not packaged as a 1.22 stand-alone install, and won't get back-ported security fixes".
If you're happy with VE as it currently operates (which is probably "good enough" for an intranet unless you have loads and loads of tables), and are happy to support VE as an in-development extension (rather than one with proper third-party support), please do go ahead. I'd be very willing to give you what support we can.
J.
On 3 December 2013 21:51, James Forrester jforrester@wikimedia.org wrote:
"Not ready" means "not packaged as a 1.22 stand-alone install, and won't get back-ported security fixes". If you're happy with VE as it currently operates (which is probably "good enough" for an intranet unless you have loads and loads of tables), and are happy to support VE as an in-development extension (rather than one with proper third-party support), please do go ahead. I'd be very willing to give you what support we can.
Like I need more gratuitous work ;-) I might give it a poke.
- d.
wikitech-l@lists.wikimedia.org