for this release,
because this would mean less hassle for packagers and people upgrading
their systems, and also guarantee a smoother transition when the new
version is ready for 4.4.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
stayed in the module with no
active maintainer for a given period of time need to be QA'd by the
module maintainer, if no one else steps up. If problems can not be
solved, they should probably be removed before the RC.
Regards,
Mauricio Piacentini
___
release
.
BTW, there are still some redraw bugs in KMines, introduced in Qt 4.5
as well. I am not sure what to do in that case as removing KMines is
not an option, and the bug does not appear to be ours... Dmitry, did
you have any success looking at these?
Regards,
Mauricio Piacentini
and with a low bandwidth connection, can someone please try
it to verify?
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
live, knowing that they will be
tagged and released aligned with the main KDE schedule?
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
it could be moved to kdeutils or something.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
in kdereview/playground and be moved before the hard freeze on May?
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
is the burden on the release team, but
Dirk seems to agree that 6 months is doable.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
interval for inclusion of new features and
applications in the main release seems too long, at least for me.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
us
follow the path that generates less stress for now, and move on to this
4.0 release.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
.
And of course, everything will be magically better after 4.0 is out :)
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
, in answer to my already less-than-clear question :)
Do you agree with me, or not?
:)
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
. To speed up discussion, a short list of names:
Konnect4
KonnectFour
KAlign4
KFourInLine
K4InLine
I think I prefer the Four format instead of the numeric 4 as it
seems to have less to do with version numbers or something like that.
Regards,
Mauricio Piacentini
in 4.0 because they missed the July cut, and stick by the
schedule.
To finish, I also think we really need to get this 4.0 thing out, as we
are stressing about smaller things almost daily :)
Regards,
Mauricio Piacentini
___
release-team mailing list
The click bug in lskat is fixed in revision 74772, no need to revert.
Apaku, thanks for finding it.
Which reminds me: we (kdegames) really need to do a through check of all
applications. A topic for our next meeting, this Saturday.
Regards,
Mauricio Piacentini
.
So each individual game could perhaps use this time to implement a
missing feature, but we would not add new games to the module after June
1st.
Regards,
Mauricio Piacentini
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman
17 matches
Mail list logo