[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: deeper freeze and kdebindings
From:       Rob Kaper <cap () capsi ! com>
Date:       2003-11-11 19:54:45
[Download RAW message or body]


On Tue, Nov 11, 2003 at 01:20:46PM +0100, Stephan Kulow wrote:
> > > Starting with next monday (17.11) the extra rule applies:
> > > * Every commit to released modules beside kde-i18n have
> > >   to contain a bug number with severity >= major. I'm trying
> > >   to watch the activities around bugs.kde.org as close as I can,
> > >   so make reasonable use of the severities.
> > Does this apply to the kdebindings module too? In the past I've regenerated 
> > the java bindings about a week or so before the final release. If I do it too 
> > early, it only needs one minor change in one kdelibs header to break the 
> > build, and the kdebindings list gets bug report mails. As far as I know there 
> > are no translation or artwork dependencies affecting the current JNI based 
> > java bindings.
> define minor change. I can't think of many reasons we'd need to change kdelibs
> interfaces for bug fixes. So I'd suggest you update the bindings on saturday and
> then do a check before the release. I hope it will result in no change. If it does
> not, you can of course still commit. That commit I'd define part of whatever commit
> gone into kdelibs to change the interface.

Idea: just tag the branch. Easier to watch the commits and has the added benefit
of opening up HEAD again for new commits.

Rob
-- 
Rob Kaper     | "In the name of sheer pity, won't someone operate on
cap@capsi.com | Chairman Arafat and put that poor cancer into a cleaner
www.capsi.com | environment? -- Rick Brookhiser

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]