<head></head><body>Hi all,<div><br></div><div>anyone who can create the 2.4 branch?</div><div><br></div><div>Thanks and happy new year!</div><div><br></div><div>Francesco</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Dec 2 2015, at 4:32 pm, Tom Kralidis <tom.kralidis@gmail.com> wrote:
<br>
<meta content="text/html; charset=utf-8"><div>Exactly. +1<br><br>Sent from my iPhone</div><div><br>On Dec 2, 2015, at 10:26, Ariel Nunez <<a href="mailto:ingenieroariel@gmail.com">ingenieroariel@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Patrick,<div><br></div><div>What I understood is that it means less alpha/beta/rc craze and just knowing that the 2.5.x releases would be 'development' and should not be used in production.</div><div><br></div><div>-a</div></div><div><br><div>On Wed, Dec 2, 2015 at 10:24 AM, Jeffrey Johnson <span dir="ltr"><<a href="mailto:ortelius@gmail.com" target="_blank">ortelius@gmail.com</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy" rel="noreferrer" target="_blank">http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy</a><br>
<div><div><br>
On Wed, Dec 2, 2015 at 10:22 PM, Patrick Dufour <<a href="mailto:pjdufour.dev@gmail.com">pjdufour.dev@gmail.com</a>> wrote:<br>
> By even/odd, do you mean bug fixes would be,<br>
><br>
> 2.4.1, 2.4.3, 2.4.5, 2.4.7, etc.<br>
><br>
> And that the stable releases will be:<br>
><br>
> 2.6.0, 2.8.0, 2.10.0, 2.12.0, etc.<br>
><br>
> Or some other sequence.<br>
><br>
> In regards, to the top number, I'd vote to stay on 2.x.x for a while and<br>
> only migrate to 3.x.x when there's a massive change.<br>
><br>
> On Dec 2, 2015 9:57 AM, "Paolo Corti" <<a href="mailto:pcorti@gmail.com">pcorti@gmail.com</a>> wrote:<br>
>><br>
>> +1 for even/odd and for 2.4.1 release<br>
>> cheers<br>
>> p<br>
>><br>
>> On Wed, Dec 2, 2015 at 9:29 AM, Alessio Fabiani<br>
>> <<a href="mailto:alessio.fabiani@geo-solutions.it">alessio.fabiani@geo-solutions.it</a>> wrote:<br>
>> > It should not, the GeoServer version is the same train. There can be an<br>
>> > issue if the users run a "paver setup" command maybe, which (as far as I<br>
>> > remember) deletes the GeoServer Data Dir.<br>
>> ><br>
>> > ==<br>
>> > GeoServer Professional Services from the experts! Visit<br>
>> > <a href="http://goo.gl/NWWaa2" rel="noreferrer" target="_blank">http://goo.gl/NWWaa2</a> for more information.<br>
>> > ==<br>
>> ><br>
>> > Ing. Alessio Fabiani<br>
>> > @alfa7691<br>
>> > Founder/Technical Lead<br>
>> ><br>
>> > GeoSolutions S.A.S.<br>
>> > Via Poggio alle Viti 1187<br>
>> > 55054 Massarosa (LU)<br>
>> > Italy<br>
>> > phone: <a value="+390584962313">+39 0584 962313</a><br>
>> > fax: <a value="+3905841660272">+39 0584 1660272</a><br>
>> > mob: <a value="+393316233686">+39 331 6233686</a><br>
>> ><br>
>> > <a href="http://www.geo-solutions.it" rel="noreferrer" target="_blank">http://www.geo-solutions.it</a><br>
>> > <a href="http://twitter.com/geosolutions_it" rel="noreferrer" target="_blank">http://twitter.com/geosolutions_it</a><br>
>> ><br>
>> > -------------------------------------------------------<br>
>> ><br>
>> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003<br>
>> ><br>
>> > Le informazioni contenute in questo messaggio di posta elettronica e/o<br>
>> > nel/i<br>
>> > file/s allegato/i sono da considerarsi strettamente riservate. Il loro<br>
>> > utilizzo è consentito esclusivamente al destinatario del messaggio, per<br>
>> > le<br>
>> > finalità indicate nel messaggio stesso. Qualora riceviate questo<br>
>> > messaggio<br>
>> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene<br>
>> > notizia<br>
>> > via e-mail e di procedere alla distruzione del messaggio stesso,<br>
>> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso,<br>
>> > divulgarlo<br>
>> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo<br>
>> > per<br>
>> > finalità diverse, costituisce comportamento contrario ai principi<br>
>> > dettati<br>
>> > dal D.Lgs. 196/2003.<br>
>> ><br>
>> ><br>
>> ><br>
>> > The information in this message and/or attachments, is intended solely<br>
>> > for<br>
>> > the attention and use of the named addressee(s) and may be confidential<br>
>> > or<br>
>> > proprietary in nature or covered by the provisions of privacy act<br>
>> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection<br>
>> > Code).Any use not in accord with its purpose, any disclosure,<br>
>> > reproduction,<br>
>> > copying, distribution, or either dissemination, either whole or partial,<br>
>> > is<br>
>> > strictly forbidden except previous formal approval of the named<br>
>> > addressee(s). If you are not the intended recipient, please contact<br>
>> > immediately the sender by telephone, fax or e-mail and delete the<br>
>> > information in this message that has been received in error. The sender<br>
>> > does<br>
>> > not give any warranty or accept liability as the content, accuracy or<br>
>> > completeness of sent messages and accepts no responsibility for changes<br>
>> > made after they were sent or for other risks which arise as a result of<br>
>> > e-mail transmission, viruses, etc.<br>
>> ><br>
>> ><br>
>> > On Wed, Dec 2, 2015 at 3:20 PM, Ariel Nunez <<a href="mailto:ingenieroariel@gmail.com">ingenieroariel@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> I am also in favor of even/odd, and releasing a 2.4.1 with bugfixes.<br>
>> >><br>
>> >> Alessio, we need to make sure that the new geoserver artifact does not<br>
>> >> wipe out the geoserver data dir on the user's computers. We have tested<br>
>> >> it<br>
>> >> with the geonode debian package but I am not sure it works on the<br>
>> >> geoserver-geonode debian package.<br>
>> >><br>
>> >> Jeff, we talked about even/odd during the code sprint and there seemed<br>
>> >> to<br>
>> >> be agreement in the room. But you are right that it has not received<br>
>> >> formal<br>
>> >> voting. Can we use this thread for people to vote concerns against it<br>
>> >> or<br>
>> >> support or should we do that in a github issue?<br>
>> >><br>
>> >> -a<br>
>> >><br>
>> >> On Wed, Dec 2, 2015 at 9:11 AM, Jeffrey Johnson <<a href="mailto:ortelius@gmail.com">ortelius@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Note Im not sure we agreed to do the even/odd numbering. Im in favor,<br>
>> >>> but I think we may need some more discussion before moving in this<br>
>> >>> direction.<br>
>> >>><br>
>> >>> On Wed, Dec 2, 2015 at 7:04 PM, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com">tomkralidis@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>> ><br>
>> >>> > +1 for a 2.4 branch. Note that at some point we agreed on using the<br>
>> >>> > even/odd strategy [1] for GeoNode releases, so our next stable<br>
>> >>> > release<br>
>> >>> > would be 2.6 (bug fix releases would be .z, i.e. 2.4.1, etc.).<br>
>> >>> ><br>
>> >>> > Comments? Should we have this documented somewhere?<br>
>> >>> ><br>
>> >>> > ..Tom<br>
>> >>> ><br>
>> >>> > [1]<br>
>> >>> ><br>
>> >>> ><br>
>> >>> > <a href="http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy" rel="noreferrer" target="_blank">http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy</a><br>
>> >>> ><br>
>> >>> > On Tue, 1 Dec 2015, Ariel Nunez wrote:<br>
>> >>> ><br>
>> >>> >> Date: Tue, 1 Dec 2015 19:47:53 -0500<br>
>> >>> >> From: Ariel Nunez <<a href="mailto:ingenieroariel@gmail.com">ingenieroariel@gmail.com</a>><br>
>> >>> >> To: Patrick Dufour <<a href="mailto:pjdufour.dev@gmail.com">pjdufour.dev@gmail.com</a>><br>
>> >>> >> Cc: geonode-devel <<a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a>><br>
>> >>> >> Subject: Re: [GeoNode-devel] 2.4.x Branch<br>
>> >>> >><br>
>> >>> >><br>
>> >>> >> I believe this is a good idea too.<br>
>> >>> >><br>
>> >>> >> -a<br>
>> >>> >><br>
>> >>> >> On Tue, Dec 1, 2015 at 3:04 PM, Patrick Dufour<br>
>> >>> >> <<a href="mailto:pjdufour.dev@gmail.com">pjdufour.dev@gmail.com</a>><br>
>> >>> >> wrote:<br>
>> >>> >><br>
>> >>> >>> We should create a 2.4.x branch on the main GeoNode repo like we<br>
>> >>> >>> have<br>
>> >>> >>> for<br>
>> >>> >>> 2.0.x.; unless we have a different plan underway to support 2.4<br>
>> >>> >>> and<br>
>> >>> >>> 2.5.<br>
>> >>> >>><br>
>> >>> >>> I did miss the road mapping day of the recent GeoNode code sprint,<br>
>> >>> >>> though. My ideas might be out of date.<br>
>> >>> >>><br>
>> >>> >>> Thanks!<br>
>> >>> >>><br>
>> >>> >>> Regards,<br>
>> >>> >>> Patrick Dufour<br>
>> >>> ><br>
>> >>> > _______________________________________________<br>
>> >>> > geonode-devel mailing list<br>
>> >>> > <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>> >>> > <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> geonode-devel mailing list<br>
>> >> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>> >> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > geonode-devel mailing list<br>
>> > <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>> > <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Paolo Corti<br>
>> Geospatial software developer<br>
>> web: <a href="http://www.paolocorti.net" rel="noreferrer" target="_blank">http://www.paolocorti.net</a><br>
>> twitter: @capooti<br>
>> skype: capooti<br>
>> _______________________________________________<br>
>> geonode-devel mailing list<br>
>> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> geonode-devel mailing list<br>
> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
><br>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>geonode-devel mailing list</span><br><span><a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a></span><br><span><a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a></span><br></div></blockquote>
</blockquote></body>