28 Sep
2011
28 Sep
'11
9:50 a.m.
On Sep 28, 2011, at 9:37 AM, Marius Dumitru Florea wrote:
On Wed, Sep 28, 2011 at 8:28 AM, Vincent Massol
<vincent(a)massol.net> wrote:
Any issue. For example a bug fix will not go in the release notes for a milestone but will
go in the release notes for a bug fix release or a RC.
A bug issue will also usually not need to be documented elsewhere on xwiki.org, except
maybe in an adhoc fashion for very important bug fixes which could be documented in the
documentation to say that such feature wasn't working in version such and works after
such other version.
Thanks
-Vincent
Hi devs,
Sergiu has started a script to fully automate a release (more to come - Sergiu will
document what it does soon). The only part not automated are the Release Notes.
IMO we can "automate" it by a process which I propose to be:
* An issue can only be closed if it's
documented on xwiki.org and on the release notes page for the upcoming release.
What type of issue? I suppose your are referring to new features or
improvements. Thanks,
Marius
> * We collectively enforce this by reopening issues if someone doesn't do the
first point, asking him/her to do it
>
> This will have some nice effects:
> * xwiki.org will be more up to date than it is now
> * it's up to the developer to document what they do (I don't think it's
good to push this to someone else) which is good since they have the most knowledge (side
note: it doesn't mean we don't need a technical writer to improve on the
documentation done by developers but it would be about style and not about content)
> * the release notes will be ready for the release, as we progress and the burden of
writing the release notes will not fall on the shoulders of the Release Manager
(there's no reason it should)
> * the whole release process will almost be a joy to do
> * with a fully automated release process it means we'll be able to perform a lot
more bugfix releases which is good for our users
>
> Here's my +1
>
> Thanks
> -Vincent