Hi,
Can anyone tell me if the branch 2.10.x is now only a bug-fix branch or new features are added to it as well.
I can successfully build 2.10.x branch without any issues while the develop branch has build errors with tests on as well as with skipping them. (errors come in domain module and in web module).
Anyways I can work with 2.10.x for now but it would be important to know if that is now just a bug-fix branch or still updated with new features.
Regards
Ameet
2013/12/9 Ameet Chaudhari <ameet.chaudhari@anonymised.com>:
Hi,
Can anyone tell me if the branch 2.10.x is now only a bug-fix branch or new
features are added to it as well.I can successfully build 2.10.x branch without any issues while the develop
branch has build errors with tests on as well as with skipping them. (errors
come in domain module and in web module).
Hi Ameet,
Branch 2.10.x is mostly for bug fixing, yes. If you manage to fix some
of this test errors, or some other errors, we will gladly accept your
pull request:
https://github.com/geonetwork/core-geonetwork/pulls
Anyways I can work with 2.10.x for now but it would be important to know if
that is now just a bug-fix branch or still updated with new features.
We are trying to focus on next version of geoNetwork, which we want to
be geoNetwork 3.0, as it has a lot of new features and a big change in
the way geoNetwork works internally:
https://github.com/geonetwork/core-geonetwork/wiki/Roadmap-GeoNetwork-3.0
Anyway, if you have any feature for 2.10.x, we will gladly consider it
to merge the pull request with the official 2.10.x branch (we have to
make sure it is very stable, before that).
But it won't be added to the 3.0 branch unless someone also does the
port. As said, architecture is heavily changed and this kind of ports
are not easy to manage from 2.10.x to 3.0. So, being realistic, any
pull request with new features on 2.10.x will not be probably ported
to next geoNetwork version. In my opinion, it will be a pity to put
efforts on new features for 2.10.x, unless it is something you need
now and cannot wait until 3.0 becomes beta (somewhat half next year).
Or it is something you can also port to 3.0 for future versions.
That was your question?
Regards,
María.
Regards
Ameet------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
On Mon, Dec 9, 2013 at 3:12 PM, María Arias de Reyna <delawen@anonymised.com>wrote:
2013/12/9 Ameet Chaudhari <ameet.chaudhari@anonymised.com>:
> Hi,
>
> Can anyone tell me if the branch 2.10.x is now only a bug-fix branch or
new
> features are added to it as well.
>
> I can successfully build 2.10.x branch without any issues while the
develop
> branch has build errors with tests on as well as with skipping them.
(errors
> come in domain module and in web module).Hi Ameet,
Branch 2.10.x is mostly for bug fixing, yes. If you manage to fix some
of this test errors, or some other errors, we will gladly accept your
pull request:
https://github.com/geonetwork/core-geonetwork/pulls
Thanks María, if I manage to fix these errors, sure I will do a pull
request.
Anyway, if you have any feature for 2.10.x, we will gladly consider it
to merge the pull request with the official 2.10.x branch (we have to
make sure it is very stable, before that).
I would be even more glad to have my pull requests accepted 
But it won't be added to the 3.0 branch unless someone also does the
port. As said, architecture is heavily changed and this kind of ports
are not easy to manage from 2.10.x to 3.0. So, being realistic, any
pull request with new features on 2.10.x will not be probably ported
to next geoNetwork version. In my opinion, it will be a pity to put
efforts on new features for 2.10.x, unless it is something you need
now and cannot wait until 3.0 becomes beta (somewhat half next year).
Or it is something you can also port to 3.0 for future versions.That was your question?
Yes indeed. I understand that changes to 2.10.x will be hard to port to 3.0.
I am eagerly watching for these changes to progress, but my work needs to
proceed now, waiting for 4-5 months is unfortunately not an option.
When 3.0 comes, I'll try if I can port my changes to it as well.
Thanks a lot, have a nice day.
Regards
Ameet