Bug#406935: 1.3.x released and stable, packagse available
On Thu, 2012-01-05 at 11:39 -0500, Antoine Beaupré wrote:
> I have noticed that 1.3 is not considered stable by upstream,
I haven't seen where they've said that.
> with frequent bugfix releases.
"frequent" does not imply "unstable", especially for a new major
version of an application, and in any case upstream has already said
that their release cycle will be slowing down.
> There are also packages for this release at:
An entirely unofficial set of packages.
And we have experimental versions as well, the
ledgersmb_1.3.9-1_all.deb at  for instance. (The stats say it's been
downloaded but if so, no one has commented on how it's working for
them...) I'm working on 1.3.9-2 now & will work on one for 1.3.10 when
it comes out. The intent is to get a version into at least Debian
Experimental fairly soon.
> I think 1.3 should be the default LedgerSMB installed in Debian, since
> this is what upstream suggests.
And it will be. Currently, I'm mostly working on taking care of the
issues that Lintian found.
> However, I do think we should allow both
> to be installed side by side since people (like me) have installed the
> 1.2 packages and may not be ready for the (maybe) complicated upgrade
In what way do you think they could be installed "side by side"?
IIRC, there is some functionality in 1.3.x to upgrade/update a 1.2.x
database but I don't see a way to have both versions of the application
itself that way and frankly I don't see the point. (If someone really
has a need to have both available, like for testing, just put the other
version(s) in a VPS.)
> What's the status of the 1.2 package in Debian? What's the blocker? It
> seems to me we should just upload 1.2.25 already...
why? Upstream notes that it is not recommended for new installations
and they also noted (back in October) that "community (free) support"
for such 1.2.x versions is expected to be "fade away" fairly quickly.