Legoktm legoktm.wikipe...@gmail.com writes:
On 9/22/14 1:10 PM, Mark A. Hershberger wrote:
In deference to the concerns raised by James Forrester, Markus and I
have decided not to back out the REL1_24 branch.
Will you be creating the REL1_24 branches for extensions and skins, or
would you
m...@nichework.com (Mark A. Hershberger) writes:
Legoktm legoktm.wikipe...@gmail.com writes:
On 9/22/14 1:10 PM, Mark A. Hershberger wrote:
In deference to the concerns raised by James Forrester, Markus and I
have decided not to back out the REL1_24 branch.
Will you be creating the
On 9/22/14 1:10 PM, Mark A. Hershberger wrote:
In deference to the concerns raised by James Forrester, Markus and I
have decided not to back out the REL1_24 branch.
Will you be creating the REL1_24 branches for extensions and skins, or
would you like me to do that?
-- Legoktm
How are you going to ensure that none of the changes that were already
merged on REL1_24 branch will be lost, and that none of the changes merged
on master that weren't meant for 1.24 will be included, and that all of
the changes merged on master will still be kept on master after the new
On 21/09/14 22:41, Markus Glaser wrote:
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
In deference to the concerns raised by James Forrester, Markus and I
have decided not to back out the REL1_24 branch.
Less than 80 hours have passed since the branch was made, so there
hasn't been time to make any major technical changes in the code base.
That leaves the social concerns that
On 22 September 2014 13:10, Mark A. Hershberger m...@nichework.com wrote:
In deference to the concerns raised by James Forrester, Markus and I
have decided not to back out the REL1_24 branch.
Less than 80 hours have passed since the branch was made, so there
hasn't been time to make any
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
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
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,
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 branch
On 21 September 2014 20:08, Legoktm legoktm.wikipe...@gmail.com 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
On Sun, Sep 21, 2014 at 3:41 PM, Markus Glaser gla...@hallowelt.biz 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
13 matches
Mail list logo
