That's what I was trying to think of. Should the next version(current
head) be 2.x or 1.x? 1.x signefies a stable version dose it not?
Fixing these bugs will requier lots of reading throught to find why it was
changed/disabeled. In the mean time I realy think the current 0.x code
should be our stable flag ship for releases in the file section.
As for 0.x branch can continue, I'l tag it 0.x.1 as I did some bugfixing
too it. Then I'l start on 0.x+1 and later release that as 0.x+1.0, just
like Jason said.
--- Jason Dorje Short <jd...@us...> wrote:
> Mike Mestnik wrote:
> > Since there are any number of unknowen small problems with CVS head.
> I'd
> > like to hack on 0.75 and bring closer to where CVS head is. Dose any
> one
> > know how I might branch this new work? Do I just need a branch name
> for
> > my work or would it be better to put HEAD on a development branch and
> move
> > Stable to cvs head? I guess I just want to rename branches withought
> > loosing history.
> >
> > Also under Featurs in README it says "game saving" dose any one know
> what
> > happened to that code?
>
> You can branch CVS with "cvs tag -j <tagname>". See the manual.
>
> For a short-term solution you can branch the original 0.75 and work on
> that [1]. But this won't help future development much. For a
> longer-term solution you should branch the current code and work on it
> until it's stable [2]. Of course most bugfixes you make will apply to
> both branches so they'll have to be committed separately.
>
> In freeciv we use static tags like R1_14_0 for a release and branch tags
>
> like S1_14 for a whole branch. We made a stable branch S1_14 before the
>
> 1.14.0 release, and let it stabilize through several beta cycles before
> releasing 1.14.0. After further bugfixes 1.14.1 was released based on
> this same branch. Meanwhile in the HEAD branch (the main branch)
> development work proceeded normally.
>
> [1] cvs up -r R0_75; cvs tag -j S0_75
> [2] cvs up -A; cvs tag -j S0_76
>
> jason
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel
>
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
|
