[Pkg-pascal-devel] release state of tuxcmd

[Tomas Bzatek]

On Sat, 2013-08-03 at 08:54 +0200, Paul Gevers wrote:
> Hi Tomas,
> 
> I am considering to take up maintenance of the tuxcmd package in Debian
> [0] which is currently unmaintained [1]. We recently started a package
> team to support packages written in pascal [2] and I think the Debian
> tuxcmd package should have it's home there.
> 
> Looking at the sourceforge website [3], the latest release I see is
> 0.6.70 (2009), while your git repository seems to feature up to 0.6.78.
> Could you please elaborate on your release strategy? I am fine with
> taking git tags if that is how you currently work.
> 
> You seem to not have been too busy with tuxcmd lately (one commit in the
> last 8 months). How do you see the future of tuxcmd? I assume you are in
> "maintenance mode". If I would get tuxcmd code related bugs in Debian,
> are you likely to help solving them, or would it mean that I had to deep
> dive into the code myself (not that coding is a problem per se, but of
> course you are way more familiar with the code).
> 
> Paul
> 
> [0] http://www.debian.org/
> [1] http://bugs.debian.org/704035
> [2] http://alioth.debian.org/projects/pkg-pascal
> [3] http://sourceforge.net/projects/tuxcmd/
> 

Hi Paul,

thanks for keeping the distro packages alive.

My release strategy is random at most, versions are incremented when
there are significant changes. That itself doesn't mean the sources are
ready for release, usually a period of testing and polishing precede new
releases.

At the current state the git master is broken, there are unfinished
things and missing functionality (core error reporting rewrite,
half-done). Staying with official releases is advised.

There have not been many changes in the past years, I have zero free
time for tuxcmd, even if I have tons of ideas and plans. I don't see a
future of this project, though I'm still actively using it. Frankly I
have hard time seeing gtk2 and gtk3 bright future either.

I'm fine with accepting patches, either bugfixes or feature
enhancements. It's always better to discuss in advance if there's
something bigger. But spending time on writing new code (or rewriting in
order to fix something) is out of question for me I'm afraid.

Cheers,
-- 
Tomas Bzatek