public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News Item: GnuCash 2.7+ Breaking Change
Date: Thu, 11 Jan 2018 11:40:12 +0200	[thread overview]
Message-ID: <1515663612.5212.1.camel@gentoo.org> (raw)
In-Reply-To: <20180111010002.GI15225@martineau.grandmasfridge.local>

On Wed, 2018-01-10 at 20:00 -0500, Aaron W. Swenson wrote:
> On 2018-01-10 22:53, Ciaran McCreesh wrote:
> > On Wed, 10 Jan 2018 17:48:32 -0500
> > "Aaron W. Swenson" <titanofold@gentoo.org> wrote:
> > > Modified a bit. This should show for anyone who has GnuCash
> > > installed.
> > 
> > For anyone who has any version of GnuCash installed, either now or
> > at
> > any point in the future. (See the recent thread on expiring news
> > items...) Are you sure you don't just want to target this at people
> > who
> > have the old version installed, instead?
> 
> As mentioned, the concern is that someone will try to use a new
> version
> and old version simultaneously.
> 
> How about “<app-office/gnucash-4"? It would allow it to "expire"
> after
> quite some time. At least past the point that we'd be concerned
> about,
> I'm sure.

That sounds good to me. The background here is, that once 2.7 is
released as stable, it'll be released as version 3.0, so 4 is after
that.
And then if they keep doing 3.2, 3.4 and so on for a long time instead,
you can try to remember to tweak the news item to expire before, e.g to
a version that drops forward migration support from 2.6.

This is all on the premise, that it's a leaf package and only kept
shown to those that have it.


Mart


  reply	other threads:[~2018-01-11  9:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 18:31 [gentoo-dev] News Item: GnuCash 2.7+ Breaking Change Aaron W. Swenson
2018-01-10 18:33 ` Kristian Fiskerstrand
2018-01-10 22:45   ` Aaron W. Swenson
2018-01-10 18:35 ` Kristian Fiskerstrand
2018-01-10 19:07   ` Ciaran McCreesh
2018-01-10 21:39     ` Aaron W. Swenson
2018-01-10 19:38 ` Peter Volkov
2018-01-10 20:46   ` Mart Raudsepp
2018-01-16 14:07     ` Róbert Čerňanský
2018-01-16 14:24       ` Kristian Fiskerstrand
2018-01-16 14:45       ` Aaron W. Swenson
2018-01-16 14:58         ` Kristian Fiskerstrand
2018-01-16 20:15           ` [gentoo-dev] " Duncan
2018-01-16 21:56           ` [gentoo-dev] " Róbert Čerňanský
2018-01-16 22:19             ` M. J. Everitt
2018-01-17  7:49               ` Róbert Čerňanský
2018-01-10 21:36   ` Aaron W. Swenson
2018-01-10 22:48 ` Aaron W. Swenson
2018-01-10 22:53   ` Ciaran McCreesh
2018-01-11  1:00     ` Aaron W. Swenson
2018-01-11  9:40       ` Mart Raudsepp [this message]
2018-01-11 16:27 ` [gentoo-dev] News Item: GnuCash 2.7+ Breaking Change (v3) Aaron W. Swenson
2018-01-11 18:02   ` Francesco Riosa
2018-01-11 21:18     ` Aaron W. Swenson
2018-01-11 22:09 ` [gentoo-dev] News Item: GnuCash 2.7+ Breaking Change (v4) Aaron W. Swenson
2018-01-11 22:30   ` Ulrich Mueller
2018-01-12 10:40     ` Aaron W. Swenson
2018-01-15  3:06 ` [gentoo-dev] News Item: GnuCash 2.7+ Breaking Change Aaron W. Swenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1515663612.5212.1.camel@gentoo.org \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox