Allen Winter | 1 Dec 04:12
Picon
Favicon

Re: kdeutils maintainer? khexedit program unmaintained

On Friday 30 November 2007 14:34:51 Friedrich W. H. Kossebau wrote:
> Hi,
> 
> from http://techbase.kde.org/Schedules/KDE4/4.0_Module_Status#Module_Status I 
> read there is no Release Maintainer for kdeutils. So who decides/cares there? 
> I guess this list, then.
> 
The Release Team, so I'll copy this over to our mailing list.

> With KHexEdit currently there is a tricky situation. Under kdeutils/khexedit 
> live two separate projects, the program KHexEdit and the binary editor plugin 
> (see the subdirs core, gui, parts), project name Okteta*.  I personally only 
> care for Okteta, but not for the program (see footnote why). 
> 
> Right now KHexEdit is roughly ported and runs, but is not fully functional 
> (painting draws outside of PaintEvent, view tabs running wild and crash the 
> program, html/rtf export not working). So not really in release state (yet).
> Two solutions:
> 1. Exclude from release and hope for me getting Okteta ready for the next one.
> 2. Search maintainer and fix KHexEdit.
> 
> I favour #1 (one program to rule things, no conflicts ;) But I understand 
> those who like #2 more, just tell me what you think.
> In case most like #2 more I would blog and mail a maintainer query to Danny 
> for inclusion in the digest.
> 
> So?
> 
> * Both projects share no code, as the plugin was written from scratch. Instead 
> of modifying KHexEdit to make use of the libs, I decided to write a program 
(Continue reading)

Dirk Mueller | 3 Dec 12:57
Picon
Favicon

Re: [kde-ev-marketing] Delaying 4.0?

On Wednesday 28 November 2007, Wade Olson wrote:

> Because we, the release planning group, have been asking since the
> summer for a good, safe, reliable date for a release event would be.
> And guess what: that answer was November.  So we padded 2 months and
> are now running into the same problem.

Really? When I was asked I said "plan for mid of february" ? ;) I was rather 
surprised to see an announcement for the release party one month before that 
time. 

Anyway, not gonna change anything anymore. Note that I`d rather release 4.0.x 
shortly afterwards than delaying forever. 

Greetings,
Dirk
Picon
Favicon

Does the string freeze remain in effect?

Hi,

ok, so KDE 4.0 has been delayed by around a month. Does this open another 
window to do some string changes (if so, for how long), or does the string 
freeze remain in effect?

On a more general note: I suppose for people who are highly involved in kde 
development this will not be a problem, and the information is accessible 
somewhere, but as an on-and-off contributor, I've found myself confused about 
what is or is not allowed at the moment, more than once. To me it would be 
really helpful, if there was a large visible note right at the top of 
http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule (or some other 
highly visible page), which always lists the freezes which are currently in 
effect, and how long they are expected to stay in effect.

Regards
Thomas
Allen Winter | 3 Dec 15:18
Picon
Favicon

Re: Does the string freeze remain in effect?

On Sunday 02 December 2007 11:02:58 Thomas Friedrichsmeier wrote:

> Hi,

>

> ok, so KDE 4.0 has been delayed by around a month. Does this open another

> window to do some string changes (if so, for how long), or does the string

> freeze remain in effect?

>

All freezes (API, feature, string) remain in effect until trunk is open for 4.1 development.

> On a more general note: I suppose for people who are highly involved in kde

> development this will not be a problem, and the information is accessible

> somewhere, but as an on-and-off contributor, I've found myself confused about

> what is or is not allowed at the moment, more than once. To me it would be

> really helpful, if there was a large visible note right at the top of

> http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule (or some other

> highly visible page), which always lists the freezes which are currently in

> effect, and how long they are expected to stay in effect.

>

I'll see what I can do.

-Allen

Tom Albers | 3 Dec 20:46
Picon

Tagging & release date RC2.

Hi, 

The techbase page has no date assigned to tagging and releasing RC2.
Was the plan to tag it this week and release next week?

Toma
Sebastian Kuegler | 3 Dec 22:22
Picon
Favicon
Gravatar

Re: Tagging & release date RC2.

On Monday 03 December 2007 20:46:19 Tom Albers wrote:
> The techbase page has no date assigned to tagging and releasing RC2.
> Was the plan to tag it this week and release next week?

That's what I understand we agreed upon. I didn't get around to fixing the 
techbase site, sorry for that.  Also, does someone feel like emailing k-c-d 
with the updated plans (Ok, a bit late, but also forgot about doing that).
--

-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 
Allen Winter | 3 Dec 23:11
Picon
Favicon

Re: kdeutils maintainer? khexedit program unmaintained

On Friday 30 November 2007 22:12:21 Allen Winter wrote:

> On Friday 30 November 2007 14:34:51 Friedrich W. H. Kossebau wrote:

> > Hi,

> >

> > from http://techbase.kde.org/Schedules/KDE4/4.0_Module_Status#Module_Status I

> > read there is no Release Maintainer for kdeutils. So who decides/cares there?

> > I guess this list, then.

> >

> The Release Team, so I'll copy this over to our mailing list.

>

> > With KHexEdit currently there is a tricky situation. Under kdeutils/khexedit

> > live two separate projects, the program KHexEdit and the binary editor plugin

> > (see the subdirs core, gui, parts), project name Okteta*. I personally only

> > care for Okteta, but not for the program (see footnote why).

> >

> > Right now KHexEdit is roughly ported and runs, but is not fully functional

> > (painting draws outside of PaintEvent, view tabs running wild and crash the

> > program, html/rtf export not working). So not really in release state (yet).

> > Two solutions:

> > 1. Exclude from release and hope for me getting Okteta ready for the next one.

> > 2. Search maintainer and fix KHexEdit.

> >

> > I favour #1 (one program to rule things, no conflicts ;) But I understand

> > those who like #2 more, just tell me what you think.

> > In case most like #2 more I would blog and mail a maintainer query to Danny

> > for inclusion in the digest.

> >

> > So?

> >

> > * Both projects share no code, as the plugin was written from scratch. Instead

> > of modifying KHexEdit to make use of the libs, I decided to write a program

> > also from scratch, using the libs. I am only halfway done, see

> > playground/utils/okteta. Bookmarks, Undo, and embedded search dialog are

> > still missing to match KHexEdit's features, but else looks good.

> >

> > Friedrich

> >

>

> If khexedit (the application) is truly terrible and unmaintained then we shouldn't

> release it. We should remove khexedit from kdeutils and plan on Okteta for 4.1.

> In the meantime, Okteta should be developed in playground.

> IOW: I agree with option 1.

>

> This is the same plan we are following for KAider replacing KBabel.

>

>

So should I add a kdeutils table to the Module Status page

saying that khexedit will be removed for 4.0 and that

okteta will be new in 4.1??

Freidrich: I assume you will be happy to do the khexedit move to unmaintained/4?

-Allen

Picon
Favicon

Re: kdeutils maintainer? khexedit program unmaintained

Hi Allen,

Am Montag, 3. Dezember 2007, um 23:11 Uhr, schrieb Allen Winter:
> On Friday 30 November 2007 22:12:21 Allen Winter wrote:
> > On Friday 30 November 2007 14:34:51 Friedrich W. H. Kossebau wrote:
> > > Hi,
> > >
> > > from
> > > http://techbase.kde.org/Schedules/KDE4/4.0_Module_Status#Module_Status
> > > I read there is no Release Maintainer for kdeutils. So who
> > > decides/cares there? I guess this list, then.
> >
> > The Release Team, so I'll copy this over to our mailing list.

Alright, am subscribed there, too.

> > > With KHexEdit currently there is a tricky situation. Under
> > > kdeutils/khexedit live two separate projects, the program KHexEdit and
> > > the binary editor plugin (see the subdirs core, gui, parts), project
> > > name Okteta*.  I personally only care for Okteta, but not for the
> > > program (see footnote why).
> > >
> > > Right now KHexEdit is roughly ported and runs, but is not fully
> > > functional (painting draws outside of PaintEvent, view tabs running
> > > wild and crash the program, html/rtf export not working). So not really
> > > in release state (yet). Two solutions:
> > > 1. Exclude from release and hope for me getting Okteta ready for the
> > > next one. 2. Search maintainer and fix KHexEdit.
> > >
> > > I favour #1 (one program to rule things, no conflicts ;) But I
> > > understand those who like #2 more, just tell me what you think.
> > > In case most like #2 more I would blog and mail a maintainer query to
> > > Danny for inclusion in the digest.
> > >
> > > So?
> > >
> > > * Both projects share no code, as the plugin was written from scratch.
> > > Instead of modifying KHexEdit to make use of the libs, I decided to
> > > write a program also from scratch, using the libs. I am only halfway
> > > done, see playground/utils/okteta. Bookmarks, Undo, and embedded search
> > > dialog are still missing to match KHexEdit's features, but else looks
> > > good.
> > >
> > > Friedrich
> >
> > If khexedit (the application) is truly terrible and unmaintained then we
> > shouldn't release it.  We should remove khexedit from kdeutils and plan
> > on Okteta for 4.1. In the meantime, Okteta should be developed in
> > playground.
> > IOW: I agree with option 1.
> >
> > This is the same plan we are following for KAider replacing KBabel.

Did someone besides me try KHexEdit? I might be wrong with my impression and 
biased (well, the latter I am for sure ;).

> So should I add a kdeutils table to the Module Status page
> saying that khexedit will be removed for 4.0 and that
> okteta will be new in 4.1??
>
> Freidrich: I assume you will be happy to do the khexedit move to
> unmaintained/4?

Not happy (heh, this is killing/removing a program which is around since 
1999), but I would do.

As the Okteta libs and KParts living in subdirs of KHexEdit (core/, gui/ and 
parts/) are maintained, by me, I would keep them there, just moving the files 
in the toplevel dir (and pics) which belong to the KHexEdit program.
The parts are implementing the modul interfaces from 
kdelibs/interfaces/khexedit/, which are used at least by KPilot and KDevelop 
(http://lxr.kde.org/ident?i=BytesEditInterface).

I guess renaming kdeutils/khexedit/ to kdeutils/okteta after that would match 
the content left in there, but it would make too many people unhappy, that 
close to a release, right? Too sad.
Moving to extragear, to follow the path of KAider, right now would be similar 
complicated...

I would svn mv kdeutils/khexedit/*  -N (or similar) to where exactly?

Friedrich
Allen Winter | 4 Dec 01:55
Picon
Favicon

Re: Tagging & release date RC2.

On Monday 03 December 2007 16:22:27 Sebastian Kuegler wrote:

> On Monday 03 December 2007 20:46:19 Tom Albers wrote:

> > The techbase page has no date assigned to tagging and releasing RC2.

> > Was the plan to tag it this week and release next week?

>

> That's what I understand we agreed upon. I didn't get around to fixing the

> techbase site, sorry for that.

Done, by toma.

> Also, does someone feel like emailing k-c-d with the updated plans.

Done, by me.

Dirk: the plan calls for tagging RC2 on Wed 5 Dec. Is that date ok for you?

Sebastian Kuegler | 4 Dec 09:56
Picon
Favicon
Gravatar

Re: Tagging & release date RC2.

On Tuesday 04 December 2007 01:55:54 Allen Winter wrote:
> On Monday 03 December 2007 16:22:27 Sebastian Kuegler wrote:
> > On Monday 03 December 2007 20:46:19 Tom Albers wrote:
> > > The techbase page has no date assigned to tagging and releasing RC2.
> > > Was the plan to tag it this week and release next week?
> >
> > That's what I understand we agreed upon. I didn't get around to fixing
> > the techbase site, sorry for that.
>
> Done, by toma.

Toma rocks.

> > Also, does someone feel like emailing k-c-d with the updated plans.
>
> Done, by me.

You rock.

> Dirk:  the plan calls for tagging RC2 on Wed 5 Dec.  Is that date ok for
> you?

Dirk rocks anyway.
--

-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 

Gmane