5 Dec
2011
5 Dec
'11
7:48 p.m.
Am Montag, 5. Dezember 2011 schrieb Timothy Pearson:
Doing a release properly requires a little over a month dedicated to
release tasks such as beta testing, compiling packages on all
distributions, compiling release notes, etc. Also, building binary
packages is not cheap, in terms of both time (of our distribution
maintainers) and money (to feed everyone's build computers with
electricity).
Releasing after the move to GIT would not cure a lot of the more
stubborn
bugs. Additionally, due to the renaming of *KDE* strings, the
distribution maintainers have some work to do in order to update their
packaging files. I don't want to place that kind of demand on our
volunteer staff during the Christmas season, and then turn right around
and demand the same thing a couple months later.
Thoughts?
What if not the whole TDE gets released but "only" bugfixed packages? It's
clear it won't work during transition and renaming phase, but when that is
settled (probably with 3.5.14) I think it would be a lot easier.
Nik
That would be much more managable. As you said it won't work for this
cycle, but it is a possibility for future releases.
Tim
Why not make a release, 3.5.14, in early January,
after the move to
Git and the rename thing is completed??
Even if it cures only a small bunch of bugs, it will be good, in many
respects.
+1
I like this idea