--===============0335480564== Content-Type: multipart/signed; boundary="nextPart25431540.Eplx95WF7U"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart25431540.Eplx95WF7U Content-Type: multipart/alternative; boundary="Boundary-00=_j5GtIjdnI2Oap6e" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_j5GtIjdnI2Oap6e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tuesday 26 August 2008, Tom Albers wrote: > Op dinsdag 26 augustus 2008 22:12 schreef u: > > i.e. /tags/kdesupport/latest-release would have cherry-picked subdirs of > > the latest phonon, strigi, qca, etc. releases from their appropriate tag > > or branch. As new releases occur the tag could be updated as well. > > I like and support the idea of a certain tag that contains the kdesupport > libs needed to build kde-stable branch. I think another tag would be need= ed > for kde trunk though. Well what I was thinking is we could make a kdesupport 4.1 branch for insta= nce=20 to do the same thing. (unless you mean kdesupport-stable which simply track= s=20 the latest stable release of KDE). And then a kdesupport/kde-trunk or something for /trunk development. If we think this is a good idea then we should probably get a list of requi= red=20 dependencies for each so that we can begin to track this. Regards, - Michael Pyne --Boundary-00=_j5GtIjdnI2Oap6e Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit

On Tuesday 26 August 2008, Tom Albers wrote:

> Op dinsdag 26 augustus 2008 22:12 schreef u:

> > i.e. /tags/kdesupport/latest-release would have cherry-picked subdirs of

> > the latest phonon, strigi, qca, etc. releases from their appropriate tag

> > or branch. As new releases occur the tag could be updated as well.

>

> I like and support the idea of a certain tag that contains the kdesupport

> libs needed to build kde-stable branch. I think another tag would be needed

> for kde trunk though.

Well what I was thinking is we could make a kdesupport 4.1 branch for instance to do the same thing. (unless you mean kdesupport-stable which simply tracks the latest stable release of KDE).

And then a kdesupport/kde-trunk or something for /trunk development.

If we think this is a good idea then we should probably get a list of required dependencies for each so that we can begin to track this.

Regards,

- Michael Pyne

--Boundary-00=_j5GtIjdnI2Oap6e-- --nextPart25431540.Eplx95WF7U Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAki0bmQACgkQqjQYp5Omm0qDtgCeJwwWxg9QEf9R4GMlSeb39vX7 7GEAoL7rQiNYjVY7hDNvUojSAY59jGYe =66I7 -----END PGP SIGNATURE----- --nextPart25431540.Eplx95WF7U-- --===============0335480564== 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 --===============0335480564==--