Re: [Amsn-devel] Release Sep 18th
Hi, as some of you already know, Youness will be busy for one month maybe a little more... For me, I will be away from Internet (or almost away) from tomorrow afternoon and up to an unknown date (due to troubles with my new location...) so I don't think it's the good time to release now... We should wait for my situation to settle (it has been said that in one month max all will be good) before releasing... Sorry but that's life aleas... Phil P.S. Be quiet when I won't be here to monitor all you do/write ;) Gustavo A. Díaz a écrit : Sounds nice!! Anything related to the skin that should be done? So i could close the 2.0 version of Sapphire as well... Cheers.! Vivia Nikolaidou escribió: OK... I suggest we release on Sep 18th :) Now everyone, you have 5 days to commit your latest fixes! Just, please, please, pretty please with sugar on top, don't add any new langen keys, because translators will be confused! Unless there are any objections, of course... Vivia -- /Gustavo A. Díaz/ *GDNet Projects* www.gdnet.com.ar http://www.gdnet.com.ar - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release Sep 18th
Hi, Maybe it was the plan already, but I didn't read it here, so I just post it... I think it would be a good thing to create the release from trunk rather than the current 0_97 branch. although many changes in trunk were merged into the branch, I think trunk is probably more stable at the moment. Regards, Harry Op 13-sep-2007, om 18:21 heeft Vivia Nikolaidou het volgende geschreven: OK... I suggest we release on Sep 18th :) Now everyone, you have 5 days to commit your latest fixes! Just, please, please, pretty please with sugar on top, don't add any new langen keys, because translators will be confused! Unless there are any objections, of course... Vivia -- --- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release Sep 18th
Sounds nice!! Anything related to the skin that should be done? So i could close the 2.0 version of Sapphire as well... Cheers.! Vivia Nikolaidou escribió: OK... I suggest we release on Sep 18th :) Now everyone, you have 5 days to commit your latest fixes! Just, please, please, pretty please with sugar on top, don't add any new langen keys, because translators will be confused! Unless there are any objections, of course... Vivia - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- /Gustavo A. Díaz/ *GDNet Projects* www.gdnet.com.ar http://www.gdnet.com.ar - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
On 6/15/06, Boris Faure (aka billiob) [EMAIL PROTECTED] wrote: 5) Send a mail to language translators so that they'll update the languages files. For 0.95, a mail was sent. Or do we release the 0.96 branch as it is right now, because languages are easily updated, so it's that much useful. Exactly, and after all it's not a final release. Just my 2 cents though - does anyone disagree? ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
2) are all binaries updated? Why not? Phil just checked, Windows binaries are OK. Tom H, can you double check Mac binaries? I need to run now. -- Also someone PLEASE test if 0.95 0.96b 0.96RC1 0.96 , ok? /me is off ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
The Mac binaries are all up to date! We have all the latest stable versions available in universal form. :D- TomOn 15 Jun 2006, at 16:25, Vivia Nikolaidou wrote:2) are all binaries updated? Why not? Phil just checked, Windows binaries are OK.Tom H, can you double check Mac binaries? I need to run now.--Also someone PLEASE test if 0.95 0.96b 0.96RC1 0.96 , ok?/me is off___Amsn-devel mailing listAmsn-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/amsn-devel Tom Hennigan[EMAIL PROTECTED]http://www.justclimbit.co.uk/ ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
we talked about the 'Event sounds' being removed from menus and we all decided (iirc) that it's ok and we should do it.. but it seems it was removed but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc) Do I just need glasses ? KKRT On Fri, 16 Jun 2006 10:28:16 -0400, Tom Hennigan [EMAIL PROTECTED] wrote: The Mac binaries are all up to date! We have all the latest stable versions available in universal form. :D - Tom On 15 Jun 2006, at 16:25, Vivia Nikolaidou wrote: 2) are all binaries updated? Why not? Phil just checked, Windows binaries are OK. Tom H, can you double check Mac binaries? I need to run now. -- Also someone PLEASE test if 0.95 0.96b 0.96RC1 0.96 , ok? /me is off ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel Tom Hennigan [EMAIL PROTECTED] http://www.justclimbit.co.uk/ -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
On 6/16/06, Youness Alaoui [EMAIL PROTECTED] wrote: we talked about the 'Event sounds' being removed from menus and we alldecided (iirc) that it's ok and we should do it.. but it seems it wasremoved but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc)Do I just need glasses ?KKRT--KaKaRoToPreferences Appearance (My events Alerts and Sounds) Play sounds when contact sign in or send message ? -- Maxime VERZIER (www.billets-orientes.com / www.verzier.info) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
No, Youness means to disable temporary the sound events... I think you aren't blind : the only place where I found it is in the traydock... Phil Le Friday 16 June 2006 18:42, Max a écrit : On 6/16/06, Youness Alaoui [EMAIL PROTECTED] wrote: we talked about the 'Event sounds' being removed from menus and we all decided (iirc) that it's ok and we should do it.. but it seems it was removed but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc) Do I just need glasses ? KKRT -- KaKaRoTo Preferences Appearance (My events Alerts and Sounds) Play sounds when contact sign in or send message ? ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Yep but then what is the different between Play sounds when contact sign in or send message and event sounds... The only other event that makes sound i can think of is when an email arrive so it is like 2 differents options for almost the same thing. On 6/16/06, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: No,Youness means to disable temporary the sound events...I think you aren't blind : the only place where I found it is in the traydock...PhilLe Friday 16 June 2006 18:42, Max a écrit: On 6/16/06, Youness Alaoui [EMAIL PROTECTED] wrote: we talked about the 'Event sounds' being removed from menus and we all decided (iirc) that it's ok and we should do it.. but it seems it was removed but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc) Do I just need glasses ? KKRT-- KaKaRoTo Preferences Appearance (My events Alerts and Sounds) Play sounds when contact sign in or send message ?___Amsn-devel mailing listAmsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel-- Maxime VERZIER ( www.billets-orientes.com / www.verzier.info) ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
There are alarms too... Phil Le Friday 16 June 2006 19:00, Max a écrit : Yep but then what is the different between Play sounds when contact sign in or send message and event sounds... The only other event that makes sound i can think of is when an email arrive so it is like 2 differents options for almost the same thing. On 6/16/06, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: No, Youness means to disable temporary the sound events... I think you aren't blind : the only place where I found it is in the traydock... Phil Le Friday 16 June 2006 18:42, Max a écrit: On 6/16/06, Youness Alaoui [EMAIL PROTECTED] wrote: we talked about the 'Event sounds' being removed from menus and we all decided (iirc) that it's ok and we should do it.. but it seems it was removed but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc) Do I just need glasses ? KKRT -- KaKaRoTo Preferences Appearance (My events Alerts and Sounds) Play sounds when contact sign in or send message ? ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
alarms doesn't count, sounds will be played if it comes from an alarm... (obviously!! like a cell phone, the alarm will sound even if you turned off your cell phone :P) KKRT On Fri, 16 Jun 2006 13:12:19 -0400, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: There are alarms too... Phil Le Friday 16 June 2006 19:00, Max a écrit : Yep but then what is the different between Play sounds when contact sign in or send message and event sounds... The only other event that makes sound i can think of is when an email arrive so it is like 2 differents options for almost the same thing. On 6/16/06, Philippe Valembois - Phil [EMAIL PROTECTED] wrote: No, Youness means to disable temporary the sound events... I think you aren't blind : the only place where I found it is in the traydock... Phil Le Friday 16 June 2006 18:42, Max a écrit: On 6/16/06, Youness Alaoui [EMAIL PROTECTED] wrote: we talked about the 'Event sounds' being removed from menus and we all decided (iirc) that it's ok and we should do it.. but it seems it was removed but never added anywhere else!!! so now, the only way to do it is from the context menu of the tray icon (which I don't have on my other pc) Do I just need glasses ? KKRT -- KaKaRoTo Preferences Appearance (My events Alerts and Sounds) Play sounds when contact sign in or send message ? ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. 2) are all binaries updated? Why not? 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
On Thu, 2006-06-15 at 23:04 +1000, Arieh Schneier wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. 2) are all binaries updated? Why not? Just asked, to be sure :) 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. No make a tag on the 0.96 branch.. seems pointless to me but someone might have reasons to do it? ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Shouldn't we make a tag of branches/0_96 now (called tags/0_96_1) ? I think so, because if we commit to 0_96 after the release, we cannot know what exactly was 0.96.1 in the repository anymore. And I think that is what Sander meant. And, iirc, it doesn't consume much repository space, as it is stored quite clever. After reviewing and committing changes between the branch and trunk, the diff between branch and trunk is almost empty now. Why did we create the branches/0_96 in the first place? Was the idea, stop implementing new features so we can release? (that would be good I think) Or am I missing something? Jonne. 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
what is wrong with you ? why have a 'poll' on wether we should create a tag or not First, we MUST create a tag, it's 100% normal, it's the best way to keep track of what we are doing.. imagine in 1 year or 2, we'd have made so many changes to SVN, so many new branches, so many backports of bugs to older branches, etc... then when we want to get the rc2 for example, we won't be able to do it ? everyone works with branches and tags, and that's how it is! you are saying that it's pointless, now, how about, in 3 years, someone says he has a huge bug in 0.96, but it's not appearing in 0.96 rc2, and it was something specific to his pc, noone else on earth could have that bug... but in 0.96 he also had a bugfix for something else, so he wants us to break the bugfix which creates his bug, and to port again the bugfix that he wants back into the rc2 version... best way is to get rc2, and patch it... now, let me think.. humm. was 0.96rc2 revision 6891 or 6981... damn, if only, back then, 3 years ago, they decided to create a tag... :( you know what, why don't YOU give me a GOOD reason for NOT creating a tag??? don't forget how SVN works, a whole copy of the repo, a tag or a branch or whatever takes NO space in the repo, so we don't care about the space... p.s.: every company that releases software creates a tag/label for every build they make, even if it's 100 builds... take a look at : http://svn.wikimedia.org/viewvc/mediawiki/ to see how branches and tags should be used... Next time, we'll make it the right way, we will branch for specific features (example, clgui branch, or amsncore branch) for every big feature we want to implement, instead of branching the next production (0.96) branch.. so the trunk/ is the development.. this means that, we would work on the trunk/ for everything, if we want to modify something huge, we creater a branch, we WON'T need to backport our changes from the trunk/ to that branch, what we'll do, is once that feature is done and complete, etc... we'll tell SVN to merge the two branches together, so that new developed feature gets integrated into the trunk/ automatically. Once we RELEASE, we create a branch for that release, and we'll do commits in that branch ONLY if we need to backport a fix for a custom build or for a new 'bugfix' version (for a critical bug for example).. example, the proxy thing, a huge problem, we had to release 0.96 because of that, if we used what I just described (the svn philosophy), we would have taken the 0.95 branch, applies the proxy fix on it, modifies the SF mirror for downloading tls, and released 0.95.1 with only these two fixes... without the need to force a release of 0.96 anyways.. gtg KKRT KKRT On Thu, 15 Jun 2006 09:26:44 -0400, Jonne Zutt [EMAIL PROTECTED] wrote: Shouldn't we make a tag of branches/0_96 now (called tags/0_96_1) ? I think so, because if we commit to 0_96 after the release, we cannot know what exactly was 0.96.1 in the repository anymore. And I think that is what Sander meant. And, iirc, it doesn't consume much repository space, as it is stored quite clever. After reviewing and committing changes between the branch and trunk, the diff between branch and trunk is almost empty now. Why did we create the branches/0_96 in the first place? Was the idea, stop implementing new features so we can release? (that would be good I think) Or am I missing something? Jonne. 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
On Thu, 15 Jun 2006 09:04:29 -0400, Arieh Schneier [EMAIL PROTECTED] wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. I don't... an RC, is a release candidate, from the very start, we had an RC in mind, we were 'going to release with known bugs'.. we can't do that on an official release.. so this IS an RC, not a release... I do accept the 0.96, 0.96.1, etc... numbering, the bugfixes thing, etc... but not for this release... this is an RC, and should not be considered anything else. So, we release this as 0.96.RC1 or 0.96RC1, whatever you want... the autoupdater should consider it as 0.96b.. which means 0.95 and 0.96 .. right ? do tests if you want. once we get the RC1 and maybe other RCs out of the way, we can release 0.96, then if you want and if needed, 0.96.1 and 0.96.2, etc... if you don't want to go through the 'RC' process, then you should have said so a few weeks ago, or months ago, so we would have fixed those huge critical issues we have now... if everyone wants it the way you said, then the release will have to postponed, in order for us to teak our brains into thinking damn, it's a production release, we must get all the bugs out, before... it's not an RC..., then release... 2) are all binaries updated? Why not? we should still check, we should recompile, just in case.. or use svn to see the revision number of the binaries against the rev number of each of the sources... 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Why Sander said that branches and tags are the same ? If they were the same why would be there a directory branches and a directory tags ? Phil Le Thursday 15 June 2006 16:43, Youness Alaoui a écrit : On Thu, 15 Jun 2006 09:04:29 -0400, Arieh Schneier [EMAIL PROTECTED] wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. I don't... an RC, is a release candidate, from the very start, we had an RC in mind, we were 'going to release with known bugs'.. we can't do that on an official release.. so this IS an RC, not a release... I do accept the 0.96, 0.96.1, etc... numbering, the bugfixes thing, etc... but not for this release... this is an RC, and should not be considered anything else. So, we release this as 0.96.RC1 or 0.96RC1, whatever you want... the autoupdater should consider it as 0.96b.. which means 0.95 and 0.96 .. right ? do tests if you want. once we get the RC1 and maybe other RCs out of the way, we can release 0.96, then if you want and if needed, 0.96.1 and 0.96.2, etc... if you don't want to go through the 'RC' process, then you should have said so a few weeks ago, or months ago, so we would have fixed those huge critical issues we have now... if everyone wants it the way you said, then the release will have to postponed, in order for us to teak our brains into thinking damn, it's a production release, we must get all the bugs out, before... it's not an RC..., then release... 2) are all binaries updated? Why not? we should still check, we should recompile, just in case.. or use svn to see the revision number of the binaries against the rev number of each of the sources... 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Technically, they are the same. It is possible, though not normal, to commit to a tag. quote isn't this tag-creation procedure the same procedure we used to create a branch? Yes, in fact, it is. In Subversion, there's no difference between a tag and a branch. Both are just ordinary directories that are created by copying. Just as with branches, the only reason a copied directory is a “tag” is because humans have decided to treat it that way: as long as nobody ever commits to the directory, it forever remains a snapshot. If people start committing to it, it becomes a branch. /quote On Thu, 2006-06-15 at 17:02 +0200, Philippe Valembois - Phil wrote: Why Sander said that branches and tags are the same ? If they were the same why would be there a directory branches and a directory tags ? Phil Le Thursday 15 June 2006 16:43, Youness Alaoui a écrit : On Thu, 15 Jun 2006 09:04:29 -0400, Arieh Schneier [EMAIL PROTECTED] wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. I don't... an RC, is a release candidate, from the very start, we had an RC in mind, we were 'going to release with known bugs'.. we can't do that on an official release.. so this IS an RC, not a release... I do accept the 0.96, 0.96.1, etc... numbering, the bugfixes thing, etc... but not for this release... this is an RC, and should not be considered anything else. So, we release this as 0.96.RC1 or 0.96RC1, whatever you want... the autoupdater should consider it as 0.96b.. which means 0.95 and 0.96 .. right ? do tests if you want. once we get the RC1 and maybe other RCs out of the way, we can release 0.96, then if you want and if needed, 0.96.1 and 0.96.2, etc... if you don't want to go through the 'RC' process, then you should have said so a few weeks ago, or months ago, so we would have fixed those huge critical issues we have now... if everyone wants it the way you said, then the release will have to postponed, in order for us to teak our brains into thinking damn, it's a production release, we must get all the bugs out, before... it's not an RC..., then release... 2) are all binaries updated? Why not? we should still check, we should recompile, just in case.. or use svn to see the revision number of the binaries against the rev number of each of the sources... 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Thanks :d Now I am less silly ;) Phil Le Thursday 15 June 2006 17:17, Jonne Zutt a écrit : Technically, they are the same. It is possible, though not normal, to commit to a tag. quote isn't this tag-creation procedure the same procedure we used to create a branch? Yes, in fact, it is. In Subversion, there's no difference between a tag and a branch. Both are just ordinary directories that are created by copying. Just as with branches, the only reason a copied directory is a “tag” is because humans have decided to treat it that way: as long as nobody ever commits to the directory, it forever remains a snapshot. If people start committing to it, it becomes a branch. /quote On Thu, 2006-06-15 at 17:02 +0200, Philippe Valembois - Phil wrote: Why Sander said that branches and tags are the same ? If they were the same why would be there a directory branches and a directory tags ? Phil Le Thursday 15 June 2006 16:43, Youness Alaoui a écrit : On Thu, 15 Jun 2006 09:04:29 -0400, Arieh Schneier [EMAIL PROTECTED] wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. I don't... an RC, is a release candidate, from the very start, we had an RC in mind, we were 'going to release with known bugs'.. we can't do that on an official release.. so this IS an RC, not a release... I do accept the 0.96, 0.96.1, etc... numbering, the bugfixes thing, etc... but not for this release... this is an RC, and should not be considered anything else. So, we release this as 0.96.RC1 or 0.96RC1, whatever you want... the autoupdater should consider it as 0.96b.. which means 0.95 and 0.96 .. right ? do tests if you want. once we get the RC1 and maybe other RCs out of the way, we can release 0.96, then if you want and if needed, 0.96.1 and 0.96.2, etc... if you don't want to go through the 'RC' process, then you should have said so a few weeks ago, or months ago, so we would have fixed those huge critical issues we have now... if everyone wants it the way you said, then the release will have to postponed, in order for us to teak our brains into thinking damn, it's a production release, we must get all the bugs out, before... it's not an RC..., then release... 2) are all binaries updated? Why not? we should still check, we should recompile, just in case.. or use svn to see the revision number of the binaries against the rev number of each of the sources... 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
can everyone PLEASE read the svn book... especially the chapter on the branching... I've just read part of it, but it's so easy to read, really well written, it's nice and easy to understand. It also allows us to learn more.. like the 'svn merge', or the 'svn blame' commands... anyways... p.s.: was I rude in a previous mail ? if so, sorry. KKRT On Thu, 15 Jun 2006 11:17:41 -0400, Jonne Zutt [EMAIL PROTECTED] wrote: Technically, they are the same. It is possible, though not normal, to commit to a tag. quote isn't this tag-creation procedure the same procedure we used to create a branch? Yes, in fact, it is. In Subversion, there's no difference between a tag and a branch. Both are just ordinary directories that are created by copying. Just as with branches, the only reason a copied directory is a “tag” is because humans have decided to treat it that way: as long as nobody ever commits to the directory, it forever remains a snapshot. If people start committing to it, it becomes a branch. /quote On Thu, 2006-06-15 at 17:02 +0200, Philippe Valembois - Phil wrote: Why Sander said that branches and tags are the same ? If they were the same why would be there a directory branches and a directory tags ? Phil Le Thursday 15 June 2006 16:43, Youness Alaoui a écrit : On Thu, 15 Jun 2006 09:04:29 -0400, Arieh Schneier [EMAIL PROTECTED] wrote: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, ... I agree, I think the second, because that is what we have always done before. I don't... an RC, is a release candidate, from the very start, we had an RC in mind, we were 'going to release with known bugs'.. we can't do that on an official release.. so this IS an RC, not a release... I do accept the 0.96, 0.96.1, etc... numbering, the bugfixes thing, etc... but not for this release... this is an RC, and should not be considered anything else. So, we release this as 0.96.RC1 or 0.96RC1, whatever you want... the autoupdater should consider it as 0.96b.. which means 0.95 and 0.96 .. right ? do tests if you want. once we get the RC1 and maybe other RCs out of the way, we can release 0.96, then if you want and if needed, 0.96.1 and 0.96.2, etc... if you don't want to go through the 'RC' process, then you should have said so a few weeks ago, or months ago, so we would have fixed those huge critical issues we have now... if everyone wants it the way you said, then the release will have to postponed, in order for us to teak our brains into thinking damn, it's a production release, we must get all the bugs out, before... it's not an RC..., then release... 2) are all binaries updated? Why not? we should still check, we should recompile, just in case.. or use svn to see the revision number of the binaries against the rev number of each of the sources... 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
/me ducks sorry, i was wrong, brains were overworked or something. We should do the tag yes. Also I agree with the rest of your email about everybody working in trunk and big changes go in branches, so not everybody has to commit his changes twice.. On Thu, 2006-06-15 at 10:37 -0400, Youness Alaoui wrote: what is wrong with you ? why have a 'poll' on wether we should create a tag or not First, we MUST create a tag, it's 100% normal, it's the best way to keep track of what we are doing.. imagine in 1 year or 2, we'd have made so many changes to SVN, so many new branches, so many backports of bugs to older branches, etc... then when we want to get the rc2 for example, we won't be able to do it ? everyone works with branches and tags, and that's how it is! you are saying that it's pointless, now, how about, in 3 years, someone says he has a huge bug in 0.96, but it's not appearing in 0.96 rc2, and it was something specific to his pc, noone else on earth could have that bug... but in 0.96 he also had a bugfix for something else, so he wants us to break the bugfix which creates his bug, and to port again the bugfix that he wants back into the rc2 version... best way is to get rc2, and patch it... now, let me think.. humm. was 0.96rc2 revision 6891 or 6981... damn, if only, back then, 3 years ago, they decided to create a tag... :( you know what, why don't YOU give me a GOOD reason for NOT creating a tag??? don't forget how SVN works, a whole copy of the repo, a tag or a branch or whatever takes NO space in the repo, so we don't care about the space... p.s.: every company that releases software creates a tag/label for every build they make, even if it's 100 builds... take a look at : http://svn.wikimedia.org/viewvc/mediawiki/ to see how branches and tags should be used... Next time, we'll make it the right way, we will branch for specific features (example, clgui branch, or amsncore branch) for every big feature we want to implement, instead of branching the next production (0.96) branch.. so the trunk/ is the development.. this means that, we would work on the trunk/ for everything, if we want to modify something huge, we creater a branch, we WON'T need to backport our changes from the trunk/ to that branch, what we'll do, is once that feature is done and complete, etc... we'll tell SVN to merge the two branches together, so that new developed feature gets integrated into the trunk/ automatically. Once we RELEASE, we create a branch for that release, and we'll do commits in that branch ONLY if we need to backport a fix for a custom build or for a new 'bugfix' version (for a critical bug for example).. example, the proxy thing, a huge problem, we had to release 0.96 because of that, if we used what I just described (the svn philosophy), we would have taken the 0.95 branch, applies the proxy fix on it, modifies the SF mirror for downloading tls, and released 0.95.1 with only these two fixes... without the need to force a release of 0.96 anyways.. gtg KKRT KKRT On Thu, 15 Jun 2006 09:26:44 -0400, Jonne Zutt [EMAIL PROTECTED] wrote: Shouldn't we make a tag of branches/0_96 now (called tags/0_96_1) ? I think so, because if we commit to 0_96 after the release, we cannot know what exactly was 0.96.1 in the repository anymore. And I think that is what Sander meant. And, iirc, it doesn't consume much repository space, as it is stored quite clever. After reviewing and committing changes between the branch and trunk, the diff between branch and trunk is almost empty now. Why did we create the branches/0_96 in the first place? Was the idea, stop implementing new features so we can release? (that would be good I think) Or am I missing something? Jonne. 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. Make a tag on the main branch? That is pointless because that isnt the 0.96, and we arent going to be integrating changes (accept for bugfixes if we plan to release a 0.96.1). So I think we don't need to tag it. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel signature.asc Description: This is a digitally signed message part ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
cool! :)
btw, you're not agreeing with me, you're agreeing with SVN philosophy and
with O'Reilly's book :D
about your idea you PMed me, releasing a 0.95.90 version as the RC...
yeah... might work... but would be too confusing for the users... I
suggest to keep it 0.96RC1 but maybe have a
set ::version 0.96RC1
set ::rc_version 0.95.90
in autoupdate {
set version $::version
if [info exists ::rc_version] set version $::rc_version
..
}
so, one internal rc version for the autoupdater only, completly
transparent to the user...
makes it easier for all of us.. as I said, the software should work it
out, not the user try not to get confused...
what do you think ?
KKRT
On Thu, 15 Jun 2006 13:49:43 -0400, Sander Hoentjen [EMAIL PROTECTED]
wrote:
/me ducks
sorry, i was wrong, brains were overworked or something. We should do
the tag yes. Also I agree with the rest of your email about everybody
working in trunk and big changes go in branches, so not everybody has to
commit his changes twice..
On Thu, 2006-06-15 at 10:37 -0400, Youness Alaoui wrote:
what is wrong with you ? why have a 'poll' on wether we should create a
tag or not
First, we MUST create a tag, it's 100% normal, it's the best way to keep
track of what we are doing.. imagine in 1 year or 2, we'd have made so
many changes to SVN, so many new branches, so many backports of bugs to
older branches, etc... then when we want to get the rc2 for example, we
won't be able to do it ? everyone works with branches and tags, and
that's
how it is!
you are saying that it's pointless, now, how about, in 3 years, someone
says he has a huge bug in 0.96, but it's not appearing in 0.96 rc2, and
it
was something specific to his pc, noone else on earth could have that
bug... but in 0.96 he also had a bugfix for something else, so he wants
us
to break the bugfix which creates his bug, and to port again the bugfix
that he wants back into the rc2 version... best way is to get rc2, and
patch it... now, let me think.. humm. was 0.96rc2 revision 6891 or
6981... damn, if only, back then, 3 years ago, they decided to create a
tag... :(
you know what, why don't YOU give me a GOOD reason for NOT creating a
tag???
don't forget how SVN works, a whole copy of the repo, a tag or a branch
or
whatever takes NO space in the repo, so we don't care about the space...
p.s.: every company that releases software creates a tag/label for every
build they make, even if it's 100 builds... take a look at :
http://svn.wikimedia.org/viewvc/mediawiki/ to see how branches and tags
should be used...
Next time, we'll make it the right way, we will branch for specific
features (example, clgui branch, or amsncore branch) for every big
feature
we want to implement, instead of branching the next production (0.96)
branch.. so the trunk/ is the development.. this means that, we would
work
on the trunk/ for everything, if we want to modify something huge, we
creater a branch, we WON'T need to backport our changes from the trunk/
to
that branch, what we'll do, is once that feature is done and complete,
etc... we'll tell SVN to merge the two branches together, so that new
developed feature gets integrated into the trunk/ automatically. Once we
RELEASE, we create a branch for that release, and we'll do commits in
that
branch ONLY if we need to backport a fix for a custom build or for a new
'bugfix' version (for a critical bug for example)..
example, the proxy thing, a huge problem, we had to release 0.96 because
of that, if we used what I just described (the svn philosophy), we would
have taken the 0.95 branch, applies the proxy fix on it, modifies the SF
mirror for downloading tls, and released 0.95.1 with only these two
fixes... without the need to force a release of 0.96
anyways.. gtg
KKRT
KKRT
On Thu, 15 Jun 2006 09:26:44 -0400, Jonne Zutt [EMAIL PROTECTED]
wrote:
Shouldn't we make a tag of branches/0_96 now (called tags/0_96_1) ?
I think so, because if we commit to 0_96 after the release, we cannot
know what exactly was 0.96.1 in the repository anymore.
And I think that is what Sander meant.
And, iirc, it doesn't consume much repository space, as it is stored
quite clever.
After reviewing and committing changes between the branch and trunk,
the diff between branch and trunk is almost empty now.
Why did we create the branches/0_96 in the first place? Was the idea,
stop implementing new features so we can release? (that would be good
I
think) Or am I missing something?
Jonne.
3) do we create a tag for this release in svn? (A tag and a branch
are
the same in svn, technically) So does it have any benefits to
create
a
tag, when we already have a 0.96 branch, which we can check out by
revision number, if bugfixes later are done in this branch.
Make a tag on the main branch? That is pointless because that isnt
the
0.96,
and we arent going to be
Re: [Amsn-devel] release
On 6/15/06, Youness Alaoui [EMAIL PROTECTED] wrote:
cool! :)
btw, you're not agreeing with me, you're agreeing with SVN philosophy and
with O'Reilly's book :D
about your idea you PMed me, releasing a 0.95.90 version as the RC...
yeah... might work... but would be too confusing for the users... I
suggest to keep it 0.96RC1 but maybe have a
set ::version 0.96RC1
set ::rc_version 0.95.90
in autoupdate {
set version $::version
if [info exists ::rc_version] set version $::rc_version
..
}
so, one internal rc version for the autoupdater only, completly
transparent to the user...
makes it easier for all of us.. as I said, the software should work it
out, not the user try not to get confused...
what do you think ?
that's what I thought too, let the autoupdater understand that 0.96RC1
0.96 somehow. But this needs someone to code it :)
___
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
5) Send a mail to language translators so that they'll update the languages files. For 0.95, a mail was sent. Or do we release the 0.96 branch as it is right now, because languages are easily updated, so it's that much useful. -- Boris FAURE (aka billiob) mail, msn : [EMAIL PROTECTED] No trees were killed in the sending of this message. However, a large number of electrons were terribly agitated. ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
Yes, you're right.. but the translations could come in with the 0.96 release, it's not that needed for the RC1.. but we'll have to assume we won't add any new keys in between, which should be the case since we'll only fix bugs between RCs, not add new stuff... KKRT On Thu, 15 Jun 2006 13:50:50 -0400, Boris Faure (aka billiob) [EMAIL PROTECTED] wrote: 5) Send a mail to language translators so that they'll update the languages files. For 0.95, a mail was sent. Or do we release the 0.96 branch as it is right now, because languages are easily updated, so it's that much useful. -- KaKaRoTo ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release
I spoke to Alvaro on PM, but he had to run, so I'm writing here instead of him: 1) now we have to update the version in the amsn file.. what should it become? More generally, what will this release be? 0.96rc1 followed by rc2, then rc..., then 0.96 or 0.96 followed by 0.96.1, etc i would say the second, because if we don't have critical bugs, we don't want to make another release that is essentially the same, and it is weird in my opinion to have 0.96rc2 followed by a 0.97 release. to be short with rc then you have to make as much rc's until there are no more bugs, and then make another release that is only a namechange from rc to normal. With the .bugfix releases none of these problems exist, and computers will have an easier time to understand what version is newer. [16:22:27] Álvaro (#) better [16:22:30] Álvaro (#) 0.95.99 [16:22:32] Álvaro (#) then 0.95.999 [16:22:40] Álvaro (#) that way it doesn't look like 0.96 yet [16:22:43] Álvaro (#) i mean [16:22:45] Álvaro (#) if it's 0.96.1 [16:22:52] Álvaro (#) people won't see it as a rc 3) do we create a tag for this release in svn? (A tag and a branch are the same in svn, technically) So does it have any benefits to create a tag, when we already have a 0.96 branch, which we can check out by revision number, if bugfixes later are done in this branch. [16:25:31] Álvaro (#) but it's better just tag 0.96 [16:25:39] Álvaro (#) than branch 0.96+revision number xxx981984934x [16:25:47] Álvaro (#) isn't it? :D [16:25:52] Álvaro (#) a tag is a finished branch [16:26:05] Álvaro (#) i think it should be tagged anyways [16:26:13] Álvaro (#) that way you can always check the list of tags [16:26:17] Álvaro (#) and see what versions were released ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release count-down
Hey, only 20 minutes left guys! no more commits to do ??? everything in everyone's point of view is perfect and ready for the release ? KKRT On Mon, 05 Dec 2005 19:40:59 -0500, Jérôme Gagnon-Voyer [EMAIL PROTECTED] wrote: 9h00 PM Eastern Time (-5GMT) In 1h20, we will set the tag for aMSN 0.95 on the current cvs snapshot If you have a last minute small fix, that's NOW :P --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release count-down
On Monday 05 December 2005 17:38, Youness Alaoui wrote: Hey, only 20 minutes left guys! no more commits to do ??? everything in everyone's point of view is perfect and ready for the release ? I guess it's time. Where do we find the package that we should base ours on? -- Karol Krizka pgpVQGqWvMPGy.pgp Description: PGP signature
Re: [Amsn-devel] Release distribution...
[EMAIL PROTECTED] msn]$ make rpm mkdir -p ./distrib rm -f THIS.TK.SPEC echo %define _builddir `pwd` THIS.AMSN.SPEC echo %define _rpmdir /tmp/RPMS THIS.AMSN.SPEC echo %define _prefix /usr THIS.AMSN.SPEC echo %define _tmppath /tmp THIS.AMSN.SPEC echo %define _datadir /usr/share/amsn THIS.AMSN.SPEC echo %define _bindir /usr/bin THIS.AMSN.SPEC echo %define _doc_files docs CREDITS FAQ GNUGPL HELP README TODO AGREEMENT remote.help THIS.AMSN.SPEC echo %define _platform `uname -m` THIS.AMSN.SPEC echo %define _version 0.95cvs THIS.AMSN.SPEC echo %define __release `cat cvs_date|head -c8` THIS.AMSN.SPEC cat amsn.spec THIS.AMSN.SPEC mkdir -p /tmp/RPMS rpmbuild -bb THIS.AMSN.SPEC error: Macro % has illegal name (%define) Executing(%prep): /bin/sh -e /tmp/rpm-tmp.29672 + umask 022 + cd /home/tjikkun/programs/msn + LANG=C + export LANG + unset DISPLAY + exit 0 Executing(%build): /bin/sh -e /tmp/rpm-tmp.29672 + umask 022 + cd /home/tjikkun/programs/msn + LANG=C + export LANG + unset DISPLAY + make make[1]: Entering directory `/home/tjikkun/programs/msn' make[1]: Nothing to be done for `build'. make[1]: Leaving directory `/home/tjikkun/programs/msn' + exit 0 Executing(%install): /bin/sh -e /tmp/rpm-tmp.30726 + umask 022 + cd /home/tjikkun/programs/msn + LANG=C + export LANG + unset DISPLAY + mkdir -p /tmp/build-amsn-0.95cvs/usr/share/amsn + mkdir -p /tmp/build-amsn-0.95cvs/usr/bin + make rpm-install INSTALL_PREFIX=/tmp/build-amsn-0.95cvs make[1]: Entering directory `/home/tjikkun/programs/msn' rm -Rf /tmp/build-amsn-0.95cvs//usr/share/amsn mkdir --parents /tmp/build-amsn-0.95cvs//usr/share/amsn find /tmp/build-amsn-0.95cvs//usr/share/amsn -name CVS -print | xargs rm -Rf mkdir --parents /tmp/build-amsn-0.95cvs//usr/bin ln -sf /usr/share/amsn/amsn /tmp/build-amsn-0.95cvs//usr/bin/amsn make[1]: Leaving directory `/home/tjikkun/programs/msn' + mkdir -p /tmp/build-amsn-0.95cvs/usr/share/applications + cp /tmp/build-amsn-0.95cvs/usr/share/amsn/amsn.desktop /tmp/build-amsn-0.95cvs/usr/share/applications + mkdir -p /tmp/build-amsn-0.95cvs/usr/share/pixmaps + ln -s -f /usr/share/amsn/icons/48x48/msn.png /tmp/build-amsn-0.95cvs/usr/share/pixmaps/msn.png + /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile Processing files: amsn-0.95cvs-20051122 Executing(%doc): /bin/sh -e /tmp/rpm-tmp.7889 + umask 022 + cd /home/tjikkun/programs/msn + DOCDIR=/tmp/build-amsn-0.95cvs/usr/share/doc/amsn-0.95cvs + export DOCDIR + rm -rf /tmp/build-amsn-0.95cvs/usr/share/doc/amsn-0.95cvs + /bin/mkdir -p /tmp/build-amsn-0.95cvs/usr/share/doc/amsn-0.95cvs + cp -pr docs CREDITS FAQ GNUGPL HELP README TODO AGREEMENT remote.help /tmp/build-amsn-0.95cvs/usr/share/doc/amsn-0.95cvs + exit 0 error: magic_file(ms, /tmp/build-amsn-0.95cvs/usr/share/amsn/AGREEMENT) failed: mode 3700644 invalid type 20 in mconvert() rpmbuild: rpmfc.c:1241: rpmfcClassify: Assertion `ftype != ((void *)0)' failed. make: *** [rpm] Aborted --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release distribution...
On Monday 21 November 2005 09:45, Youness Alaoui wrote: Hello, hello.. you wanted feedback, here it is : [EMAIL PROTECTED]:~/msn$ make rpm make: *** No rule to make target `/bin/rpm', needed by `rpm'. Stop. I don't think /bin/rpm is needed as a make rule. I removed it and it works on my gentoo machine. I also had to change the uname -i command to uname -m to get the right architecture. [EMAIL PROTECTED]:~/msn$ make deb mkdir -p ./distrib/DEB sed 1s/#VERSION#/0.95cvs-`cat cvs_date|head -c8`/ debian/changelog.in debian/changelog dpkg-buildpackage -b -D dpkg-buildpackage: source package is amsn dpkg-buildpackage: source version is 0.95cvs-20051121 dpkg-buildpackage: source changed by Phil [EMAIL PROTECTED] dpkg-buildpackage: host architecture i386 debian/rules clean make[1]: Entering directory `/home/kakaroto/msn' dh_testdir dh_testroot dh_testroot: You must run this as root (or use fakeroot). make[1]: *** [clean] Error 1 make[1]: Leaving directory `/home/kakaroto/msn' make: *** [deb] Error 2 I don't know what's the problem with the make rpm, maybe it's because I don't have rpm in /bin/rpm but in /usr/bin/rpm (I'm using a debian system) and the dpkg is probably because I'm not as root (I think so :P) so I don't know if you want to do something about that, like use fakeroot or something, because most users might want to create a .deb file without being root.. KaKaRoTo On Sun, 20 Nov 2005 12:10:47 -0500, Le Philousophe - Phil [EMAIL PROTECTED] wrote: Hi, I improved the distribution system : I added the support for deb files Now to create packages you can do : make deb for dpkg system make rpm for rpm system In addition I modified the version system in the autoconf script : configure.ac We have 4 fields at the beginning : APPNAME which wasn't change and is always amsn (because amsn is always amsn :p) APPVERSION which is now 0.95 and not 0.95cvs APPRELEASE which is 1 but is ignored for the moment APPSTABLE which is actually no. WE HAVE TO CHANGE THIS FIELD JUST BEFORE THE RELEASE !! It switches between two version system : the unstable which set versions as 0.95cvs-mmdd (taken from cvs_date) and the stable one : 0.95-n where n is the release. So before the release we have to change APPSTABLE to yes and redid autoconf (should be automatic when doing make). All of ways when you will generate a package you will see the bad filename but it's always better to change it before : it avoids to do the job twice :p Phil P.S. Before the release, we should check the binaries for Windows, especially TkCxImage since I modified a little the code after the last DLL committing. Arieh, can you complie with the last source before releasing the 0.95 ?? --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- Karol Krizka pgpuMegxciKGV.pgp Description: PGP signature
Re: [Amsn-devel] Release distribution...
Hi, Thanks a lot for all your work, it's really appreciated. I have a few things to talk about, but it will be short... : 1 - good job everyone, I'm such everyone here will be proud of the 0.95 release! :) 2 - I didn't have time yesterday, and I don't know about today (sunday).. but I'll see what I can do.. problem is, I don't know what to do and I don't know what others are doing... can we get a TODO list of what needs to be done for the release, with flags for what has been done, and initials for what is being done by who ? maybe put it in the wiki and send a link here. 3 - What I though of doing is to finish my work on the cam2mpeg utility that I want to provide with amsn.. do you all accept I spend time on this or do you suggest I leave it alone and use my little free time on something more needed ? 4 - I sent a mail a few weeks ago about how cvs should be re-arranged... a lot of files that are there while they shouldn't, etc... if you look at amsn's directory, you'll see it's around 44MB, if we clean the correct things (all the list I gave last time), you'll see it will take only 6MB... once compressed it's 1.5MB ... we should fix those issues before releasing and we should also make sure the package contains the minimal thing (no source files, no mac/windows things if it's linux, no unused things (like pixmapbutton), etc...) I think that's it... you see 4 points in such a small email, I'm getting better :P KaKaRoTo On Sun, 20 Nov 2005 12:10:47 -0500, Le Philousophe - Phil [EMAIL PROTECTED] wrote: Hi, I improved the distribution system : I added the support for deb files Now to create packages you can do : make deb for dpkg system make rpm for rpm system In addition I modified the version system in the autoconf script : configure.ac We have 4 fields at the beginning : APPNAME which wasn't change and is always amsn (because amsn is always amsn :p) APPVERSION which is now 0.95 and not 0.95cvs APPRELEASE which is 1 but is ignored for the moment APPSTABLE which is actually no. WE HAVE TO CHANGE THIS FIELD JUST BEFORE THE RELEASE !! It switches between two version system : the unstable which set versions as 0.95cvs-mmdd (taken from cvs_date) and the stable one : 0.95-n where n is the release. So before the release we have to change APPSTABLE to yes and redid autoconf (should be automatic when doing make). All of ways when you will generate a package you will see the bad filename but it's always better to change it before : it avoids to do the job twice :p Phil P.S. Before the release, we should check the binaries for Windows, especially TkCxImage since I modified a little the code after the last DLL committing. Arieh, can you complie with the last source before releasing the 0.95 ?? --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release distribution...
ok... maybe what I sent in my previous email should be added ? yes/no ? what I also noticed is that there was a kind of list for the release in the 0.95RC TODO thread... if not, at least, it had the name of the packagers who should take care of which package distro.. I think it's outdated in the wiki.. KaKaRoTo On Sun, 20 Nov 2005 13:15:33 -0500, Jérôme Gagnon-Voyer [EMAIL PROTECTED] wrote: I added it in a subsection of the release guide and modified the release guide http://amsn.sourceforge.net/wiki/tiki-index.php?page=Release+Guide As I said before, I would like people to look at the release guide to be sure it's complete. Le 05-11-20 à 12:10, Le Philousophe - Phil a écrit : Hi, I improved the distribution system : I added the support for deb files Now to create packages you can do : make deb for dpkg system make rpm for rpm system In addition I modified the version system in the autoconf script : configure.ac We have 4 fields at the beginning : APPNAME which wasn't change and is always amsn (because amsn is always amsn :p) APPVERSION which is now 0.95 and not 0.95cvs APPRELEASE which is 1 but is ignored for the moment APPSTABLE which is actually no. WE HAVE TO CHANGE THIS FIELD JUST BEFORE THE RELEASE !! It switches between two version system : the unstable which set versions as 0.95cvs-mmdd (taken from cvs_date) and the stable one : 0.95-n where n is the release. So before the release we have to change APPSTABLE to yes and redid autoconf (should be automatic when doing make). All of ways when you will generate a package you will see the bad filename but it's always better to change it before : it avoids to do the job twice :p Phil P.S. Before the release, we should check the binaries for Windows, especially TkCxImage since I modified a little the code after the last DLL committing. Arieh, can you complie with the last source before releasing the 0.95 ?? --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] Release distribution...
http://amsn.sourceforge.net/wiki/tiki-index.php?page=Release+GuideIf you think we should add something, just tell it, this is the thiing we should use to make the release. Everything is there.Le 05-11-20 à 13:21, Youness Alaoui a écrit : 2 - I didn't have time yesterday, and I don't know about today (sunday).. but I'll see what I can do.. problem is, I don't know what to do and I don't know what others are doing... can we get a TODO list of what needs to be done for the release, with flags for what has been done, and initials for what is being done by who ? maybe put it in the wiki and send a link here.
Re: [Amsn-devel] Release distribution...
On Sunday 20 November 2005 10:28, Youness Alaoui wrote: On Sun, 20 Nov 2005 13:21:27 -0500, Youness Alaoui 4 - I sent a mail a few weeks ago about how cvs should be re-arranged... a lot of files that are there while they shouldn't, etc... if you look at amsn's directory, you'll see it's around 44MB, if we clean the correct things (all the list I gave last time), you'll see it will take only 6MB... once compressed it's 1.5MB ... we should fix those issues before releasing and we should also make sure the package contains the minimal thing (no source files, no mac/windows things if it's linux, no unused things (like pixmapbutton), etc...) here's the thread about that mail : http://comments.gmane.org/gmane.network.instant-messaging.amsn.devel/69 I'll go though the list and see what I can remove. Just a question, is the linphone plugin usable or can it be deleted? -- Karol Krizka pgpd3f5ujozyx.pgp Description: PGP signature
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
2005/11/17, Harry Vennik [EMAIL PROTECTED]: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred wrote: 2005/11/17, Harry Vennik [EMAIL PROTECTED]: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) Greets. - -- () Alvaro J. Iradier Muro [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDfIeKoDlUrRluukQRAqocAKDsnqwWZmhF8cpTUj4dck+jjbpptQCg0AH2 NYwda8QDBbcHfePzDVwyaA4= =V1eX -END PGP SIGNATURE- --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
cool, I think it sets it up.. and I think, as Alvaro said, the opinion of the users is clear already... If we (devels) know that 0.95 is not complete and all, and we still want to release, then it means users will also want to release... I'll let the poll go until the week-end and then I'll do my best to find a little time and help in the release... unless someone requests the poll goes a little longer... Do you think anything should be done before the release ? here's my points : - check that 0.95.1 will be considered newer than 0.95 and 0.95.2 newer than 0.95.1 in the auto-update system... Maybe I'll think about other things before we release... KaKaRoTo On Thu, 17 Nov 2005 08:37:14 -0500, Alvaro J. Iradier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred wrote: 2005/11/17, Harry Vennik [EMAIL PROTECTED]: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) Greets. - -- () Alvaro J. Iradier Muro [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDfIeKoDlUrRluukQRAqocAKDsnqwWZmhF8cpTUj4dck+jjbpptQCg0AH2 NYwda8QDBbcHfePzDVwyaA4= =V1eX -END PGP SIGNATURE- --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
* I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) - -- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) I don't have time now, but probably wont have time tomorrow to write anything so I will make it short. I am not adding my name to these lists as I believe the options are flawed in the understandings, it appears that the 2 options have been combined into 1. Releasing 0.95 now means we release what we have as a complete stable release and then start working on 0.96. The second option is to release a 0.95 candidate and hold off new features until it has had a chance to be cleaned of any minor bugs that shouldn't have to wait till 0.96. Now I think we should release a 0.95 candidate and fix any bugs reported before starting to work on 0.96, I also think that is what Karol wanted before Youness explained the options and 'combined' them into 1. Whether we call the release 0.95RC1 followed by 0.95 or 0.95 followed by 0.95.1 is irrelevant, as long as the users know this is stable but still has some minor bugs that we want reported so that we can release a new patched release with no extra features. Whatever we call it 0.95 or 0.95RC1 shouldn't matter, as long as 0.94 recognises it as a new update. We can then correct the code to recognise the next release correctly (before releasing this 1). So what I am proposing is new options: * (1) I want to release 0.95 now but hold off on new features until we have had a chance to fix any bugs that get reported (notifying users that there may be some and we want them to report it - after checking the known issues page..): - Arieh * (2) I want to release 0.95 as a stable build and start working on 0.96 immediately: / Then a second question for those that chose (1) above; * (a) I want this release to be called 0.95RC1 then followed by 0.95: * (b) I want this release to be called 0.95 then followed by 0.95.1 etc * (c) I want this release to be called 0.95.1 then followed by 0.95.2 etc * (d) I don't really care as long as the check for new update is checked/fixed to work with what is chose: -Arieh Further comments: Arieh - I chose (d) as it doesn't matter to me, but out of the first 3 I would probably choose (c) if I was forced to make a choice. As long as we ensure that users were notified on amsn main page, and maybe even on the download page, that this release may contain some bugs but we endeavour to release a new version with just bug fixes and no extra features as soon as the bugs have been found and eradicated. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
On Thu, 17 Nov 2005 10:10:01 -0500, Arieh Schneier [EMAIL PROTECTED] wrote: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) - -- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) I don't have time now, but probably wont have time tomorrow to write anything so I will make it short. I am not adding my name to these lists as I believe the options are flawed in the understandings, it appears that the 2 options have been combined into 1. Releasing 0.95 now means we release what we have as a complete stable release and then start working on 0.96. The second option is to release a 0.95 candidate and hold off new features until it has had a chance to be cleaned of any minor bugs that shouldn't have to wait till 0.96. Now I think we should release a 0.95 candidate and fix any bugs reported before starting to work on 0.96, I also think that is what Karol wanted before Youness explained the options and 'combined' them into 1. Ok, I guess I wasn't clear enough on both possibilities.. the first one is we release 0.95 now, start working on new features, bug fixes, and when we think that our 0.95TODO is completed and almost all bugs known were fixed, we release a more stable release of 0.95 (with bug fixes AND new features if any were added since the 0.95 release)... The second choice is we keep it as it is now which means that we will continue waiting for the 0.95RC TODO to be finished (webcam assistant is the one I'm thinking about now...) THEN we release 0.95RC1 (it doesn't mean now...) then once it's out, we'll work on the pending issues only, until we get the whole 0.95 TODO completed without adding new features.. I'm actually asking to go into an anarchy instead of an democracy... (I don't want it to be a dictature either).. so these are my 2 choices... and I chose the anarchy... to just get it out and fix it later because I think we're never gonna release anything if we keep it like this... If still uncertain, I can try and explain how the 2 options are not the same.. Whether we call the release 0.95RC1 followed by 0.95 or 0.95 followed by 0.95.1 is irrelevant, as long as the users know this is stable but still has some minor bugs that we want reported so that we can release a new patched release with no extra features. Well, changing the build number doesn't mean it has only bug fixes, it means it has minor fixes... so 0.95.1 can have new features and bug fixes for 0.95 while 0.95RC1 means it's a release candidate, it means we're not yet into the 0.95 state and it means that we're only waiting for bugs to come in and the 0.95 release will only be bug fixes of the RC.. That's why I said 0.95-0.95.1 instead of 0.95RC1-0.95 Whatever we call it 0.95 or 0.95RC1 shouldn't matter, as long as 0.94 recognises it as a new update. We can then correct the code to recognise the next release correctly (before releasing this 1). So what I am proposing is new options: Well, as I just said, it's not that irrelevant because of the implied meaning of each release, but it's not important and we don't really care about that, and as you said, as long as 0.94 reconizes both releases as newer and the next release to be out should have a fix in order to reconize later versions correctly.. * (1) I want to release 0.95 now but hold off on new features until we have had a chance to fix any bugs that get reported (notifying users that there may be some and we want them to report it - after checking the known issues page..): - Arieh * (2) I want to release 0.95 as a stable build and start working on 0.96 immediately: - Youness.. The reason is because the 0.95 is not going to be released because we finished our TODO, it's because the development has stalled.. I think noone is motivated now because there is a feature freeze.. if we remove the feature freeze, we'll all (those who have time) get motivated again and we'll work on amsn and at the same time, fix those bugs that were pending for a year... I answere 2, even if it says start working on 0.96.. I think it should be start working on the next release whether it's 0.96 with all it's milestones, TODO list, etc... or just next release being 0.95.1 with a few new features and bug fixes, or whatever.. as long as we can say to everybody do whatever you want now / Then a second question for those that chose (1) above; * (a) I want this release to be called 0.95RC1 then followed by 0.95: * (b) I want this release to be called 0.95 then followed by 0.95.1 etc
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
* I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro Phil (but need a rush before it) Tom * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) Phil (like Alvaro) Tom Le Philousophe - Phil wrote: Hey guys !! You are too complicated !!! I will answer to the old one since it's obvious that the name isn't the most important the real question is : Do we out something now ?? Other thing And MSNP11 ??? Do we leave it for post 0.95 ?? It is almost finished : I mean Sander wanted to do a thing with snit so I didn't committed my work... But I always have it and with it we have almost all ready !! For the packaging as I already said RPM maker is ready launch make rpm and nothing more. For Debian packaging, I think the most difficult was done with RPMs I need a spec file and it needs testing... Does a Knoppix live will be sufficient : I don't want to install Debian neither Ubuntu because I like my Fedora with its 2.6.14 kernel :p (a troll I know) Ah !! There is always the bug with the traydock for linux : it isn't finished yet... I think I haven't any skills... I need a developper knowing X programming now !! Hurry up !! :p Phil --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
On Thu, 17 Nov 2005 13:43:38 -0500, Le Philousophe - Phil [EMAIL PROTECTED] wrote: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro Phil (but need a rush before it) * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) Phil (like Alvaro) Hey guys !! You are too complicated !!! I will answer to the old one since it's obvious that the name isn't the most important the real question is : Do we out something now ?? well, the name is kind of important, but it's still a release issue... and if we ge something out now, it depends on the poll's results... btw... your vote was : Phil (but need a rush before it) what did it mean ? (maybe answer in french if you want) Other thing And MSNP11 ??? Do we leave it for post 0.95 ?? It is almost finished : I mean Sander wanted to do a thing with snit so I didn't committed my work... But I always have it and with it we have almost all ready !! yes, the problem is ALMOST ready.. also, it hasn't been tested enough yet.. and we need to leave some things for 0.96, right ? ;) also, we're doing this in order to get 0.95 out as soon as possible.. if we wait for the assistant, we'll never get 0.95 out, if we wait for MSNP11, it's even worse... now 0.95b is stable, I don't want to add MSNP11 and make it unstable.. it's a choice to be made and I think we should go with safety for the moment... For the packaging as I already said RPM maker is ready launch make rpm and nothing more. perfect For Debian packaging, I think the most difficult was done with RPMs I need a spec file and it needs testing... I think it's pretty easy to create the debian dir... Does a Knoppix live will be sufficient : I don't want to install Debian neither Ubuntu because I like my Fedora with its 2.6.14 kernel :p (a troll I know) I don't know about knoppix... you can try elive :D it's nice and very complete (with amsn cvs too ;)) Ah !! There is always the bug with the traydock for linux : it isn't finished yet... I think I haven't any skills... I need a developper knowing X programming now !! Hurry up !! :p Phil haha, you look like a seller if you call before midnight, you get a second rag for free!! hurry up!! :P you can ask your question on the forumns, maybe a user can help, or you can try on a forum of a different group, or the X mailing list... but here, I don't think any of us has knowledge of X development... Goood luck... btw... what's the bug with traydock and how important it is ? --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
Le Jeudi 17 Novembre 2005 20:26, Youness Alaoui a écrit : On Thu, 17 Nov 2005 13:43:38 -0500, Le Philousophe - Phil [EMAIL PROTECTED] wrote: * I want to release 0.95 NOW : Jerome Youness Karol Krizka Harry Fred Alvaro Phil (but need a rush before it) * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) --- * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. Harry Alvaro (I think the user opinion is clear!) Phil (like Alvaro) Hey guys !! You are too complicated !!! I will answer to the old one since it's obvious that the name isn't the most important the real question is : Do we out something now ?? well, the name is kind of important, but it's still a release issue... and if we ge something out now, it depends on the poll's results... btw... your vote was : Phil (but need a rush before it) what did it mean ? (maybe answer in french if you want) I need we have to rush on some troubles always existing like those I mentioned below, we have to analyze the bug reports on the site because it is interesting. In fact last week end I fixed a little bug but there was many bug reports about it !! It shows we don't use enough this powerful tool. I think there is always a bug on the webcam assistant with the channels but I am not sure since I saw a bug about it... Other thing And MSNP11 ??? Do we leave it for post 0.95 ?? It is almost finished : I mean Sander wanted to do a thing with snit so I didn't committed my work... But I always have it and with it we have almost all ready !! yes, the problem is ALMOST ready.. also, it hasn't been tested enough yet.. and we need to leave some things for 0.96, right ? ;) also, we're doing this in order to get 0.95 out as soon as possible.. if we wait for the assistant, we'll never get 0.95 out, if we wait for MSNP11, it's even worse... now 0.95b is stable, I don't want to add MSNP11 and make it unstable.. it's a choice to be made and I think we should go with safety for the moment... For the packaging as I already said RPM maker is ready launch make rpm and nothing more. perfect For Debian packaging, I think the most difficult was done with RPMs I need a spec file and it needs testing... I think it's pretty easy to create the debian dir... Does a Knoppix live will be sufficient : I don't want to install Debian neither Ubuntu because I like my Fedora with its 2.6.14 kernel :p (a troll I know) I don't know about knoppix... you can try elive :D it's nice and very complete (with amsn cvs too ;)) I will see : I only need the debian package construction kit. But what do you mean by dir ?? I don't want to create the repository but only the package to do make deb Ah !! There is always the bug with the traydock for linux : it isn't finished yet... I think I haven't any skills... I need a developper knowing X programming now !! Hurry up !! :p Phil haha, you look like a seller if you call before midnight, you get a second rag for free!! hurry up!! :P you can ask your question on the forumns, maybe a user can help, or you can try on a forum of a different group, or the X mailing list... but here, I don't think any of us has knowledge of X development... Goood luck... btw... what's the bug with traydock and how important it is ? It's a graphical issue : the back of the icon isn't drawn well --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
So what's next guys? What's remaining? Lee? The mac release is ready to go (all my compilations are done).I'm fucking ready for a release, I fixed few bugs tonight. I decided to go to bed one hour later to be able to finish what I wanted to finish, If I was able to do it, everybody is able to. We have the weekend guys just for that, do all the small things for the release.The steps for a release is that:http://amsn.sourceforge.net/wiki/tiki-index.php?page=Release+Guide Everybody, take a look and make sure it's complete.Lee, I know you did a lot of things on website side and documentation side. If you need help to finish things just ask me on MSN, I'm sure other people can help you too on that. If you have something to add...then say it heheLe 05-11-17 à 22:13, Karol Krizka a écrit :- check that 0.95.1 will be considered newer than 0.95 and 0.95.2 newerthan 0.95.1 in the auto-update system...Just did that and fixed it.
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
On Thursday 17 November 2005 21:22, Jérôme Gagnon-Voyer wrote: So what's next guys? What's remaining? Lee? The mac release is ready to go (all my compilations are done). I'm fucking ready for a release, I fixed few bugs tonight. I decided to go to bed one hour later to be able to finish what I wanted to finish, If I was able to do it, everybody is able to. We have the weekend guys just for that, do all the small things for the release. The steps for a release is that: http://amsn.sourceforge.net/wiki/tiki-index.php?page=Release+Guide Everybody, take a look and make sure it's complete. Lee, I know you did a lot of things on website side and documentation side. If you need help to finish things just ask me on MSN, I'm sure other people can help you too on that. If you have something to add...then say it hehe As you mentioned in the email to me, we should move the link to the bug reporting to our sf site. Forwarding in TCL does not work so the database would have to be moved. This is not hard as all that's needed is dump the database and recreate it at sf.net (I'll need the password). Then just move the files and edit the mysql settins in the config. -- Karol Krizka pgpjDrUKrJqQt.pgp Description: PGP signature
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
* I want to release 0.95 NOW : Jerome Youness * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) Karol Krizka * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. On Wed, 16 Nov 2005 23:27:50 -0500, Karol Krizka [EMAIL PROTECTED] wrote: On Wednesday 16 November 2005 20:12, Youness Alaoui wrote: Ok, here's the thing.. I think 0.95 is really great and people will like it ALOT (even with the glitches) especially those who don't know what a CVS is... I suggest we skip the 0.95RC1 release, we go directly to 0.95, we adapt the webcam wizard in order for it to work (I think it was already done.. who can confirm?) and we make sure the wizard is run on the first webcam send.. also, make it available in the Tools menu. We put up the new website, we change SF forum to the new forum, we make great packages (klik, autopackage, win32, mac, rpm/deb/tgz/whatever-else) and we release 0.95... we wait about a month or two, just the time needed to fix all new bugs and all pending issues and we release 0.95.1 What do you think ? I'm half half but I will on no. The 0.95 release has a lot of new changes and I dunno how much they are tested. Having an release candidate can bring in a wider audience, unless of course there are more cvs users than 0.94. We can then spend 2-3 weeks (a set period before release) fixing reported bugs and then just go straight to a stable release. That's the thing, 0.95 is I think the most stable release we ever had (0.94 was also stable, but not as much as 0.95 IN MY OPINION), I mean, I never have any bugs, problems but I remember when I began working for amsn and a few years later, we would always have at least 2 bugs a week... So I don't think it's a real issue having the current bugs as they are now.. Also, note one thing, if we release 0.95RC1, most people won't understand what RC1 means, it might seem strange and that's it.. and then, they'll see 0.95 is released and they won't get it as they already have 0.95 (RC1 but they don't know what that means so they consider it as being 0.95)... don't forget how many n00bs use amsn every day. Also, it will cause a problem with the auto-updated, it won't understand 0.95 as being newer than 0.95RC1... if we release 0.95 now and then 0.95.1 in a couple of weeks/months, then it's the same as 0.95RC then 0.95 ... in terms of release... The major problem now is that we don't have the manpower to do all that! everyone went into hibernation! noone is active, so we can't keep it like that... I mean, if you look at the important 0.95 TODO list, how many things were fixed in it lately ? none for the last month AT LEAST... if we continue like this, we'll NEVER get a 0.95 release out... The most important thing is also that the CVS version is widely used by a lot of people, so we could assume it has been tested enough!!! Jerome, I've seen your forum, can you tell us how many people downloaded the latest 0.95 beta release ON MAC ? do you have any number ? if you don't have all numbers, maybe just how many downloaded it using bittorrent ? I don't know if you have access to these stats... anyways. With the webcam feature introduced in amsn CVS a lot of people wanted to try out cvs just in order to get the webcam working, so we have a lot of users trying it each day now... almost every forum questions, or tracker questions or mails, almost anything from the past months are about CVS... can you tell me when is the last time you had to answer a question about the 0.94 release ? I don't even remember what it looked like... and noone talks about it anymore.. Anyways, that's my opinion and the reasons why I wanted to push 0.95 now, before wasting any more time... Thanks, KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
Re: [Amsn-devel] release 0.95 NOW? was : RE: TkCximage not loaded
* I want to release 0.95 NOW : Jerome Youness Karol Krizka * No, we keep the way we had before, release 0.95RC1, then RC2, then ... and 0.96 for next year... (hoping we finish what has been pending for 0.95RC1) * I want user's opinions Youness Karol Krizka * No, we'll take the vote from the developpers as being the ultimate decision. On Wed, 16 Nov 2005 23:27:50 -0500, Karol Krizka [EMAIL PROTECTED] wrote: Anyways, that's my opinion and the reasons why I wanted to push 0.95 now, before wasting any more time... Fain, you convinced me. I don't remember any bugs that get in the way of daily usage. Also I didn't know that the RC labelling will confuse the update notifier. I guess if any severe bugs are found we can just release a 0.95.1 version. yaay!! hehe, I didn't mean to convince you, I was just stating my opinion and my reasons.. but that's cool. The RC labeling will confuse the updated because I think it assumes the version number is numeric only...(and I think it supposes it's X.Y so maybe X.Y.Z will not work that good, but we'll have to test this)... There are some sever bugs at the moment... first the pwc driver bug should be fixed or the webcam_settings_bug variable should be accessed through the advanced preferences dialog... Also disconnections causes amsn to eat all the memory and possibly by killed by the kernel once it takes all the available memory. Btw. I think the memory used is increased when disconnected, but it still happens even without disconnections... one thing to look out for is the socket creation (proxy object if you remember...) I think those are the major issues we currently have, I might have forgotten something... -- KaKaRoTo --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
