On Sun, Sep 21, 2014 at 3:41 PM, Markus Glaser wrote:
> Let me be clear about one thing: this is a matter of unclear
> responsibilites. I'm not blaming anyone personally for what they did. Let's
> clarify the process (maybe here on this list) and make _better_ mistakes
> tomorrow :)
>
Yup, agree
On 21 September 2014 20:08, Legoktm wrote:
> Hi,
>
> On 9/21/14, 1:42 PM, Mark A. Hershberger wrote:
> > Dear Wikitech-l
> >
> > REL1_24 was branched and announced ahead of schedule[0].
> >
> > Our schedule[1] clearly states that we will announce a branch one week
> > before we make one in order
Hi,
On 9/21/14, 1:42 PM, Mark A. Hershberger wrote:
> Dear Wikitech-l
>
> REL1_24 was branched and announced ahead of schedule[0].
>
> Our schedule[1] clearly states that we will announce a branch one week
> before we make one in order to allow developers to put any necessary work
> into the br
MediaWiki Bugzilla Report for September 15, 2014 - September 22, 2014
Status changes this week
Reports changed/set to UNCONFIRMED: 5
Reports changed/set to NEW: 18
Reports changed/set to ASSIGNED : 24
All,
Thanks to new architecture developments within the Memento Project, we are
pleased to announce the availability of Version 1.0.0 of the Memento Headers
time travel Extension for MediaWiki. The extension can be downloaded via [1].
Information on the extension is available at [2]. A demon
All,
Thanks to a few informal code reviews, version 2.1.0 of the Memento time travel
Extension for MediaWiki has been released. The extension can be downloaded via
[1]. Information on the extension is available at [2]. A demonstration wiki
equipped with the extension is available at [3].
Th
Hi Isarra,
> Why is this ahead of schedule? Two months before release
> seems pretty reasonable to me;
> You don't want to rush this stuff, especially when
> balancing with breaking changes in the next release.
It's ahead of the planned release schedule [1] by a few weeks. The real issues
is,
On 21/09/14 20:42, Mark A. Hershberger wrote:
Dear Wikitech-l
REL1_24 was branched and announced ahead of schedule[0].
Our schedule[1] clearly states that we will announce a branch one week
before we make one in order to allow developers to put any necessary work
into the branch and keep backpo
Dear Wikitech-l
REL1_24 was branched and announced ahead of schedule[0].
Our schedule[1] clearly states that we will announce a branch one week
before we make one in order to allow developers to put any necessary work
into the branch and keep backports to a minimum.
The current release is plann
Just a few thoughts:
* I agree that the tone of the email that started this discussion about
software quality standards was unnecessarily critical. Even in production
releases, users may find occasional bugs.
* The intent of HHVM implementation and James' quick response to the
problem report are
Hey,
I know requiring unit tests was discussed in the past, anyone remembers
> where and what the result was?
>
The most cohesive discussion on this I can remember was in the thread
"Architecture Guidelines: Writing Testable Code".
https://lists.wikimedia.org/pipermail/wikitech-l/2013-June/thread
On 2014-09-21 09:51, Pine W wrote:
> Thanks, but I'm looking for something that is more specific to MediaWiki
> and that commits development teams to specific, standardized, and
> transparently measured quality metrics as products advance or regress in
> their path to production release.
Yes I wou
Given longtime experience with problematic releases of MediaWiki features,
I think that published quality standards that products must meet in order
to become production releases could help to limit the number and
seriousness of additional troubled launches. These standards would also
reduce the a
Thanks, but I'm looking for something that is more specific to MediaWiki
and that commits development teams to specific, standardized, and
transparently measured quality metrics as products advance or regress in
their path to production release.
Pine
___
14 matches
Mail list logo
