Hi!
Quoting Aaron J. Seigo ase...@kde.org:
a) thanks for working on this
:D
b) this is going to force us to define our desired workflow for plasma now
that we have git. more on that later, and i think an irc meeting for that is
in order, in fact.
+1. I think that we can come up with an
* make the change shortly after the public release of 4.6, to maximize the
easy-backporting window
Well, theoretically, we could do the backporting in a bit dirty way if we are
careful - having the code in bot git repo and
svn (in local) - where svn would be on a branch we want to backport
On Monday, November 8, 2010, Ivan Cukic wrote:
* make the change shortly after the public release of 4.6, to maximize
the easy-backporting window
Well, theoretically, we could do the backporting in a bit dirty way if we
are careful - having the code in bot git repo and svn (in local) -
On Sunday 07 November 2010 16.36.35 Artur de Souza wrote:
[...]
PS: as soon as I finish the conversion that is running right now I'll
push the code to my scratch area so you can take a look at the repo,
check the history and then point if you find any errors/mismatches
(the last try was 100%
CC'ing the release team on this, since there's a point of interest here.
Release Team: Artur is working on migrating kdeplasma-addons to git. the
question is now about logistical details and issues. see below.
On Saturday, November 6, 2010, Artur de Souza wrote:
Any thoughts?
a) thanks for
Hi,
- Original Message -
but that will require support from the release team as the release of
kdeplasma-addons for 4.6 would have to come from git.kde.org instead
of
svn.kde.org. if the release team members veto that for the 4.6
release, then
we will need to consider the second (or
A Diumenge, 7 de novembre de 2010, Aaron J. Seigo va escriure:
CC'ing the release team on this, since there's a point of interest here.
Release Team: Artur is working on migrating kdeplasma-addons to git. the
question is now about logistical details and issues. see below.
On Saturday,
