--===============1968445950==
Content-Type: multipart/signed;
  boundary="nextPart4979907.VzTvpRAUrV";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4979907.VzTvpRAUrV
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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=20
question is now about logistical details and issues. see below.

On Saturday, November 6, 2010, Artur de Souza wrote:
> Any thoughts?

a) thanks for working on this

b) this is going to force us to define our desired workflow for plasma now=
=20
that we have git. more on that later, and i think an irc meeting for that i=
s=20
in order, in fact.

c) timing will be important and we need to coordinate development. personal=
ly=20
i can imagine at least two approaches:

* we make the migration ASAFP, before the first betas of 4.6 and before 4.7=
 is=20
branched off so that backporting / forwardporting changes will continue to=
=20
happen

* make the change shortly after the public release of 4.6, to maximize the=
=20
easy-backporting window

personally, i prefer the first since it will give us continuity between 4.6=
=20
and 4.7. usually once we go into beta of a release and the next one is abou=
t=20
to branch off, the older release stops getting backported fixes anyways. in=
=20
this case that would be the 4.5 branch in svn. so this would be the nicest=
=20
time to make the switch, imho.

but that will require support from the release team as the release of=20
kdeplasma-addons for 4.6 would have to come from git.kde.org instead of=20
svn.kde.org. if the release team members veto that for the 4.6 release, the=
n=20
we will need to consider the second (or some other?) option.

also, when we do the import, we'll need to notify everyone on plasma-devel@=
 so=20
that we don't get commits happening in svn on the day(s) of the actual impo=
rt.=20
that's easy enough to coordinate though, and perhaps sysadmin could help us=
 by=20
making that area of svn read-only on the day the git import is scheduled to=
=20
start.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks

--nextPart4979907.VzTvpRAUrV
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEABECAAYFAkzXBD4ACgkQ1rcusafx20OcTgCgjYORDB7JR+nMy714Y2vijiF5
HQQAoJAWKyaK72Q0MaupPShT9kGNa+ky
=3fC5
-----END PGP SIGNATURE-----

--nextPart4979907.VzTvpRAUrV--

--===============1968445950==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============1968445950==--