On Sun, 26 Oct 2014, Remy Blank wrote:
I'm not really qualifying as a dev anymore, and I tend to have a radical
view on such issues, but I would make the just-released 0.12.6 the last
release on the 0.12 branch, and only patch it for security issues.
Rationale: the dev team is small, and the time that you guys can spend
on Trac (thanks a lot, BTW!) should be spent on new features and bug
fixes, not on maintenance.
Actually I'd vote for the same. Better to have progress for 1.x instead of
too much support for 0.12.x. For 0.12 only major bugs and security fixes.
I want a patch free Trac installation again. 1.0.2 cut mine down to 1
patch, but still not 0 :-)
P.S. For JOSM we have a monthly release schedule working fine. 2 months
for Trac also sounds good to me. With automated builds the workload should
be reduced. And from user side I prefer reported bugs (with patches) to be
fixed within two months and not two years.
Anyway I'm not part of Trac core and I think the most important rule is
"Who does the work decides!".
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
