db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: [jira] Commented: (DERBY-2847) More clarification issues for the release notes.
Date Sat, 07 Jul 2007 16:09:52 GMT
On 7/7/07, Daniel John Debrunner <djd@apache.org> wrote:
> Myrna van Lunteren wrote:
> > On 7/6/07, Daniel John Debrunner (JIRA) <jira@apache.org> wrote:
> >> What's the ant target to build the release notes [...]
> >
> > See:
> > http://wiki.apache.org/db-derby/ReleaseNoteProcess#head-1562c977bce7878313b51f6e55a9856bc2b09801
> >
> >
> > The step that's currently  most troublesome is to generate the reports
> > out of JIRA.
> > part of it can be accomplished by:
> > java org.apache.derbyBuild.JiraConnector
> > (But this gives everything, and I've modified the release notes
> > generator to strip out test issues, for example.)
> > Theoretically, this could be one step...
> I assume you are going to commit those changes back in. A release needs
> to be in a state where someone else can build it using the same source
> as is in the release. I hope there's no manual editing of the release notes.

I posted my changes as a patch with DERBY-2570, but they weren't
committed, not ready. I'll add my current changes into the 10.3 line.
However, it's definitely less than perfect, and it may need more work
for a next release.

And unfortunately, I think there is going to be some manual editing of
the release notes; I have to reconcile issues fixed in, and in it. I could be wrong, but it seems the current
ReleaseNotesGenerator does not take a range of versions. Still it's a
lot better than generating the entire release notes by hand.


> >
> What does building using 'eclipse' mean? I assume one can build plugins
> from an ant target without launching the IDE.

nope...The *core* plugin gets created by the current ant release, but
the ui and doc plugin have to be generated manually using the IDE. At
least, those are the steps, if there is another, automated way of
doing it, that would be a great improvement.

> It would be good for us to get this mindset for the release process, if
> it can't be done through ant then it can't be part of the release
> process. I see that the release managers seem to have to struggle to
> build the release artifacts, that doesn't encourage others to be release
> managers, enable release often or allow regular testing of the release
> process. I'm envious when I see other open source projects build a
> release quickly and move straight to a vote, even when a new committer
> performs the release manager role.


> I'd be willing to help out on some of these ant targets.

> Dan.


View raw message