>>>> Stephen writes:
Stephen> A plan that nobody intends to follow is useless.
Of course. The reason for discussing it is to find a plan that we
intend to follow, at least for the next few steps. The reason for
following a plan is that it will be easier and more fun to collaborate
on tasks and finish them. Not to mention the fact that the task at
hand would be acknowledged as something that would be accepted as
Stephen> We need to decide which are required for a release, and then
Stephen> we can start planning the release.
Yes. I have listed a few that I, obviously naively, think is
necessary. Please contribute to that list by providing the items,
bugs, task etc that you think is needed.
Stephen> People who want to work on technically independent tasks
Stephen> rather than the release should be allowed to do so, but they
Stephen> should also be made aware that they're not helping with the
That is fine by me. The only problem there is if the independent tasks
gets half checked in making main unstable. That is another reason for
trying to focus on a few task and not trying to do everything in
Stephen> I don't know. You seem to think a quick release is
Stephen> important. But technically a "sync" is not a prerequisite to
Stephen> a release, and putting it into the list of release tasks will
Stephen> delay release by many months.
Right but at some time getting more in sync might feel the right thing
to focus on and then we do it. Then that will be the next item on the
agenda. This will of course not include a sync of everything.
This task will likely resurface at times etc.
Stephen> In fact the only absolute requirement for a release is a
Stephen> release manager.
I'm not up to date with the role the release manager plays. Making a
release ought to be a simple as agreeing we are done and setting the
tag. The rest is process (but of course hard work)
XEmacs-Beta mailing list