mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff MAURY <jeffma...@jeffmaury.com>
Subject Re: Big mess in 2.0
Date Tue, 26 Nov 2013 22:08:47 GMT
I want to keep it because I don't like deleting stuff on the server that
may be pushed somewhere else. That's why I prefer to keep it but in read
only to make sure the current situation won't happen anymore.
But if we cannot have a read only mode, then delete it.

Jeff


On Tue, Nov 26, 2013 at 11:03 PM, Emmanuel Lécharny <elecharny@gmail.com>wrote:

> Le 11/26/13 10:40 PM, Jeff MAURY a écrit :
> > Hello,
> >
> > I'm restoring my Mina development environment after my disk crash.
> > I noticed we now have two branches for 2.0, the 2.0 and 2.0.8.
> > It seems most of the updates has been done in 2.0.
> > So I think we shoud clean up this situation.
> > I will propose:
> >
> >    - merge 2.0.8 into 2.0
>
> +1
> >    - put 2.0.8 in read only: don't know if Infra can do it, but I don't
> >    like deleting something on the server
>
> 2.0.8 is useless. Once it gets merged into 2.0, why should we keep it ?
> All in all, we can also just apply the few modifications done on 2.0.8
> (currently, only 2)
>
> We also need to get a 2.0.8 release cut pretty soon, as a few critical
> bugs have been fixed in this branch.
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
>


-- 
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message