Re: How to proceed?

Hi, I added the information about patching a branch to the CMS site developer section. Maybe it's helpful for other people too :-) Maruan Sahyoun Am 03.05.2013 um 10:50 schrieb Thomas Chojecki i...@rayman2200.de: Am 01.05.2013 19:56, schrieb Andreas Lehmkuehler: Hi, Am 01.05.2013 11:55,

Re: How to proceed?

Am 01.05.2013 19:56, schrieb Andreas Lehmkuehler: Hi, Am 01.05.2013 11:55, schrieb Thomas Chojecki: Seems that I missing some basics knowledge about maintaining branches. I only used branches for bug fix releases without merging. So I would go the way just committing it on the branch and trunk

Re: How to proceed?

Hi, Am 30.04.2013 20:23, schrieb Thomas Chojecki: Hi all, the voting shows a clear tendency to use the trunk for the 2.0.0 version. It wasn't a real vote but I guess we have lazy consensus about it. Also the step to Java 1.6 as minimum requirement is a positive one. Yes, I just created a

Re: How to proceed?

Am 01.05.2013 11:27, schrieb Andreas Lehmkuehler: Am 30.04.2013 20:23, schrieb Thomas Chojecki: I will start doing first bugfixes and with the issue PDFBOX-1587 we will break the compatibility to the older version. So I have some question to the branches. There is only a 1.8 branch, can I

Re: How to proceed?

Hi, Am 01.05.2013 11:55, schrieb Thomas Chojecki: Am 01.05.2013 11:27, schrieb Andreas Lehmkuehler: Am 30.04.2013 20:23, schrieb Thomas Chojecki: I will start doing first bugfixes and with the issue PDFBOX-1587 we will break the compatibility to the older version. So I have some question to

Re: How to proceed?

Hi all, the voting shows a clear tendency to use the trunk for the 2.0.0 version. Also the step to Java 1.6 as minimum requirement is a positive one. I will start doing first bugfixes and with the issue PDFBOX-1587 we will break the compatibility to the older version. So I have some question

Re: How to proceed?

that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even

Re: How to proceed?

Am 26.04.2013 07:36, schrieb Andreas Lehmkühler: - use the current trunk for the ongoing development of 2.0.0 - use indivual branches for bigger changes in the trunk, as Guillaume did when refactoring xmpbox - use the current 1.8-branch [1] for bugfix-releases, as I did when releasing 1.8.1 - a

Re: How to proceed?

+1 too On Fri, Apr 26, 2013 at 9:23 AM, Thomas Chojecki i...@rayman2200.de wrote: Am 26.04.2013 07:36, schrieb Andreas Lehmkühler: - use the current trunk for the ongoing development of 2.0.0 - use indivual branches for bigger changes in the trunk, as Guillaume did when refactoring

Re: How to proceed?

that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9 feature

Re: How to proceed?

, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9 feature release should be possible by branching the 1.8-branch. WDYT? BR Andreas Lehmkühler

Re: How to proceed?

that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9

Re: How to proceed?

Am 18.04.2013 um 21:11 schrieb Andreas Lehmkuehler andr...@lehmi.de: Hi, what is our next target after releasing 1.8.0 and 1.8.1? We already started some discussions about that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how

Re: How to proceed?

, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9 feature

Re: How to proceed?

Hi, Am 19.04.2013 00:50, schrieb Maruan Sahyoun: I think there are different levels to think about which are interwoven a) which use cases do we support - parsing, text extraction, merging, form filling, viewing, creation …. - do we need more? can we drop some? Perhaps the creation of pdfs

Re: How to proceed?

Hi, Am 19.04.2013 09:47, schrieb Timo Boehme: Hi, For the 2.0 features: - switch to Java 1.6 What java6 only feature exactly are you thinking about? Best regards, Timo BR Andreas Lehmkühler

Re: How to proceed?

Hi, Am 18.04.2013 23:04, schrieb Thomas Chojecki: Hi, Back to topic. - I think we should try to focus on type safety first. More generic collections and code cleanup. That's a good point to start. - The other thing is the COSWriter. Writting recursive trough the document sounds good, but it

Re: How to proceed?

Hi, Regarding the discussion about 'latest work' and 'nearly deliverable work', I share Timo's opinion. When I made deep rework on xmpbox, as proposed by Andreas, I did it in a branch and merged when it was mostly ready. I think it is the best option to prepare the 2.0 because : * we do not know

Re: How to proceed?

Hi, Am 19.04.2013 17:50, schrieb Andreas Lehmkuehler: Hi, Am 19.04.2013 09:47, schrieb Timo Boehme: Hi, For the 2.0 features: - switch to Java 1.6 What java6 only feature exactly are you thinking about? First which comes to my mind is a very basic one that IOException can wrap another

How to proceed?

Hi, what is our next target after releasing 1.8.0 and 1.8.1? We already started some discussions about that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer

Re: How to proceed?

that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new

Re: How to proceed?

21:11 schrieb Andreas Lehmkuehler andr...@lehmi.de: Hi, what is our next target after releasing 1.8.0 and 1.8.1? We already started some discussions about that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should

Re: How to proceed?

...@lehmi.de: Hi, what is our next target after releasing 1.8.0 and 1.8.1? We already started some discussions about that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd

Re: How to proceed?

that topic, but I'd like to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9

Re: How to proceed?

to have clarification. Is it time to go for a 2.0 version? If we agree to that goal, how should we proceed? Should we branch or simply use the trunk? I'd prefer to continue using the trunk. We are still able to release bugfix versions using the 1.8-branch. Even a new 1.9 feature release should