Re: next release TODO

bracnhes discussin is in another thread :P
we won't revert the changes, I was thinking about something as simple as :
if { $::version != "0.95.1" } {
   # encapsulate new feature's code in here
}



KKRT

On Sun, 29 Jan 2006 11:52:21 -0500, Harry Vennik <htvennik@xxxxxxxxx>  
wrote:

> Okay, I agree on that, but how is it to be done?
> We'll need to keep the release code separate then.
> I think it would be best to list the commits to revert, then after some  
> time
> of fixing bugs, create a branch, and revert the feature commits in the
> branch.
> Or did you plan to do it outside cvs?
>
> ---------- Oorspronkelijk bericht ----------
> Van: "Youness Alaoui" <kakaroto@xxxxxxxxxxxxxxxxxxxxxx>
> Onderwerp: [Amsn-devel] next release TODO
> Datum: zondag 29 januari 2006 09:20
>
>
> > 7 - review CIA's commit log (as above) and find out any new features  
> > introduced that doesn't fit into the next release (example, new  
> > contactlist code, msnp12, msnp13, etc...) and make up a list of those  
> > things to remove,search for the commits' diffs and make sure they do  
> > not  
> > appear on the next release
>
>
> -------------------------------------------------------
> 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@xxxxxxxxxxxxxxxxxxxxx
> 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642