Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Sat, Feb 24, 2018 at 01:54:10PM +, José Abílio Matos wrote: > On Friday, 23 February 2018 18.15.34 WET Scott Kostyshak wrote: > > To get you back, I made you waste time with thinking about my above > > proposal :) > > > > Scott > > It is always a good sign when at the end of a development cycle the > release manager is smiling. ;-) Actually, when I'm nervous or scared for some strange reason I tend to (attempt to) make jokes. Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Friday, 23 February 2018 18.15.34 WET Scott Kostyshak wrote: > To get you back, I made you waste time with thinking about my above > proposal :) > > Scott It is always a good sign when at the end of a development cycle the release manager is smiling. ;-) Good job. -- José Abílio
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Sat, Feb 24, 2018 at 12:23:52AM +, Pavel Sanda wrote: > Scott Kostyshak wrote: > > > Haha! Yeah, we should announce that users shouldn't be surprised if LyX > > > gets some lengths wrongs because its allowed to drink now! > > > > Yeah, it might occassionally black out as well. > > :)) Especially with new painting stuff on Mac (Apple Vodka flavors). P Well, I don't know if it will be any better after drinking Window cleaner. Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
Scott Kostyshak wrote: > > Haha! Yeah, we should announce that users shouldn't be surprised if LyX > > gets some lengths wrongs because its allowed to drink now! > > Yeah, it might occassionally black out as well. :)) Especially with new painting stuff on Mac (Apple Vodka flavors). P
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 10:48:59PM +, Pavel Sanda wrote: > Scott Kostyshak wrote: > > > Aren't we supposed to celebrate rounded years or something like that? > > > > Try to go into a bar in the U.S. when you are 20.51 years old and order > > a drink :) > > Haha! Yeah, we should announce that users shouldn't be surprised if LyX > gets some lengths wrongs because its allowed to drink now! Yeah, it might occassionally black out as well. > > If I open > > > > https://www.mail-archive.com/search?l=mid&q=20180131063641.otaji7vmdbqehima%40steph > > > > all of the links work fine for me on Firefox and Chromium. For you, the > > period after the "BugTrackerHome" URL causes a problem on Firefox? > > If you look meticulously mail-archive filters '.' out from url. But if you > copy paste the whole string I believe even your firefox will have problems. Ah I see now what you mean. You're talking about copy/pasting. I thought you were talking about clicking on the URL. OK it sounds like the current ANNOUNCE is OK then. Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
Scott Kostyshak wrote: > > Aren't we supposed to celebrate rounded years or something like that? > > Try to go into a bar in the U.S. when you are 20.51 years old and order > a drink :) Haha! Yeah, we should announce that users shouldn't be surprised if LyX gets some lengths wrongs because its allowed to drink now! > If I open > > https://www.mail-archive.com/search?l=mid&q=20180131063641.otaji7vmdbqehima%40steph > > all of the links work fine for me on Firefox and Chromium. For you, the > period after the "BugTrackerHome" URL causes a problem on Firefox? If you look meticulously mail-archive filters '.' out from url. But if you copy paste the whole string I believe even your firefox will have problems. Pavel
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 09:32:24AM +, José Abílio Matos wrote: > On Friday, 23 February 2018 03.34.52 WET Joel Kulesza wrote: > > Minor wording question here and on the website: is "down" potentially > > confusing for a non-native English speaker? Would "unavailable" be more > > clear? > > In the case of (European) Portuguese the equivalent of down is the word that > we use > for those cases so it is not confusing. :-) > > OTHO I agree that "unavailable" is more correct since the problems come > because the > server is unavailable even if it is not down (e.g. a problem with the local > network, ...). Since we say "slow or down" isn't no movement an extreme case of "slow", in which case we can just simplify the entire phrase to "slow"? Or does "slow" imply strictly positive movement? On a more serious note, I agree that "unavailable" is more clear, and have changed it on the website. > Now personally I understand the idea of down in a physical sense, when we > shutdown a > server the fans stop and it really seems as if a plane just landed. ;-) > > PS: Sorry for wasting everyone a few seconds reading this message. :-) To get you back, I made you waste time with thinking about my above proposal :) Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 10:10:38AM +, Pavel Sanda wrote: > Scott Kostyshak wrote: > > > -The 2.3 series has a rich set of new features compared to the current > > > stable > > > -series. An overview of the new features can be found here: > > > +With this release, LyX celebrates 22 years of existence. The 2.3 series > > > > How many years of existence are we celebrating? According to this > > Aren't we supposed to celebrate rounded years or something like that? Try to go into a bar in the U.S. when you are 20.51 years old and order a drink :) > But quite frankly, who cares :) Well, it would be nice to just figure it out so that it is one less thing to think through each time when editing the ANNOUNCE. I don't care in which way we determine it, but it would be nice to know if anyone else cares. Or we can just remove the part about the years. I don't have a preference between rounding, flooring, or excluding. > > Pavel, you added a space in-between a URL and a period at ca7aae8d, but you > > did > > not add a space for the others. Should we add a space for the others as > > well? > > I tested only with firefox. If I open https://www.mail-archive.com/search?l=mid&q=20180131063641.otaji7vmdbqehima%40steph all of the links work fine for me on Firefox and Chromium. For you, the period after the "BugTrackerHome" URL causes a problem on Firefox? > It does well if "." is just behind domain name, it > breaks if you made it part of filename, which makes sense. So basically, if the last part of the link is a slash, there is no problem if a period follows. Otherwise there is a problem. OK, so in this case the current ANNOUNCE is fine. Good to know. Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 10:21:19AM +, Uwe Stöhr wrote: > Am 23.02.2018 um 04:03 schrieb Scott Kostyshak: > > > Uwe, I included the same note that we did for 2.2.0, mentioning that if you > > installed a pre-release, you should uninstall those versions. Is this > > still the correct note? > > Yes, this is still correct. > My experience is that some users e.g. only tested beta1 but not an RC or RC1 > but not RC2. This caused often troubles. A reinstall is the clean solution > and only takes a minute -much less than writing an email when experiencing > troubles. Makes sense. Thanks for confirming. Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
Am 23.02.2018 um 04:03 schrieb Scott Kostyshak: Uwe, I included the same note that we did for 2.2.0, mentioning that if you installed a pre-release, you should uninstall those versions. Is this still the correct note? Yes, this is still correct. My experience is that some users e.g. only tested beta1 but not an RC or RC1 but not RC2. This caused often troubles. A reinstall is the clean solution and only takes a minute -much less than writing an email when experiencing troubles. regards Uwe
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
Scott Kostyshak wrote: > > -The 2.3 series has a rich set of new features compared to the current > > stable > > -series. An overview of the new features can be found here: > > +With this release, LyX celebrates 22 years of existence. The 2.3 series > > How many years of existence are we celebrating? According to this Aren't we supposed to celebrate rounded years or something like that? But quite frankly, who cares :) > Pavel, you added a space in-between a URL and a period at ca7aae8d, but you > did > not add a space for the others. Should we add a space for the others as well? I tested only with firefox. It does well if "." is just behind domain name, it breaks if you made it part of filename, which makes sense. Pavel
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Friday, 23 February 2018 03.34.52 WET Joel Kulesza wrote: > Minor wording question here and on the website: is "down" potentially > confusing for a non-native English speaker? Would "unavailable" be more > clear? In the case of (European) Portuguese the equivalent of down is the word that we use for those cases so it is not confusing. :-) OTHO I agree that "unavailable" is more correct since the problems come because the server is unavailable even if it is not down (e.g. a problem with the local network, ...). Now personally I understand the idea of down in a physical sense, when we shutdown a server the fans stop and it really seems as if a plane just landed. ;-) PS: Sorry for wasting everyone a few seconds reading this message. :-) Regards, -- José Abílio
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 03:34:52AM +, Joel Kulesza wrote: > On Thu, Feb 22, 2018 at 8:03 PM, Scott Kostyshak wrote: > > > > -You can download LyX 2.3.0rc2 from ftp://ftp.lyx.org/pub/lyx/devel/. > > > -In case the primary ftp server (based in France) is down or too slow you > > > -can try one of our mirrors listed at https://www.lyx.org/Download#toc11 > > . > > > +You can download LyX 2.3.0 from https://www.lyx.org/Download/. > > > > Minor wording question here and on the website: is "down" potentially > confusing for a non-native English speaker? Would "unavailable" be more > clear? Could be. Note that the announce for the final release does not directly link to the ftp so it does not mention that the ftp is in France. So the relevant text to look at is now here: https://www.lyx.org/Download/ Indeed there is "down" there also, so the discussion is still relevant. (and of course it's relevant for the next pre-release, 2.4.0alpha1). Scott signature.asc Description: PGP signature
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Thu, Feb 22, 2018 at 8:03 PM, Scott Kostyshak wrote: > > -You can download LyX 2.3.0rc2 from ftp://ftp.lyx.org/pub/lyx/devel/. > > -In case the primary ftp server (based in France) is down or too slow you > > -can try one of our mirrors listed at https://www.lyx.org/Download#toc11 > . > > +You can download LyX 2.3.0 from https://www.lyx.org/Download/. > Minor wording question here and on the website: is "down" potentially confusing for a non-native English speaker? Would "unavailable" be more clear?
Re: [LyX/2.3.x] Update ANNOUNCE for 2.3.0
On Fri, Feb 23, 2018 at 02:59:02AM +, Scott Kostyshak wrote:
> commit 88f4cb4999fee051bd2a3afe38e33376b44687be
> Author: Scott Kostyshak
> Date: Thu Feb 22 21:46:58 2018 -0500
>
> Update ANNOUNCE for 2.3.0
> ---
> ANNOUNCE | 28 +---
> 1 files changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/ANNOUNCE b/ANNOUNCE
> index 90578c3..d285467 100644
> --- a/ANNOUNCE
> +++ b/ANNOUNCE
> @@ -1,23 +1,21 @@
> -Public release of LyX version 2.3.0rc2
> +Public release of LyX version 2.3.0
>
>
> -We are proud to announce the second public release candidate of the new LyX
> 2.3
> -series. This pre-release is meant for testing and should not be used for
> -serious work. For curious users who would like to test in order to help catch
> -bugs before the 2.3.0 release, please back up all of your documents and be
> -prepared for the worst to happen. Most users (who desire a stable LyX
> version)
> -should not use this pre-release.
> +We are proud to announce the release of LyX 2.3.0.
>
> -The 2.3 series has a rich set of new features compared to the current stable
> -series. An overview of the new features can be found here:
> +With this release, LyX celebrates 22 years of existence. The 2.3 series
How many years of existence are we celebrating? According to this
message [1], we can interpret the birthdate of LyX as being in
September, 1995. According to here [2], it seems like 2 September is a
reasonable date to use.
This gives us:
d1=$(date -d "now" +%s)
d2=$(date -d "1995-09-2" +%s)
echo $(( (d1 - d2) / 31536000 )) years
echo "(${d1} - ${d2}) / 31536000" | bc -l
which gives 22.49 years. I suppose we cannot "celebrate 23 years" anyway
until > 23.00 years so even if it were 22.8 we might still go with "22
years".
> +has a rich set of new features compared to the current stable series.
>
> +LyX 2.3.0 is the culmination of two years of hard work. An overview
Is it OK to put "two years"? 2.2.0 was released on May 23. However, work
on features that ended up in 2.3.0 was begun before 2.2.0 was released.
For this release, I think two years feels about right. It would be nice
to have a rule of thumb for the future. I propose the time since the
previous major release was branched. So for 2.4.0, it will be the date
of that release minus the date of the following commit:
$(git merge-base 2.3.x master)
> +of the new features can be found here:
>https://wiki.lyx.org/LyX/NewInLyX23
>
> -You can download LyX 2.3.0rc2 from ftp://ftp.lyx.org/pub/lyx/devel/.
> -In case the primary ftp server (based in France) is down or too slow you
> -can try one of our mirrors listed at https://www.lyx.org/Download#toc11.
> +You can download LyX 2.3.0 from https://www.lyx.org/Download/.
>
> -We appreciate your help in testing this pre-release!
> +For Windows users, if you installed a pre-release of LyX 2.3.0, you
> +should uninstall that version before installing this newer release.
Uwe, I included the same note that we did for 2.2.0, mentioning that if you
installed a pre-release, you should uninstall those versions. Is this
still the correct note?
> +
> +We hope you will enjoy the result!
>
> If a file from an earlier version of LyX is opened *and saved* with
> any version of 2.3.x, then the original file will automatically be
> @@ -27,7 +25,7 @@ the original file, if no backup directory is set. The
> filename of the
> backup file will be:
> ORIGNAME-lyxformat-NUM.lyx~
> where NUM is the LyX format number of the original file. In the case of
> -2.2.x file, this will be 508, but in the case of older files it will be
> +a 2.2.x file, this will be 508, but in the case of older files it will be
> different.
>
> The file lib/RELEASE-NOTES lists some known issues and problems compared
> @@ -35,7 +33,7 @@ to the current stable releases (LyX 2.2.x). We strongly
> recommend that
> packagers of LyX on various platforms and distributions read this file.
>
> As with any major release, this one comes with a lot of new features but
> -also some bugs. If you think you have found a bug in LyX 2.3.0rc2, either
> +also some bugs. If you think you have found a bug in LyX 2.3.0, either
> email the LyX developers' mailing list (lyx-devel at lists.lyx.org),
> or open a bug report at https://www.lyx.org/trac/wiki/BugTrackerHome .
Pavel, you added a space in-between a URL and a period at ca7aae8d, but you did
not add a space for the others. Should we add a space for the others as well?
> Please specify if the behavior you are reporting is different from behavior
Scott
[1]
https://www.mail-archive.com/search?l=mid&q=76c02464-df10-c977-1c06-89700cccb918%40lyx.org
[2]
http://www.lyx.org/misc/archaeology/lyx-time.html
signature.asc
Description: PGP signature
