-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
R14 RC1 is finally out the door! http://trinity-announce.pearsoncomputing.net/?0::30
This means the merge window for R14 RC2 is now OPEN. Please commit any outstanding patches at this time.
This merge window will close 11/26/2014 to allow for R14 RC2 build and release. Please concentrate all efforts on the unresolved bugs blocking Bug 2014.
Thanks!
Tim
Date: Wed, 19 Nov 2014 13:16:55 -0600 From: kb9vqf@pearsoncomputing.net To: trinity-devel@lists.pearsoncomputing.net Subject: [trinity-devel] TDE R14.0.0 Release Candidate 1 Available
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
R14 RC1 is finally out the door! http://trinity-announce.pearsoncomputing.net/?0::30
This means the merge window for R14 RC2 is now OPEN. Please commit any outstanding patches at this time.
This merge window will close 11/26/2014 to allow for R14 RC2 build and release. Please concentrate all efforts on the unresolved bugs blocking Bug 2014.
Thanks!
Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlRs7KYACgkQLaxZSoRZrGGu7wDdF1lrSVs0NGoOKtKLNy405IdG ZQ2XaQsB554CiQDeIK3uREMA7R2KbHcsMgmlaWQTCS57Fml/IyMQRQ== =X3nZ -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi,
Great! I think the the release announcement should be on website first page.
-Alexandre
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi,
Great! I think the the release announcement should be on website first page.
Yes, you are correct. I had to put together a screenshot so it took a bit longer than expected, but everything should be up on the site now.
Thanks!
Tim
2014-11-20 5:31 GMT+03:00 Timothy Pearson kb9vqf@pearsoncomputing.net:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi,
Great! I think the the release announcement should be on website first page.
Yes, you are correct. I had to put together a screenshot so it took a bit longer than expected, but everything should be up on the site now.
Thanks!
Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlRtUoIACgkQLaxZSoRZrGGoTwDdGcMMBbEYAuE32p/C4DXrF4JV H/57aKIQ2X31FwDgxGWhz3NMoUIYwIEYQRfFYCYiotqekM8SLo3ziQ== =ALzR -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Congratulations with the R14 finally done it's way to the final stages of the release...
Are there/will there be any packaged tarballs for the rc* or a special git tag? And whould you mind to package i18n tarball in multiple packages (like tde-i18n-<lang>) not as it was packaged before in one giant file at least for the release?
Congratulations with the R14 finally done it's way to the final stages of the release...
Hi,
Would it be good for you to inform linux news websites such as: http://www.tuxmachines.org http://lxer.com/ http://lwn.net
Seems like it is a good time to draw attention. Attention might mean critics, but it might also mean more dev, more users, more donations...
-Alexandre
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Congratulations with the R14 finally done it's way to the final stages of the release...
Hi,
Would it be good for you to inform linux news websites such as: http://www.tuxmachines.org http://lxer.com/ http://lwn.net
Seems like it is a good time to draw attention. Attention might mean critics, but it might also mean more dev, more users, more donations...
-Alexandre
I'd like to wait for RC2 before doing that; as you can see on the Wiki page we have a bunch of stupid user-visible bugs that are already fixed and waiting for builds, but would be difficult to undo from first perceptions.
Tim
On Thu, 20 Nov 2014 17:48:16 -0600 "Timothy Pearson" kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Congratulations with the R14 finally done it's way to the final stages of the release...
Hi,
Would it be good for you to inform linux news websites such as: http://www.tuxmachines.org http://lxer.com/ http://lwn.net
Seems like it is a good time to draw attention. Attention might mean critics, but it might also mean more dev, more users, more donations...
-Alexandre
I'd like to wait for RC2 before doing that; as you can see on the Wiki page we have a bunch of stupid user-visible bugs that are already fixed and waiting for builds, but would be difficult to undo from first perceptions.
We might also want to get a list of appropriate news sites together so that we can hit them all simultaneously when RC2 is tagged. In addition to Alexandre's list above, phoronix.com comes to mind. Others?
E. Liddell
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
2014-11-20 5:31 GMT+03:00 Timothy Pearson kb9vqf@pearsoncomputing.net:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi,
Great! I think the the release announcement should be on website first page.
Yes, you are correct. I had to put together a screenshot so it took a bit longer than expected, but everything should be up on the site now.
Thanks!
Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlRtUoIACgkQLaxZSoRZrGGoTwDdGcMMBbEYAuE32p/C4DXrF4JV H/57aKIQ2X31FwDgxGWhz3NMoUIYwIEYQRfFYCYiotqekM8SLo3ziQ== =ALzR -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Congratulations with the R14 finally done it's way to the final stages of the release...
Are there/will there be any packaged tarballs for the rc* or a special git tag?
I wasn't planning on it as the TDE upload bandwidth won't handle it and RC1 is rather buggy. I *might* tag RC2 (not sure yet) but definitely will tag R14 itself.
And whould you mind to package i18n tarball in multiple packages (like tde-i18n-<lang>) not as it was packaged before in one giant file at least for the release?
I'll see what I can do...
Tim
On Friday 21 of November 2014 00:46:03 Timothy Pearson wrote:
2014-11-20 5:31 GMT+03:00 Timothy Pearson kb9vqf@pearsoncomputing.net:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi,
Great! I think the the release announcement should be on website first page.
Yes, you are correct. I had to put together a screenshot so it took a bit longer than expected, but everything should be up on the site now.
Thanks!
Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlRtUoIACgkQLaxZSoRZrGGoTwDdGcMMBbEYAuE32p/C4DXrF4JV H/57aKIQ2X31FwDgxGWhz3NMoUIYwIEYQRfFYCYiotqekM8SLo3ziQ== =ALzR -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Congratulations with the R14 finally done it's way to the final stages of the release...
Are there/will there be any packaged tarballs for the rc* or a special git tag?
I wasn't planning on it as the TDE upload bandwidth won't handle it and RC1 is rather buggy. I *might* tag RC2 (not sure yet) but definitely will tag R14 itself.
And whould you mind to package i18n tarball in multiple packages (like tde-i18n-<lang>) not as it was packaged before in one giant file at least for the release?
I'll see what I can do...
Tim
Earlier here, in the discussion about using of branches, the consensus was that the RC versions version will not be tagged.