Re: Delay of release....
Sorry about the delay I've been extremely busy for the past couple of weeks. I will move the release today. -- Gregory Casamento - Original Message From: Richard Frith-Macdonald [EMAIL PROTECTED] To: Adam Fedor [EMAIL PROTECTED] Cc: GNUstep developer list gnustep-dev@gnu.org Sent: Saturday, January 27, 2007 3:03:59 PM Subject: Re: Delay of release On 27 Jan 2007, at 19:59, Adam Fedor wrote: On Jan 26, 2007, at 10:13 AM, Guenther Noack wrote: Speaking of GNUstep bugfix releases, what happened to the release of version 1.13.1, that fixes the buffer overflow issue I reported ( https://savannah.gnu.org/bugs/?18366)? I've seen that the stable branch is tagged 1.13.1 now, but there's still no release made public, neither on the web page nor on the ftp. I know that your time is limited and this is all done on a volunteer basis, but this is certainly not a good sign for a framwork which wants to be used in professional applications. The package is still in the incoming directory on the ftp server. I could move it and update everything, I just was unsure if Richard or Greg wanted to wait for something. Let me know. I put it up there for Greg to put in place (I don't have write access to do it myself) and emaild him about it a few weeks ago. Don't know whether he just hasn't had time or there is some other reason. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
Hi! On Tue, Jan 23, 2007 at 11:02:21AM +, Richard Frith-Macdonald wrote: I agree with that, but the fact is that we haven't done that in the past, so if we are going to start we need a policy decision that bugfixes are to be backported from trunk to the stable branch [...] This sounds like a very good idea to me, especially the idea of publishing daily snapshots. Speaking of GNUstep bugfix releases, what happened to the release of version 1.13.1, that fixes the buffer overflow issue I reported ( https://savannah.gnu.org/bugs/?18366)? I've seen that the stable branch is tagged 1.13.1 now, but there's still no release made public, neither on the web page nor on the ftp. I know that your time is limited and this is all done on a volunteer basis, but this is certainly not a good sign for a framwork which wants to be used in professional applications. Don't get me wrong, I don't blame anyone on this. I'm happy that the patch came so quick, but it's sad that the bugfix release did somehow not come out yet, as the task of doing it should be easy compared to doing a bugfix. -Guenther ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On Jan 26, 2007, at 10:13 AM, Guenther Noack wrote: Speaking of GNUstep bugfix releases, what happened to the release of version 1.13.1, that fixes the buffer overflow issue I reported ( https://savannah.gnu.org/bugs/?18366)? I've seen that the stable branch is tagged 1.13.1 now, but there's still no release made public, neither on the web page nor on the ftp. I know that your time is limited and this is all done on a volunteer basis, but this is certainly not a good sign for a framwork which wants to be used in professional applications. The package is still in the incoming directory on the ftp server. I could move it and update everything, I just was unsure if Richard or Greg wanted to wait for something. Let me know. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On 27 Jan 2007, at 19:59, Adam Fedor wrote: On Jan 26, 2007, at 10:13 AM, Guenther Noack wrote: Speaking of GNUstep bugfix releases, what happened to the release of version 1.13.1, that fixes the buffer overflow issue I reported ( https://savannah.gnu.org/bugs/?18366)? I've seen that the stable branch is tagged 1.13.1 now, but there's still no release made public, neither on the web page nor on the ftp. I know that your time is limited and this is all done on a volunteer basis, but this is certainly not a good sign for a framwork which wants to be used in professional applications. The package is still in the incoming directory on the ftp server. I could move it and update everything, I just was unsure if Richard or Greg wanted to wait for something. Let me know. I put it up there for Greg to put in place (I don't have write access to do it myself) and emaild him about it a few weeks ago. Don't know whether he just hasn't had time or there is some other reason. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On 2007-01-22 04:34:00 -0800 Fred Kiefer [EMAIL PROTECTED] wrote: Gregory John Casamento schrieb: My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, Oops, are you talking about a release of gui trunk or are you planing a bug fix release for gui? The late case should be alright, but there might be a problem, if you are going to push out the current trunk of gui as a release. I made some changes that will break backward compatibility and am about to make a lot more of such changes. Well, backwards compatibility I believe is already pretty much shot as I have added an ivar to NSTableView, and I believe that Richard has added one to NSControl, so it would be good if we could get these added now, (even if the code to use them is omitted from the release due to instability or whatever) :D ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On 23 Jan 2007, at 10:22, Matt Rice wrote: On 2007-01-22 04:34:00 -0800 Fred Kiefer [EMAIL PROTECTED] wrote: Gregory John Casamento schrieb: My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, Oops, are you talking about a release of gui trunk or are you planing a bug fix release for gui? The late case should be alright, but there might be a problem, if you are going to push out the current trunk of gui as a release. I made some changes that will break backward compatibility and am about to make a lot more of such changes. Well, backwards compatibility I believe is already pretty much shot as I have added an ivar to NSTableView, and I believe that Richard has added one to NSControl, Not that I recall. so it would be good if we could get these added now, (even if the code to use them is omitted from the release due to instability or whatever) :D Not to mention the move of NSAffineTransform out of gui and in to base to match Apple ... which means that whenever we make a new unstable release of gui we also need to make one of base. Wouldn't it be good to backport bugfixes and make a stable release of gui (and back) without all the incompatible changes asap though? ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On 2007-01-23 02:30:26 -0800 Richard Frith-Macdonald [EMAIL PROTECTED] wrote: On 23 Jan 2007, at 10:22, Matt Rice wrote: On 2007-01-22 04:34:00 -0800 Fred Kiefer [EMAIL PROTECTED] wrote: Gregory John Casamento schrieb: My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, Oops, are you talking about a release of gui trunk or are you planing a bug fix release for gui? The late case should be alright, but there might be a problem, if you are going to push out the current trunk of gui as a release. I made some changes that will break backward compatibility and am about to make a lot more of such changes. Well, backwards compatibility I believe is already pretty much shot as I have added an ivar to NSTableView, and I believe that Richard has added one to NSControl, Not that I recall. sorry it was NSResponder added the has_tooltips flag so it would be good if we could get these added now, (even if the code to use them is omitted from the release due to instability or whatever) :D Not to mention the move of NSAffineTransform out of gui and in to base to match Apple ... which means that whenever we make a new unstable release of gui we also need to make one of base. Wouldn't it be good to backport bugfixes and make a stable release of gui (and back) without all the incompatible changes asap though? *shrug* pretty much indifferent on this. It be nice if this were done proactively as bugfixes were introduced though ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On 23 Jan 2007, at 10:56, Matt Rice wrote: so it would be good if we could get these added now, (even if the code to use them is omitted from the release due to instability or whatever) :D Not to mention the move of NSAffineTransform out of gui and in to base to match Apple ... which means that whenever we make a new unstable release of gui we also need to make one of base. Wouldn't it be good to backport bugfixes and make a stable release of gui (and back) without all the incompatible changes asap though? *shrug* pretty much indifferent on this. It be nice if this were done proactively as bugfixes were introduced though I agree with that, but the fact is that we haven't done that in the past, so if we are going to start we need a policy decision that bugfixes are to be backported from trunk to the stable branch immediately, and we need the developers working on svn to buy in to the idea and actually do it. In an ideal world we would get new developers (who aren't confident to leap in and do bigger jobs) to do the backporting, but if we don't have any such volunteers we would need to be prepared to do it ourselves. The advantage of immediately backporting bugfixes (apart from making the process of doing a new bugfix release a whole lot easier because you don't have to try to backport a whole lot of changes in one go) is that it would make it worthwhile to set up an automated snapshot of the stable branch so that people could easily download something with latest bugfixes in it. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
Here's the procedure for actually making a release: http://wiki.gnustep.org/index.php/GNUstep_release_procedure Ok ... thanks. I suppose for gnustep-make I can do all the steps up to tagging the release, then you or Gregory will send out announces and manage the release publishing ? I'd plan to do the release in a couple of weeks, so I might get time to write a bit of documentation for it first. here's the policy for version numbering and when to make a release (applies more to libraries, though): http://wiki.gnustep.org/index.php/GNUstep_release_policy It doesn't seem to apply that easily to gnustep-make. ;-) But since 1.13.0 we have dropped the library suffixes and changed the ./obj directories ... if you have stuff compiled with 1.13.0 on your machine when you install the new gnustep-make you might need to recompile everything. :-) That seems to deserve at least bumping up the minor number to 1.14.0! ;-) Thanks PS: When we complete the Linux/general FHS support (which is not far, I'm getting there, a last big effort [involving also gnustep-base] and it will be done) I'd like to bump the gnustep-make version number straight up to 2.0.0. Which will be deserved because of the massive psychological/practical impact of the change. ;-) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
On Jan 23, 2007, at 4:03 PM, Nicola Pero wrote: Ok ... thanks. I suppose for gnustep-make I can do all the steps up to tagging the release, then you or Gregory will send out announces and manage the release publishing ? Sure, that's fine. But since 1.13.0 we have dropped the library suffixes and changed the ./obj directories ... if you have stuff compiled with 1.13.0 on your machine when you install the new gnustep-make you might need to recompile everything. :-) That seems to deserve at least bumping up the minor number to 1.14.0! ;-) Definitely. 1.14 is the current (unreleased) unstable version of base so it should at least be bumped to that. I always like to at least keep these two packages in sync with release numbers as well. The only issue is that the current policy states that 'stable' release have an even sub-minor version number, but perhaps we could just clean that up with the next stable/unstable release (or change the policy). PS: When we complete the Linux/general FHS support (which is not far, I'm getting there, a last big effort [involving also gnustep- base] and it will be done) I'd like to bump the gnustep-make version number straight up to 2.0.0. Which will be deserved because of the massive psychological/practical impact of the change. ;-) That sounds grand. Advertising that GNUstep now automatically integrates with standard systems might make people take notice... ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
RE: Delay of release....
I want to make a gnustep-make release. It would be 1.14.0. What is the current workflow to do that ? Thanks -Original Message- From: Gregory John Casamento [EMAIL PROTECTED] Sent: Mon, January 22, 2007 8:15 am To: GNUstep Developers gnustep-dev@gnu.org Subject: Delay of release All, My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, GJC -- Gregory Casamento ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
Fred, I understand and agree with Richard on this. We will give the gui trunk some time to stabilize before making a release. Also, there are some bugfixes which should be made for quality sake prior to the release. Thanks, GJC -- Gregory Casamento - Original Message From: Fred Kiefer [EMAIL PROTECTED] To: Gregory John Casamento [EMAIL PROTECTED] Cc: GNUstep Developers gnustep-dev@gnu.org Sent: Monday, January 22, 2007 7:34:00 AM Subject: Re: Delay of release Gregory John Casamento schrieb: My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, Oops, are you talking about a release of gui trunk or are you planing a bug fix release for gui? The late case should be alright, but there might be a problem, if you are going to push out the current trunk of gui as a release. I made some changes that will break backward compatibility and am about to make a lot more of such changes. As you know I did delay these changes for some time to give you time for a release, but as that time did expire and Richard explained, that I should not wait any longer (at least this was how I understood his mail), I started with these changes. So, if you are planing a gui release, please do some checking of my changes first (NSControl!!!) and perhaps wait for another week to give me the chance to finish off the changes to NSButtonCell as well. With that in place we will have a system that is hopefully a bit more stable than the current state. Sorry for the misunderstanding Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Delay of release....
Here's the procedure for actually making a release: http://wiki.gnustep.org/index.php/GNUstep_release_procedure here's the policy for version numbering and when to make a release (applies more to libraries, though): http://wiki.gnustep.org/index.php/GNUstep_release_policy On Jan 22, 2007, at 5:52 AM, Nicola Pero wrote: I want to make a gnustep-make release. It would be 1.14.0. What is the current workflow to do that ? Thanks -Original Message- From: Gregory John Casamento [EMAIL PROTECTED] Sent: Mon, January 22, 2007 8:15 am To: GNUstep Developers gnustep-dev@gnu.org Subject: Delay of release All, My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, GJC -- Gregory Casamento ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Delay of release....
All, My sincerest apologies on the recent delay of the release. I have been working on correcting a few bugs prior to the release and other events have delayed me as well. The release should be made in either Monday or Tuesday. Thanks for your patience, GJC -- Gregory Casamento ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
