On 10/14/2012 09:29 PM, Tyler Romeo wrote:
I also think
we should have better plans on what is actually going to be in each
release. In other words, a site administrator should be able to know what
new features are planned for the next release before the actual release has
been made. Maybe
I like the idea of LTS releases which are very useful in enterprise
environments with focus on stability and maintenance.
We typically build our MediaWiki Enterprise stacks on Ubuntu Server LTS...
/Alexander
Am 15.10.2012 03:26, schrieb Mark A. Hershberger:
I said I would lay out my thoughts
On 10/16/2012 10:43 AM, planetenxin wrote:
I like the idea of LTS releases which are very useful in enterprise
environments with focus on stability and maintenance.
We typically build our MediaWiki Enterprise stacks on Ubuntu Server LTS..
How many of these stacks do you deploy? Would you be
I am aware of the RELEASE-NOTES file. However, it is only updated once a
feature has been merged into the codebase, There should be some general
idea of at least what is planned for a release before the code is actually
written.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
On 10/16/2012 11:45 AM, Tyler Romeo wrote:
There should be some general
idea of at least what is planned for a release before the code is actually
written.
This would mean getting any non-WMF contributors (the volunteers) to
spec out what they planned to work on before hand and be committed to
As a sort of compromise, maybe we could write up a list of new features
MediaWiki administrators would find useful a month before the release is
planned. By that time, we've got a very good idea of what is going to
be in it.
This seems like a good idea. Even if we never follow through with
On Tue, Oct 16, 2012 at 12:18 PM, Mark A. Hershberger m...@everybody.org
wrote:
On 10/16/2012 11:45 AM, Tyler Romeo wrote:
There should be some general
idea of at least what is planned for a release before the code is actually
written.
This would mean getting any non-WMF contributors (the
I said I would lay out my thoughts regarding MW releases this weekend,
so here goes.
First: I want to provide a regular schedule so users know what to
expect, but something that a volunteer (me, for now) can achieve.
Second: I want to provide something that Linux distributors can
incorporate
I do like the idea of a semiannual release. On a related note, I also think
we should have better plans on what is actually going to be in each
release. In other words, a site administrator should be able to know what
new features are planned for the next release before the actual release has
been
Release notes?
-Chad
On Oct 14, 2012 9:30 PM, Tyler Romeo tylerro...@gmail.com wrote:
I do like the idea of a semiannual release. On a related note, I also think
we should have better plans on what is actually going to be in each
release. In other words, a site administrator should be able to
10 matches
Mail list logo