Am 22.11.2010 05:49 schrieb percious:
That's about the most negative response I've seen in sometime. Yes, I
could have held up the 2.1 release, I saw this happen back in the days
of 0.8/1.0 TG, and it ultimately hurt the community.
There are many things which hurt the community.
As you also pointed out, we have many users who are not very experienced
yet, and we also want to be attractive to new users. For both of these
people, proper docs are a crucial issue.
Therefore in the last time on tg-trunk we talked a lot about how to
improve the docs before releasing 2.1 so that when it comes out, people
would have a good impression and experience. That's why I worked quite a
bit on a new layout and Sphinx theme and reserved time for the doc
sprint. But it was cancelled, there was no alternate date, and when I
suggested a new doc sprint on the mailing list last week, nobody
answered, so I think it's fair for me to say that "nobody cared". Maybe
my response was negative, but yes, I am disappointed about that.
Well, stuff happens, so we can always change our plans and priorities.
My point is that when plans are altered then this should be discussed or
at least communicated. Therefore we have our mailing lists [2]. I'm not
on IRC all day and honestly had no idea that the 2.1 release was going
to happen last weekend. I was also a bit annoyed because tickets from
the 2.1 final milestone were postponed or closed without comment and
without giving people a chance for feedback before the release.
My wish for the future is that the dates for important releases such as
2.1 are announced beforehand, and we can have a sprint with everybody
who cares where we try to fix the open tickets for the milestone or
decide together which need to be postponed, test everything in different
environments [1], and brush up the docs and release notes.
I hope you don't misunderstand me. You've done a lot, try to push TG 2
forward and we all appreciate that. But there are issues which cannot be
solved by you working even more and harder on TG 2. They can only be
solved by having better communication and release management [2] that
gets all committers and new people involved instead of getting them
accustomed that you're doing everything for them anyway.
-- Christoph
[1] I noticed that some tickets you closed as "worksforme" still did not
work for me, because I had different versions of Paste, Pylons or
repoze.who/what.xyz, webutils etc. Tried to adapt some required
versions, not sure if these changes made it into the release.
[2] http://www.oss-watch.ac.uk/resources/releasemanagement.xml
"When preparing a new release, the release manager needs to determine
its scope and planning. They should involve the committers and users and
seek some level of agreement from them about the scope and planning of
the release. This is because the users will play a very important role
in testing the prospective release and adopting the release once it has
been made final. For this reason, all communication about the scope and
planning of the release should be publicly accessible, for example via a
public mailing list."
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
