11:40 a.m.
Dear all,
as we discussed recently I have created a new sourceforge tracker named
"Backwards-incompatible changes", and have added a first item relating
to the changed use of the $vcv accessors. Please check it out, correct
it and/or expand it. (Allin and Jack, could you just drop some keywords
what other incompatible changes will be new in 1.7.5, if any. thanks)
I have designated the "group" field of the tracker to refer to different
gretl versions, so that later it will be possible to search for all
incompatible changes in a specific version. Currently there is only a
group "new in 1.7.5", but as time progresses there will of course be
more groups. (And there is a bogus group "changed in gretl version" that
I erroneously created and now can't get rid of anymore.)
This tracker is already visible on the sourceforge tracker page. I'm not
sure if regular users are able to submit new items (which they normally
shouldn't do), but at least you need to be logged in before doing that,
and submitted items can always be deleted later.
Before I announce this on the users list I would like to wait a bit for
feedback, however.
cheers,
sven
2:19 p.m.
On Fri, 2 May 2008, Sven Schreiber wrote:
as we discussed recently I have created a new sourceforge
tracker named "Backwards-incompatible changes", and have added a
first item relating to the changed use of the $vcv accessors.
Please check it out, correct it and/or expand it...
Thanks very much, Sven. But now I see the new tracker in place I
have to say, I wonder if this is the right way to go.
It's certainly a good thing to have a searchable database of such
changes, but IMO this should be (a) static and (b) editable only
by developers (including yourself, of course). The regular SF
tracker apparatus (Assigned to/Status/Priority, and so on) doesn't
seem to apply, and might be confusing.
However, that's just my first reaction and I'm willing to be
persuaded otherwise.
Allin.
2:38 p.m.
Am 02.05.2008 16:19, Allin Cottrell schrieb:
On Fri, 2 May 2008, Sven Schreiber wrote:
> as we discussed recently I have created a new sourceforge
> tracker named "Backwards-incompatible changes", and have added a
> first item relating to the changed use of the $vcv accessors.
> Please check it out, correct it and/or expand it...
Thanks very much, Sven. But now I see the new tracker in place I
have to say, I wonder if this is the right way to go.
It's certainly a good thing to have a searchable database of such
changes, but IMO this should be (a) static and (b) editable only
by developers (including yourself, of course). The regular SF
tracker apparatus (Assigned to/Status/Priority, and so on) doesn't
seem to apply, and might be confusing.
quickly @b: I'm not sure right who may edit it. I have set some
permissions, where the six gretl developers I could identify in the
sourceforge list are made admins of that new tracker. I'm not sure what
that means for regular (logged-in) users, it would be nice if someone
who's not in the sourceforge gretl developers list could test.
-sven
4:14 p.m.
On Fri, 2 May 2008, Sven Schreiber wrote:
quickly @b: I'm not sure right who may edit it. I have set some
permissions, where the six gretl developers I could identify in
the sourceforge list are made admins of that new tracker. I'm
not sure what that means for regular (logged-in) users, it would
be nice if someone who's not in the sourceforge gretl developers
list could test.
I wonder if we might be better with a cvs-controlled log of
incompatible changes, much like the current ChangeLog.
I've done a mock-up of this; it's not linked to from the main
page, but you can find it at:
http://gretl.sourceforge.net/Backward.html
Any thoughts on the relative merits of these approaches?
Allin.
4:50 p.m.
Allin Cottrell schrieb:
On Fri, 2 May 2008, Sven Schreiber wrote:
> quickly @b: I'm not sure right who may edit it. I have set some
> permissions, where the six gretl developers I could identify in
> the sourceforge list are made admins of that new tracker. I'm
> not sure what that means for regular (logged-in) users, it would
> be nice if someone who's not in the sourceforge gretl developers
> list could test.
I wonder if we might be better with a cvs-controlled log of
incompatible changes, much like the current ChangeLog.
I've done a mock-up of this; it's not linked to from the main
page, but you can find it at:
http://gretl.sourceforge.net/Backward.html
Any thoughts on the relative merits of these approaches?
your page looks good to me. I have no particular vested interested in
the tracker solution, I just want a transparent documentation.
cheers,
sven
4:52 p.m.
On Tue, 6 May 2008, Allin Cottrell wrote:
On Fri, 2 May 2008, Sven Schreiber wrote:
> quickly @b: I'm not sure right who may edit it. I have set some
> permissions, where the six gretl developers I could identify in
> the sourceforge list are made admins of that new tracker. I'm
> not sure what that means for regular (logged-in) users, it would
> be nice if someone who's not in the sourceforge gretl developers
> list could test.
I wonder if we might be better with a cvs-controlled log of
incompatible changes, much like the current ChangeLog.
I've done a mock-up of this; it's not linked to from the main
page, but you can find it at:
http://gretl.sourceforge.net/Backward.html
Any thoughts on the relative merits of these approaches?
I like the Changelog-style better. Pros:
a) no spam involved
b) it's rather easy to look for stuff: you open the web page, and
everything is there. If in the future the list greows, all you have to do
is press Ctrl-F and you're pretty much done.
c) requires very little maintenance, but more or less the same holds for
the SF tracker
d) optionally, it can be turned into an Emacs-style "forward-incompatible
unfeatures" (if you have no idea of what I'm talking about, never mind,
it's an in-joke)
Cons: none I can see right now.
While we're at it: the Changelog is nice, but not exactly newbie-friendly.
For the next release, it'd be nice if someone volunteered to write a
"Release Notes" page, more or less in the style of Abiword's
(http://www.abiword.org/release-notes/2.6.0.phtml) or Gnumeric's
(http://www.gnome.org/projects/gnumeric/announcements/1.8/gnumeric-1.8.shtml).
There are several people on the devel list that I think would do an
excellent job (Sven, Andreas, Talha, to name but a few).
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche
r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti
9:32 a.m.
Riccardo (Jack) Lucchetti schrieb:
While we're at it: the Changelog is nice, but not exactly
newbie-friendly. For the next release, it'd be nice if someone
volunteered to write a "Release Notes" page, more or less in the style
of Abiword's (http://www.abiword.org/release-notes/2.6.0.phtml) or
Gnumeric's
(http://www.gnome.org/projects/gnumeric/announcements/1.8/gnumeric-1.8.shtml).
There are several people on the devel list that I think would do an
excellent job (Sven, Andreas, Talha, to name but a few).
If writing the release notes is not strictly tied to the release date
(but for example could happen a week after release), then I guess I
would be willing to do that. OTOH, I seem to remember that Allin said it
would be easier if he or you do it.
Just let me know.
-sven
9:41 p.m.
Am 06.05.2008 18:14, Allin Cottrell schrieb:
On Fri, 2 May 2008, Sven Schreiber wrote:
> quickly @b: I'm not sure right who may edit it. I have set some
> permissions, where the six gretl developers I could identify in
> the sourceforge list are made admins of that new tracker. I'm
> not sure what that means for regular (logged-in) users, it would
> be nice if someone who's not in the sourceforge gretl developers
> list could test.
I wonder if we might be better with a cvs-controlled log of
incompatible changes, much like the current ChangeLog.
I've done a mock-up of this; it's not linked to from the main
page, but you can find it at:
http://gretl.sourceforge.net/Backward.html
It seems everybody agrees to have that cvs-based thing on the webpage.
So I guess it should be linked to from the main page. And the new
tracker must be removed, but it looks as if only Allin has the
permissions to do it, I just tried but couldn't find any relevant button.
-sven
6148
days inactive
6155
days old
7 comments
3 participants
participants (3)
-
Allin Cottrell -
Riccardo (Jack) Lucchetti -
Sven Schreiber