It's been quite a while since there has been a crossfire release, so it seems
about time for one.
So I'm thinking that in a couple weeks time, packing up what is there as a
release and putting it up on sourceforge.
There are a few reasons for this announcement:
- If there is code/changes
On 11/14/10 09:19 PM, Mark Wedel wrote:
>
>Been a little more than 6 months since last official release, and I was
> thinking that trying to get one out before end of the year might be nice.
>
>Thoughts/comments?
>
>Any list of bugs or other things that must be fixed before a release is
On 11/22/10 10:19 AM, Nicolas Weeger wrote:
>>Client too old may be reasonable - at some point, the older clients
>> really will not work.
>>
>>It isn't feasible of course to test every client with every version of
>> the server, and vice versa. The problem of enforcing versions gets trick
> Client too old may be reasonable - at some point, the older clients
> really will not work.
>
> It isn't feasible of course to test every client with every version of
> the server, and vice versa. The problem of enforcing versions gets tricky
> - one does not want to force version 1.60 clie
On 11/20/10 01:04 AM, Nicolas Weeger wrote:
> Hello.
>
>
>>Been a little more than 6 months since last official release, and I was
>> thinking that trying to get one out before end of the year might be nice.
>>
>>Thoughts/comments?
>>
>>Any list of bugs or other things that must be fixe
Hello.
> Been a little more than 6 months since last official release, and I was
> thinking that trying to get one out before end of the year might be nice.
>
> Thoughts/comments?
>
> Any list of bugs or other things that must be fixed before a release is
> made?
Things to fix for the n
On 11/16/10 08:24 PM, Kevin R. Bulgrien wrote:
> IMO, it is time to ditch gtk-v2.glade as the default. It is becoming a
> not so uncommon event for a new user to come on IRC and have fits
> getting the important window panels to show up (inventory in particular).
> I've had one disappear off IRC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/16/10 10:24 PM, Kevin R. Bulgrien wrote:
> I don't really know of any serious stability
> reports out there, though some users seem to be confused by the
> account / character setup dialogs.
I've been working on the walk though for the new accou
> Been a little more than 6 months since last official release, and I was
> thinking that trying to get one out before end of the year might be nice.
>
> Thoughts/comments?
1.50.0 is broken. One cannot create a new character due to a .glade file
bug. A release is needed. Technically, a 1.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/10 11:19 PM, Mark Wedel wrote:
>
> Been a little more than 6 months since last official release, and I was
> thinking that trying to get one out before end of the year might be nice.
>
> Thoughts/comments?
There has been a number of ch
Been a little more than 6 months since last official release, and I was
thinking that trying to get one out before end of the year might be nice.
Thoughts/comments?
Any list of bugs or other things that must be fixed before a release is made?
Likewise, any list of the major changes sin
Just a note - I've put a copy of this document, with a few minor changes, on
the wiki:
http://wiki.metalforge.net/doku.php/crossfire_release_cycle
___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/cro
Also, about restructurations of code, svn unlike cvs does not 'forget'
the history of a file when it's moved. I use cvs a lot for work and
dureing refactoring of our code (which happens from time to time) we
already lost versions of some files because they were deleted / restored
/ deleted and
> I'm not sure about the other systems out there - once can spend a lot of
> time looking over all the documentation, etc. AS with our last discussion,
> I'm most inclined to stick with CVS since we know what it does and doesn't
> have any real major shortcomings (it works right now).
I'm in no
svn does branching and tagging, and according to this faq
(http://subversion.tigris.org/faq.html#merge-using-tags) it does it
pretty well.
basically svn does this to handle branching and merging
copy trunk -> myBranch
copy myBranch -> myBranchMerged
modify myBranch at will
copy the diff between
Some of SVN big advantages appears to be able to work offline (keeps copy of
data you checked out around so you can do diffs without needing connection, as
well as ungets). Some of the other features may not make as big a difference
to
us - ability to use different connection methods (that
Lalo Martins wrote:
>
>
Ahh yes, those are the sorts of SVN issues I've heard about, though I'm
not experienced with SVN myself.
> I believe the idea is to try some proper revision control system like bzr
> (there's
> free hosting at launchpad.net; you can host your own using only ssh and
> a
Mark Wedel wrote:
> As far as going to something else, I think it would have to be vastly
> better -
> sourceforge provides a nice free environment - it keeps things very simple -
> it
> is associated with a group, not a single person.
>
> Something that is not free or associated with one p
On Tue, 08 Aug 2006 00:44:01 -0700, Mark Wedel wrote:
> Alex Schultz wrote:
>>> - Should we switch to SVN? Switching repositories at same time as switching
>>>what the head branch means would make the most sense.
>>>
>> I agree that when switching what the head branch means makes the most
>
Nicolas Weeger (Laposte) wrote:
> Hello.
>
> I globally agree, a few points:
>
>>- Client and server releases will be done at same time, with matching
>> version numbers.
>> - Exception is micro releases, where it may be only the client or
>>only the server released.
>
> Th
Alex Schultz wrote:
>
>> - Should we switch to SVN? Switching repositories at same time as switching
>>what the head branch means would make the most sense.
>>
> I agree that when switching what the head branch means makes the most
> sense, however I'm not sure that to SVN would be a great
Hello.
I globally agree, a few points:
>- Client and server releases will be done at same time, with matching
> version numbers.
> - Exception is micro releases, where it may be only the client or
>only the server released.
This supposes client will evolve too. Experience s
Mark Wedel wrote:
> Per the recent discussion on code reorganization and what goes in what
> release, this document is an attempt to gather the points raised and make it
> into a formal document that can be included in the code or put on the wiki.
>
>
Those rules seem to make alot of sense to me.
Per the recent discussion on code reorganization and what goes in what
release, this document is an attempt to gather the points raised and make it
into a formal document that can be included in the code or put on the wiki.
This document does not attempt to justify or explain why different things
24 matches
Mail list logo
