| 1 |
On Wed, 2018-01-10 at 20:00 -0500, Aaron W. Swenson wrote: |
| 2 |
> On 2018-01-10 22:53, Ciaran McCreesh wrote: |
| 3 |
> > On Wed, 10 Jan 2018 17:48:32 -0500 |
| 4 |
> > "Aaron W. Swenson" <titanofold@g.o> wrote: |
| 5 |
> > > Modified a bit. This should show for anyone who has GnuCash |
| 6 |
> > > installed. |
| 7 |
> > |
| 8 |
> > For anyone who has any version of GnuCash installed, either now or |
| 9 |
> > at |
| 10 |
> > any point in the future. (See the recent thread on expiring news |
| 11 |
> > items...) Are you sure you don't just want to target this at people |
| 12 |
> > who |
| 13 |
> > have the old version installed, instead? |
| 14 |
> |
| 15 |
> As mentioned, the concern is that someone will try to use a new |
| 16 |
> version |
| 17 |
> and old version simultaneously. |
| 18 |
> |
| 19 |
> How about “<app-office/gnucash-4"? It would allow it to "expire" |
| 20 |
> after |
| 21 |
> quite some time. At least past the point that we'd be concerned |
| 22 |
> about, |
| 23 |
> I'm sure. |
| 24 |
|
| 25 |
That sounds good to me. The background here is, that once 2.7 is |
| 26 |
released as stable, it'll be released as version 3.0, so 4 is after |
| 27 |
that. |
| 28 |
And then if they keep doing 3.2, 3.4 and so on for a long time instead, |
| 29 |
you can try to remember to tweak the news item to expire before, e.g to |
| 30 |
a version that drops forward migration support from 2.6. |
| 31 |
|
| 32 |
This is all on the premise, that it's a leaf package and only kept |
| 33 |
shown to those that have it. |
| 34 |
|
| 35 |
|
| 36 |
Mart |
Archives