3 Nov
2010
3 Nov
'10
12:15 p.m.
On Wed, Nov 3, 2010 at 08:56, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
I'm summarizing some idea I've had about some tools to help the release process:
Idea 1: Create a semi-automated Release Plan page on xwiki.org
===================================================
* Read the POM from
http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution/jetty/hsql…
(using aether)
We should be able to choose the link since we have the same needs for
stable branch releases.
* Find all transitive dependencies (using aether)
* For each dep:
"For each SNAPSHOT dep and parent pom" (to be more precise ;))
** Read its POM
** Read the version from the pom, remove the SNAPSHOT part
** Read the JIRA URL from the pom
** Find the list of issues in jira with a fixfor equal to the read version
** If there are not closed issue display a warning message
I think not closed issues should be categorized a bit more to make
easier to see the issue that should be carefully checked:
* Would be nice to list not closed issues which are tagged "in
progress" to make sure to check with the owner that it's not going to
be committed before the release.
* A third list could contains not closed "blocker" (and maybe
"critical") issues which are supposed to block the release.
** Display the list of issues found
** Read the SVN info from the POM to find the svn tag URL (using svnkit for example)
** With the version build a full URL
** Get the svn revision number of the last commit for that URL
** Do a svn log on trunk/ to find all commits since the last release
** Display them
Would be nice to filter commits which are related to already closed
jira issues. Maybe also filter all "[cleanup] ...", "More svn:ignore"
and things like that which don't really deserve a release.
This should give a Release Plan Dashboard allowing the releaser to see at a glance what
should be released, saving him the work to:
- find all deps
- find which modules have been modified and needs to be released
Idea 2: Create a Release application on dev.xwiki.org
==========================================
* A very simple application with a home listing all past releases that have been done
already + a create new release button
* When you press that create button it creates a new release page, copying a template
page which has the release steps
* Use the todo macro/application to list all the steps to be performed in the release,
allowing the release to tick them visually as he progresses through the release (it's
important to be able to tick a task in view mode - if we don't have this feature in an
existing todo/task macro then develop it).
WDYT? Would that help the release process? Any other ideas.?
Idea 1 would help for sure. Not sure Idea 2 really deserve to develop
something for it, copy past does it well enough. What would really be
interesting is to see what you describe in Idea 1 as a configurable
suggest (you have a button for each releasable module to validate if
it deserve it on not) to generate a page with what we have in
http://dev.xwiki.org/xwiki/bin/view/Community/ReleasePlans for a
release and maybe add visual tick feature you describe in Idea 2.
Some notes:
* as soon as xwiki.org will be upgraded to 2.5 and more we will have
aether and maven which comes with extension manager so i would say
lets upgrade it before implementing this
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne