Hi Folks,
I agree with release responsibility rotation, because it's a lot of
administrative work that is sometimes really boring. Thus its best for
the team
to rotate this responsibility ;)
Richard
Quoting Thomas Diesler <thomas.diesler(a)jboss.com>:
Hi Heiko/Team,
I would like to rotate the release responsibility among the team members
again. As we talked about, you would be the one who owns the 2.0.3.GA
release.
I've started a to document what needs to be done here:
http://jbws.dyndns.org/mediawiki/index.php?title=Release_Procedure
Please complete this documentation if necessary as you go along. Your
first responsibility would be to decide upon the set of jira issues that
will get fixed for 2.0.3.GA by jira freeze (14-Dec-2007). You would talk
to everybody who owns jira issues for that release and get their OK that
their issues will actually get fixed in time for code freeze
(18-Jan-2008). After jira freeze there should be no change in the number
of issues that go into the release.
cheers & good luck
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev