[GeoNode-devel] 2.4.x Branch

Wed Dec 2 07:24:39 PST 2015

http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy

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