On Mon, 10 Apr 2006 20:27:33 -0400, Karol Krizka <[EMAIL PROTECTED]> wrote:

On Monday 10 April 2006 10:31, Youness Alaoui wrote:
ok, thanks! :p
I've enabled SVN, but now the repo is empty, I don't want to migrate CVS
YET... if we migrate to SVN, we'll need to do some things.. first, there
is no 'gateway'/bridge between cvs and svn, which means that a commit on
svn won't appear on cvs... which means that if we switch to SVN it will be
a FULL SWITCH, there will be NO MORE CVS AT ALL!!!!
wow, I began writing this email 5 hours ago, went to sleep, woke up, wrote
a bit, did some IRC support, and now I'm back, so let me get back all my
ideas...
oh yeah, so we'll need to completly shut down CVS, you understand that? so
we first need, before making any decision, to see what changes it will
involve...
first : once the migration request is sent to SF, we might wait 24h before the migration process is unqueued and done, which means no commits during
that time...
second : disabling CVS will only remove the 'CVS' webpage from our SF
site, but all CVS accesses will remain, which means our users who are used
to use (lol) cvs will still get the 'latest' cvs which is not the latest
svn...
we'll probably need to close CVS, something like delete all files (after a successfull migration) and put a single CVS_CLOSED.README file explaining
situation and giving link to svn instructions...
I would say have a finaly commit that replaces amsn with a script that pops up a box saying: "Go here to learn how to switch to SVN." and then after a month or so remove the repository completly. No need to keep it around as garbage
on sf.net's site.


yes, that's what I kind of said, different is that we can't remove the repository!! SF does not allow us to close a repo, so we'll have to delete all the files from the repo.. and in that case, why wait a month, we could just do it from the begining, and.. well, that's what I said before... we could keep a 'amsn' script that prints that to screen indeed... instead of a readme...


we'll need to update our language, we'll begin saying "do you use 0.95 or
svn?" and be ready for hundreds of support question similar to "what
svn??? I'm using the cvs version" or "svn? is it the codename for next
release?:D" etc...
we'll need to update the scripts for the cvs snapshot, which will become a svn snapshot, links to amsn_cvs.tar.gz will become amsn_svn.tar.gz, update
the FAQ...
Why not just use "devel" instead of svn or cvs? This would get rid of any such
problems in the future and makes more sence.


sounds good! I don't really like 'devel' as it reminds me of evil.. devel (6).. so n00bs would probably also not understand.. if we can find something similar, I'd say ok, if not, I'd say ok for devel.

we'll have to update CIA, see how we can ustomize the scripts for sending
emails to commit ML... for now we can have a mail sent on commit, but I
don't think we can modify the script to suit our purpose (like ignoring
the cvsdate commit)...
maybe cvsdate will need to be removed, because I hate the way it's done
and maybe svn will provide us with a solution by itself...
SVN does file versioning by repisitory, not file. So when you commit a change, it increments the "revision number" of the whole thing. I suppose we could
use this. I'm not sure how to get this easly through command line though,
without using the svn command. Maybe someone more familiar with this could
comment?

yeah, that's the idea I had, but I don't know how we could do it (looking in .svn, but where to look)... I'm also sure the revision is local, not on serverside, so we just need to find which files change on an update to 1 revision up, that will narrow our search... or ask in some svn forum, no ?

anything else related to cvs will need to be updated, which means a lot of
work involved, it's not a single click process...

now, what do you think and who wants to do it all (or help) ?

I'll be happy to help, but I have AP exams comming up in a month, so I will be studying for those. If after May 10th something still needs to be done, I'll
lend my hand.


we'll see, problem is that I don't feel like doing it, and I don't know about other people.. if someone is willing to divide the work, I'll do my part, but apart from that, I don't feel like doing it... i hope others will be more motivated! :)

KKRT


On Mon, 10 Apr 2006 04:18:16 -0400, Le Philousophe - Phil

<[EMAIL PROTECTED]> wrote:
> Just Do it ! ;)
> Phil
>
> Le Monday 10 April 2006 08:23, Youness Alaoui a écrit :
>> question...
>> are we going to migrate to SVN ? I don't want a poll over this, just a
>> simple "yes, we're just too lazy to do it"...
>>
>> KKRT
>>
>> On Mon, 10 Apr 2006 02:18:45 -0400, Youness Alaoui
>>
>> <[EMAIL PROTECTED]> wrote:
>> > tiki wiki has version 1.9.2 released too, we're still using 1.8.6..
>> > shouldn't that also be updated ?
>> >
>> >
>> > On Sun, 09 Apr 2006 21:56:46 -0400, Youness Alaoui
>> >
>> > <[EMAIL PROTECTED]> wrote:
>> >> phpBB 2.0.20 has been released on April 7th :
>> >> http://www.phpbb.com/phpBB/viewtopic.php?f=14&t=380687
>> >> you think we should upgrade ? someone wants to do it ?
>> >> btw, I found out that if you search for "word1 AND word2" in the
>> >> forums, it will search for forums containing both words!!! at last,
>>
>> the
>>
>> >> default is a OR, but the 'AND' keyword is recognized, I've been
>>
>> trying
>>
>> >> to acheive this for quite a while, I know vivia also wanted to be
>>
>> able
>>
>> >> to use the search facility more efficiently, now it seems it's easy
>> :
>> :)
>> :
>> >> Also note that I did some modifications to the bugs reporting system, >> >> you can take a look at it, what I simply did is to show 100 reports >> >> instead of 10, show the current range of reports and the total number
>> >> of reports shown. Also, in the showbug window, next to 'Reports'
>>
>> where
>>
>> >> it lists all reports matchinga  criteria, now it also displays the
>> >> number of reports that matched!
>> >> I noticed that sometimes the new bugs reports coming in are not
>> >> correctly filtered, iirc every incoming bug rport should be matched >> >> against all 'bugs', but it seems that some would match but are still
>> >> set as wild bugs.. Karol, can you confirm ? (simple way to test,
>>
>> open a
>>
>> >> high-pri bug and press 'Search', if it finds new bugs, it means that
>>
>> it
>>
>> >> wasn't able to match them when they were added to the DB...)
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> _______________________________________________
> 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 xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to