On Wed, Sep 28, 2011 at 1:42 PM, Vincent Massol <[email protected]> wrote:
> > On Sep 28, 2011, at 12:30 PM, Eduard Moraru wrote: > > > Hi, > > > > On Wed, Sep 28, 2011 at 8:28 AM, Vincent Massol <[email protected]> > wrote: > > > >> 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. > >> > > > > I`m not very keen of such an approach. This adds paperwork to N people > > (devs) that have already completed a job > > I definitely don't agree here. A dev job is not complete if > * tests are not written > * documentation has not been added > > > , multiplied by M issues (which can > > be more than 1 each day) done by each person... instead of just 1 person > > (release manager) in charge of a task that is repeated once every couple > of > > weeks (low frequency). > > I'm not sure I understand what you're saying. Are you also suggesting that > committers should not do code reviews and any of all the other tasks they're > suppose to do because it takes too much time and would be better done by a > single individual? I hope not… :) > > Side note: You should try to be a release manager to see what it takes > (although with Sergiu's script it should be much easier now). > > > Plus, the N devs have to use 2 tools to close one single bug. > > What tools? > 1. Jira 2. XWiki.org > > > Why don`t we use Jira's ability to comment on an issue when actually > closing > > it? We could then make a script to automatically round up all such > comments > > for the release process. At least it would be a single application and it > > would be no major breaking of the flow. > > If what you suggest is automated releases notes, I've been trying to do > that for about 12 years now and it has never worked to a satisfactory level > ;) > > What you suggest is also not very good IMO because it duplicates work > effort since the devs will need to document the stuff on xwiki.org anyway. > Please be more clear (preferably with an example) about what you expect for each developer to document on xwiki.org for each issue closed. > >> * We collectively enforce this by reopening issues if someone doesn't do > >> the first point, asking him/her to do it > >> > > > > Not sure how things work on Jira, but maybe we could do a very simple > Jira > > extension/plugin that does not allow closing an issue without commenting > on > > the chosen solution or whatever it is that we would want in the release > > notes. > > I don't see how that would help xwiki.org be more up to date. Remember > that release notes should point to documentation not duplicate it. > For instance, in http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise32M3I see no link to the list of fixed Jira issues, grouped by issue type. What I see there is a "resume" rather than a full, bullet list (maybe with expandable sections to say 2 words about the stuff done for the particular issue) of things done. While I agree that the resume is more user friendly (for users that have the attention span to read full paragraphs), I also think that we should include (prefferably), or at least link to, the Jira generated issue list. You can`t have people guess that they have to go to Jira and make 3-5 clicks to get the list of fixed issues. Thanks, Eduard > > Thanks > -Vincent > > > Thanks, > > Eduard > > > >> > >> 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 > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
