You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by Maruan Sahyoun <sa...@fileaffairs.de> on 2020/11/02 07:45:01 UTC
[DISCUSS] PDFBox 3.0.0
Dear fellow dev colleagues,
PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are we in a position to target a release for end of
year? Maybe by also dropping all open issues which do not have to go into the release but can be done at a later date because
they add functionality? What's missing, keeping us from doing it?
The other option would be to drop it entirely (move to sandbox or so) and rebase on the current 2.0 branch as many changes have
been backported and add the important pieces such as the new parser on top of that.
I'd like to find a way to get the good parts to our users quickly and moving forward to maybe do smaller, more targeted
increments.
Thoughts? Other/better ideas?
BR
Maruan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Am 02.12.20 um 18:37 schrieb sahyoun@fileaffairs.de:
> Hi,
>
> further the discussion about 3.0 - could we look at the open issues and
> pick the ones we think we will be working on for 3.0 and assign them
> accordingly. Proposal would be to remove the other ones from the 3.0
> target (by next Monday?). This way we get a better picture about what's
> missing.
+1
I already started with that and am going to continue to do so. Let us see how
many are left on monday.
I've just added two new version to JIRA (4.0.0 and 2.0.23) to support that.
> I will open a ticket for adding a migration guide which we can create
> content for in the days coming.
Good idea
Andreas
>
> WDYT?
>
> BR
> Maruan
>
> Am Donnerstag, den 05.11.2020, 12:12 +0100 schrieb Andreas Lehmkuehler:
>>
>> Am 03.11.20 um 20:49 schrieb Tilman Hausherr:
>>> Hi,
>>>
>>> I support having a 3.0 release because of the new parser.
>> OK, so lets proceed with Maruans proposal and try to become feature
>> complete by
>> the end of November. Once we reached that goal we can think about a
>> first
>> alpha/beta/release candidate of the trunk as 3.0
>>
>>> I'm against moving to git because I dislike git for its complexity.
>>> Git and its
>>> difficulties is probably the most frequent topic on http://dev.to .
>>> Using git
>>> means that I will have to spend brain cells on mastering it instead
>>> of working
>>> on PDFBox itself. I doubt it will attract new users - PDF is a
>>> successful but
>>> 20+ year old file format that is "unsexy" for most people.
>> We should postpone that discussion and move to a fresh thread.
>>
>> Andreas
>>
>>>
>>> Tilman
>>>
>>> Am 03.11.2020 um 08:40 schrieb Andreas Lehmkuehler:
>>>> Hi,
>>>>
>>>> Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
>>>>> Dear fellow dev colleagues,
>>>>>
>>>>> PDFBox 3.0.0 is in the works for quite some time now. Maybe for
>>>>> too long. Are
>>>>> we in a position to target a release for end of
>>>>> year? Maybe by also dropping all open issues which do not have
>>>>> to go into the
>>>>> release but can be done at a later date because
>>>>> they add functionality? What's missing, keeping us from doing
>>>>> it?
>>>> You are right, it already took too long. We can't wait until it
>>>> is "perfect".
>>>> I've already started to review my tickets and am going to
>>>> postpone some of the
>>>> TODOs on my personal PDFBox list. I hope to come back with a list
>>>> of TODOs for
>>>> 3.0 in a couple of days
>>>>
>>>>
>>>>> The other option would be to drop it entirely (move to sandbox
>>>>> or so) and
>>>>> rebase on the current 2.0 branch as many changes have
>>>>> been backported and add the important pieces such as the new
>>>>> parser on top of
>>>>> that.
>>>> That would end up in just another 3.0 version but with a lot of
>>>> additional
>>>> work to merge those changes and a lot of chances to introduce new
>>>> bugs. To sum
>>>> it up, IMHO that isn't an option for me.
>>>>
>>>>
>>>>> I'd like to find a way to get the good parts to our users
>>>>> quickly and moving
>>>>> forward to maybe do smaller, more targeted
>>>>> increments.
>>>> That's a good idea. We should find a way to have some sort of a
>>>> release plan,
>>>> so that our users including ourselves know what to expect. Maybe
>>>> something
>>>> like: one major per year with a list of planned features. A
>>>> missing feature
>>>> won't necessarily block a major release, bugfix releases as
>>>> needed.
>>>>
>>>>
>>>>> Thoughts? Other/better ideas?
>>>> First of all thanks for the valuable input and for starting the
>>>> discussion. We
>>>> are already releasing a lot of stuff but we need to find a way to
>>>> release the
>>>> majors more often.
>>>>
>>>> How about moving to git after the 3.0 release? I'm not one of
>>>> those guys which
>>>> are convinced that only a new tool can solve our issues, but it
>>>> would have
>>>> some advantages compared to svn:
>>>>
>>>> * working with feature branches would make it easier to
>>>> pick/postpone certain
>>>> features for a release
>>>> * reviews would be possible without committing the source to the
>>>> trunk first
>>>> * some unrelated side effect w.r.t. to the discussed release
>>>> issue, it may
>>>> attract more new users as people are getting used to use
>>>> git/github instead of
>>>> svn + patches.
>>>>
>>>>
>>>> Andreas
>>>>
>>>>> BR
>>>>> Maruan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------
>>>>> ------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>>>>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>>>>
>>>>
>>>>
>>>> -----------------------------------------------------------------
>>>> ----
>>>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>>>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>>>
>>>
>>>
>>> -------------------------------------------------------------------
>>> --
>>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by "sahyoun@fileaffairs.de" <sa...@fileaffairs.de>.
Hi,
further the discussion about 3.0 - could we look at the open issues and
pick the ones we think we will be working on for 3.0 and assign them
accordingly. Proposal would be to remove the other ones from the 3.0
target (by next Monday?). This way we get a better picture about what's
missing.
I will open a ticket for adding a migration guide which we can create
content for in the days coming.
WDYT?
BR
Maruan
Am Donnerstag, den 05.11.2020, 12:12 +0100 schrieb Andreas Lehmkuehler:
>
> Am 03.11.20 um 20:49 schrieb Tilman Hausherr:
> > Hi,
> >
> > I support having a 3.0 release because of the new parser.
> OK, so lets proceed with Maruans proposal and try to become feature
> complete by
> the end of November. Once we reached that goal we can think about a
> first
> alpha/beta/release candidate of the trunk as 3.0
>
> > I'm against moving to git because I dislike git for its complexity.
> > Git and its
> > difficulties is probably the most frequent topic on http://dev.to .
> > Using git
> > means that I will have to spend brain cells on mastering it instead
> > of working
> > on PDFBox itself. I doubt it will attract new users - PDF is a
> > successful but
> > 20+ year old file format that is "unsexy" for most people.
> We should postpone that discussion and move to a fresh thread.
>
> Andreas
>
> >
> > Tilman
> >
> > Am 03.11.2020 um 08:40 schrieb Andreas Lehmkuehler:
> > > Hi,
> > >
> > > Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
> > > > Dear fellow dev colleagues,
> > > >
> > > > PDFBox 3.0.0 is in the works for quite some time now. Maybe for
> > > > too long. Are
> > > > we in a position to target a release for end of
> > > > year? Maybe by also dropping all open issues which do not have
> > > > to go into the
> > > > release but can be done at a later date because
> > > > they add functionality? What's missing, keeping us from doing
> > > > it?
> > > You are right, it already took too long. We can't wait until it
> > > is "perfect".
> > > I've already started to review my tickets and am going to
> > > postpone some of the
> > > TODOs on my personal PDFBox list. I hope to come back with a list
> > > of TODOs for
> > > 3.0 in a couple of days
> > >
> > >
> > > > The other option would be to drop it entirely (move to sandbox
> > > > or so) and
> > > > rebase on the current 2.0 branch as many changes have
> > > > been backported and add the important pieces such as the new
> > > > parser on top of
> > > > that.
> > > That would end up in just another 3.0 version but with a lot of
> > > additional
> > > work to merge those changes and a lot of chances to introduce new
> > > bugs. To sum
> > > it up, IMHO that isn't an option for me.
> > >
> > >
> > > > I'd like to find a way to get the good parts to our users
> > > > quickly and moving
> > > > forward to maybe do smaller, more targeted
> > > > increments.
> > > That's a good idea. We should find a way to have some sort of a
> > > release plan,
> > > so that our users including ourselves know what to expect. Maybe
> > > something
> > > like: one major per year with a list of planned features. A
> > > missing feature
> > > won't necessarily block a major release, bugfix releases as
> > > needed.
> > >
> > >
> > > > Thoughts? Other/better ideas?
> > > First of all thanks for the valuable input and for starting the
> > > discussion. We
> > > are already releasing a lot of stuff but we need to find a way to
> > > release the
> > > majors more often.
> > >
> > > How about moving to git after the 3.0 release? I'm not one of
> > > those guys which
> > > are convinced that only a new tool can solve our issues, but it
> > > would have
> > > some advantages compared to svn:
> > >
> > > * working with feature branches would make it easier to
> > > pick/postpone certain
> > > features for a release
> > > * reviews would be possible without committing the source to the
> > > trunk first
> > > * some unrelated side effect w.r.t. to the discussed release
> > > issue, it may
> > > attract more new users as people are getting used to use
> > > git/github instead of
> > > svn + patches.
> > >
> > >
> > > Andreas
> > >
> > > > BR
> > > > Maruan
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------
> > > > ------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > > > For additional commands, e-mail: dev-help@pdfbox.apache.org
> > > >
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > > For additional commands, e-mail: dev-help@pdfbox.apache.org
> > >
> >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > For additional commands, e-mail: dev-help@pdfbox.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
--
--
Maruan Sahyoun
FileAffairs GmbH
Josef-Schappe-Straße 21
40882 Ratingen
Tel: +49 (2102) 89497 88
Fax: +49 (2102) 89497 91
sahyoun@fileaffairs.de
www.fileaffairs.de
Geschäftsführer: Maruan Sahyoun
Handelsregister: AG Düsseldorf, HRB 53837
UST.-ID: DE248275827
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Am 03.11.20 um 20:49 schrieb Tilman Hausherr:
> Hi,
>
> I support having a 3.0 release because of the new parser.
OK, so lets proceed with Maruans proposal and try to become feature complete by
the end of November. Once we reached that goal we can think about a first
alpha/beta/release candidate of the trunk as 3.0
> I'm against moving to git because I dislike git for its complexity. Git and its
> difficulties is probably the most frequent topic on http://dev.to . Using git
> means that I will have to spend brain cells on mastering it instead of working
> on PDFBox itself. I doubt it will attract new users - PDF is a successful but
> 20+ year old file format that is "unsexy" for most people.
We should postpone that discussion and move to a fresh thread.
Andreas
>
> Tilman
>
> Am 03.11.2020 um 08:40 schrieb Andreas Lehmkuehler:
>> Hi,
>>
>> Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
>>> Dear fellow dev colleagues,
>>>
>>> PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are
>>> we in a position to target a release for end of
>>> year? Maybe by also dropping all open issues which do not have to go into the
>>> release but can be done at a later date because
>>> they add functionality? What's missing, keeping us from doing it?
>> You are right, it already took too long. We can't wait until it is "perfect".
>> I've already started to review my tickets and am going to postpone some of the
>> TODOs on my personal PDFBox list. I hope to come back with a list of TODOs for
>> 3.0 in a couple of days
>>
>>
>>> The other option would be to drop it entirely (move to sandbox or so) and
>>> rebase on the current 2.0 branch as many changes have
>>> been backported and add the important pieces such as the new parser on top of
>>> that.
>> That would end up in just another 3.0 version but with a lot of additional
>> work to merge those changes and a lot of chances to introduce new bugs. To sum
>> it up, IMHO that isn't an option for me.
>>
>>
>>> I'd like to find a way to get the good parts to our users quickly and moving
>>> forward to maybe do smaller, more targeted
>>> increments.
>> That's a good idea. We should find a way to have some sort of a release plan,
>> so that our users including ourselves know what to expect. Maybe something
>> like: one major per year with a list of planned features. A missing feature
>> won't necessarily block a major release, bugfix releases as needed.
>>
>>
>>> Thoughts? Other/better ideas?
>> First of all thanks for the valuable input and for starting the discussion. We
>> are already releasing a lot of stuff but we need to find a way to release the
>> majors more often.
>>
>> How about moving to git after the 3.0 release? I'm not one of those guys which
>> are convinced that only a new tool can solve our issues, but it would have
>> some advantages compared to svn:
>>
>> * working with feature branches would make it easier to pick/postpone certain
>> features for a release
>> * reviews would be possible without committing the source to the trunk first
>> * some unrelated side effect w.r.t. to the discussed release issue, it may
>> attract more new users as people are getting used to use git/github instead of
>> svn + patches.
>>
>>
>> Andreas
>>
>>> BR
>>> Maruan
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Tilman Hausherr <TH...@t-online.de>.
Hi,
I support having a 3.0 release because of the new parser.
I'm against moving to git because I dislike git for its complexity. Git
and its difficulties is probably the most frequent topic on
http://dev.to . Using git means that I will have to spend brain cells on
mastering it instead of working on PDFBox itself. I doubt it will
attract new users - PDF is a successful but 20+ year old file format
that is "unsexy" for most people.
Tilman
Am 03.11.2020 um 08:40 schrieb Andreas Lehmkuehler:
> Hi,
>
> Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
>> Dear fellow dev colleagues,
>>
>> PDFBox 3.0.0 is in the works for quite some time now. Maybe for too
>> long. Are we in a position to target a release for end of
>> year? Maybe by also dropping all open issues which do not have to go
>> into the release but can be done at a later date because
>> they add functionality? What's missing, keeping us from doing it?
> You are right, it already took too long. We can't wait until it is
> "perfect". I've already started to review my tickets and am going to
> postpone some of the TODOs on my personal PDFBox list. I hope to come
> back with a list of TODOs for 3.0 in a couple of days
>
>
>> The other option would be to drop it entirely (move to sandbox or so)
>> and rebase on the current 2.0 branch as many changes have
>> been backported and add the important pieces such as the new parser
>> on top of that.
> That would end up in just another 3.0 version but with a lot of
> additional work to merge those changes and a lot of chances to
> introduce new bugs. To sum it up, IMHO that isn't an option for me.
>
>
>> I'd like to find a way to get the good parts to our users quickly and
>> moving forward to maybe do smaller, more targeted
>> increments.
> That's a good idea. We should find a way to have some sort of a
> release plan, so that our users including ourselves know what to
> expect. Maybe something like: one major per year with a list of
> planned features. A missing feature won't necessarily block a major
> release, bugfix releases as needed.
>
>
>> Thoughts? Other/better ideas?
> First of all thanks for the valuable input and for starting the
> discussion. We are already releasing a lot of stuff but we need to
> find a way to release the majors more often.
>
> How about moving to git after the 3.0 release? I'm not one of those
> guys which are convinced that only a new tool can solve our issues,
> but it would have some advantages compared to svn:
>
> * working with feature branches would make it easier to pick/postpone
> certain features for a release
> * reviews would be possible without committing the source to the trunk
> first
> * some unrelated side effect w.r.t. to the discussed release issue, it
> may attract more new users as people are getting used to use
> git/github instead of svn + patches.
>
>
> Andreas
>
>> BR
>> Maruan
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Maruan Sahyoun <sa...@fileaffairs.de>.
> Am 03.11.20 um 10:03 schrieb Maruan Sahyoun:
> > Hi,
> >
> >
> >
> >
> > > Hi,
> > >
> > > Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
> > > > Dear fellow dev colleagues,
> > > >
> > > > PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are we in a position to target a release for end of
> > > > year? Maybe by also dropping all open issues which do not have to go into the release but can be done at a later date because
> > > > they add functionality? What's missing, keeping us from doing it?
> > > You are right, it already took too long. We can't wait until it is "perfect".
> > > I've already started to review my tickets and am going to postpone some of the
> > > TODOs on my personal PDFBox list. I hope to come back with a list of TODOs for
> > > 3.0 in a couple of days
> >
> > I'll do the same with mine - pick the open tickets and either assign/mark for 3.0.0 or drop if I won't do ones which are
> > assigned.
> >
> > What about targeting to stop actively working on 3.0 by End of Nov and then do some housekeeping/late fixes in Dec. This way by
> > end of Nov we might have a feature complete version.
> +1
>
> ....
>
> > > > I'd like to find a way to get the good parts to our users quickly and moving forward to maybe do smaller, more targeted
> > > > increments.
> > > That's a good idea. We should find a way to have some sort of a release plan, so
> > > that our users including ourselves know what to expect. Maybe something like:
> > > one major per year with a list of planned features. A missing feature won't
> > > necessarily block a major release, bugfix releases as needed.
> > >
> >
> > I find the release cycle Apache Camel has very attractive (they are more people though)
> > https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/
> Looks like some common scheme and IMHO quite good, but I'm afraid we haven't the
> manpower to support such schedule.
It's more about the scheme and commons terms such LTS and Feature Release not about the schedule itself (see my comment about
"... they have more people though ...")
>
>
> > What I think is that - after releasing 3.0
> >
> > 1.8 -> EOL
> Yes, I guess we already agreed on that a long time ago. ;-)
>
> > 2.0 -> LTS release (e.g. to be supported for 2 years)
> > 3.0 is our feature branch
> >
> > With the feature release we do quarterly increments having a joint discussion about the major feature(s) upfront to put in
> > (keeping time for bug fixes, contributions ... etc ).
> We are more or less using that schedule for our bugfix releases and again I
> don't see the manpower to work on feature releases as well. :-(
We typically do a mix of bugfixes and features already. Only question is if new features go into an LTS release or not.
>
> > And then - maybe in a years time or so - one of the 3.x releases will become LTS overlapping 2.0 wich will become EOL later and
> > so on. So for our users there is always a LTS version to keep a stable API and Java etc. version and a feature version where we
> > move quicker but have stable releases in between.
> Lets concentrate first on getting 3.0 out of the door it is long overdue ...
> meanwhile we can collect ideas on how to proceed
>
+1 for getting it out first and then plan the next steps.
> >
> > A little towards productizing PDFBox. >>
> > > > Thoughts? Other/better ideas?
> > > First of all thanks for the valuable input and for starting the discussion. We
> > > are already releasing a lot of stuff but we need to find a way to release the
> > > majors more often.
> > >
> > > How about moving to git after the 3.0 release? I'm not one of those guys which
> > > are convinced that only a new tool can solve our issues, but it would have some
> > > advantages compared to svn:
> > >
> > > * working with feature branches would make it easier to pick/postpone certain
> > > features for a release
> > > * reviews would be possible without committing the source to the trunk first
> > > * some unrelated side effect w.r.t. to the discussed release issue, it may
> > > attract more new users as people are getting used to use git/github instead of
> > > svn + patches.
> >
> > I prefer git over svn and other Apache projects already did the move. But I'm happy to keep svn if others like to do so.
> > Branching (although possible in svn), decentralized repo and better tooling support (with the tools I use) are the features why
> > I prefer git over svn.
> >
> > BR
> > Maruan
> >
> > >
> > > Andreas
> > >
> > > > BR
> > > > Maruan
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > > > For additional commands, e-mail: dev-help@pdfbox.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > > For additional commands, e-mail: dev-help@pdfbox.apache.org
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
--
Maruan Sahyoun
FileAffairs GmbH
Josef-Schappe-Straße 21
40882 Ratingen
Tel: +49 (2102) 89497 88
Fax: +49 (2102) 89497 91
sahyoun@fileaffairs.de
www.fileaffairs.de
Geschäftsführer: Maruan Sahyoun
Handelsregister: AG Düsseldorf, HRB 53837
UST.-ID: DE248275827
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Am 03.11.20 um 10:03 schrieb Maruan Sahyoun:
> Hi,
>
>> Hi,
>>
>> Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
>>> Dear fellow dev colleagues,
>>>
>>> PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are we in a position to target a release for end of
>>> year? Maybe by also dropping all open issues which do not have to go into the release but can be done at a later date because
>>> they add functionality? What's missing, keeping us from doing it?
>> You are right, it already took too long. We can't wait until it is "perfect".
>> I've already started to review my tickets and am going to postpone some of the
>> TODOs on my personal PDFBox list. I hope to come back with a list of TODOs for
>> 3.0 in a couple of days
>
> I'll do the same with mine - pick the open tickets and either assign/mark for 3.0.0 or drop if I won't do ones which are
> assigned.
>
> What about targeting to stop actively working on 3.0 by End of Nov and then do some housekeeping/late fixes in Dec. This way by
> end of Nov we might have a feature complete version.
+1
....
>>> I'd like to find a way to get the good parts to our users quickly and moving forward to maybe do smaller, more targeted
>>> increments.
>> That's a good idea. We should find a way to have some sort of a release plan, so
>> that our users including ourselves know what to expect. Maybe something like:
>> one major per year with a list of planned features. A missing feature won't
>> necessarily block a major release, bugfix releases as needed.
>>
>
> I find the release cycle Apache Camel has very attractive (they are more people though)
> https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/
Looks like some common scheme and IMHO quite good, but I'm afraid we haven't the
manpower to support such schedule.
> What I think is that - after releasing 3.0
>
> 1.8 -> EOL
Yes, I guess we already agreed on that a long time ago. ;-)
> 2.0 -> LTS release (e.g. to be supported for 2 years)
> 3.0 is our feature branch
>
> With the feature release we do quarterly increments having a joint discussion about the major feature(s) upfront to put in
> (keeping time for bug fixes, contributions ... etc ).
We are more or less using that schedule for our bugfix releases and again I
don't see the manpower to work on feature releases as well. :-(
> And then - maybe in a years time or so - one of the 3.x releases will become LTS overlapping 2.0 wich will become EOL later and
> so on. So for our users there is always a LTS version to keep a stable API and Java etc. version and a feature version where we
> move quicker but have stable releases in between.
Lets concentrate first on getting 3.0 out of the door it is long overdue ...
meanwhile we can collect ideas on how to proceed
>
> A little towards productizing PDFBox. >>
>>> Thoughts? Other/better ideas?
>> First of all thanks for the valuable input and for starting the discussion. We
>> are already releasing a lot of stuff but we need to find a way to release the
>> majors more often.
>>
>> How about moving to git after the 3.0 release? I'm not one of those guys which
>> are convinced that only a new tool can solve our issues, but it would have some
>> advantages compared to svn:
>>
>> * working with feature branches would make it easier to pick/postpone certain
>> features for a release
>> * reviews would be possible without committing the source to the trunk first
>> * some unrelated side effect w.r.t. to the discussed release issue, it may
>> attract more new users as people are getting used to use git/github instead of
>> svn + patches.
>
> I prefer git over svn and other Apache projects already did the move. But I'm happy to keep svn if others like to do so.
> Branching (although possible in svn), decentralized repo and better tooling support (with the tools I use) are the features why
> I prefer git over svn.
>
> BR
> Maruan
>
>>
>> Andreas
>>
>>> BR
>>> Maruan
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: dev-help@pdfbox.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Maruan Sahyoun <sa...@fileaffairs.de>.
Hi,
> Hi,
>
> Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
> > Dear fellow dev colleagues,
> >
> > PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are we in a position to target a release for end of
> > year? Maybe by also dropping all open issues which do not have to go into the release but can be done at a later date because
> > they add functionality? What's missing, keeping us from doing it?
> You are right, it already took too long. We can't wait until it is "perfect".
> I've already started to review my tickets and am going to postpone some of the
> TODOs on my personal PDFBox list. I hope to come back with a list of TODOs for
> 3.0 in a couple of days
I'll do the same with mine - pick the open tickets and either assign/mark for 3.0.0 or drop if I won't do ones which are
assigned.
What about targeting to stop actively working on 3.0 by End of Nov and then do some housekeeping/late fixes in Dec. This way by
end of Nov we might have a feature complete version.
>
> > The other option would be to drop it entirely (move to sandbox or so) and rebase on the current 2.0 branch as many changes have
> > been backported and add the important pieces such as the new parser on top of that.
> That would end up in just another 3.0 version but with a lot of additional work
> to merge those changes and a lot of chances to introduce new bugs. To sum it up,
> IMHO that isn't an option for me.
agreed
>
>
> > I'd like to find a way to get the good parts to our users quickly and moving forward to maybe do smaller, more targeted
> > increments.
> That's a good idea. We should find a way to have some sort of a release plan, so
> that our users including ourselves know what to expect. Maybe something like:
> one major per year with a list of planned features. A missing feature won't
> necessarily block a major release, bugfix releases as needed.
>
I find the release cycle Apache Camel has very attractive (they are more people though)
https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/
What I think is that - after releasing 3.0
1.8 -> EOL
2.0 -> LTS release (e.g. to be supported for 2 years)
3.0 is our feature branch
With the feature release we do quarterly increments having a joint discussion about the major feature(s) upfront to put in
(keeping time for bug fixes, contributions ... etc ).
And then - maybe in a years time or so - one of the 3.x releases will become LTS overlapping 2.0 wich will become EOL later and
so on. So for our users there is always a LTS version to keep a stable API and Java etc. version and a feature version where we
move quicker but have stable releases in between.
A little towards productizing PDFBox.
>
> > Thoughts? Other/better ideas?
> First of all thanks for the valuable input and for starting the discussion. We
> are already releasing a lot of stuff but we need to find a way to release the
> majors more often.
>
> How about moving to git after the 3.0 release? I'm not one of those guys which
> are convinced that only a new tool can solve our issues, but it would have some
> advantages compared to svn:
>
> * working with feature branches would make it easier to pick/postpone certain
> features for a release
> * reviews would be possible without committing the source to the trunk first
> * some unrelated side effect w.r.t. to the discussed release issue, it may
> attract more new users as people are getting used to use git/github instead of
> svn + patches.
I prefer git over svn and other Apache projects already did the move. But I'm happy to keep svn if others like to do so.
Branching (although possible in svn), decentralized repo and better tooling support (with the tools I use) are the features why
I prefer git over svn.
BR
Maruan
>
> Andreas
>
> > BR
> > Maruan
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> > For additional commands, e-mail: dev-help@pdfbox.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
--
Maruan Sahyoun
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: [DISCUSS] PDFBox 3.0.0
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Hi,
Am 02.11.20 um 08:45 schrieb Maruan Sahyoun:
> Dear fellow dev colleagues,
>
> PDFBox 3.0.0 is in the works for quite some time now. Maybe for too long. Are we in a position to target a release for end of
> year? Maybe by also dropping all open issues which do not have to go into the release but can be done at a later date because
> they add functionality? What's missing, keeping us from doing it?
You are right, it already took too long. We can't wait until it is "perfect".
I've already started to review my tickets and am going to postpone some of the
TODOs on my personal PDFBox list. I hope to come back with a list of TODOs for
3.0 in a couple of days
> The other option would be to drop it entirely (move to sandbox or so) and rebase on the current 2.0 branch as many changes have
> been backported and add the important pieces such as the new parser on top of that.
That would end up in just another 3.0 version but with a lot of additional work
to merge those changes and a lot of chances to introduce new bugs. To sum it up,
IMHO that isn't an option for me.
> I'd like to find a way to get the good parts to our users quickly and moving forward to maybe do smaller, more targeted
> increments.
That's a good idea. We should find a way to have some sort of a release plan, so
that our users including ourselves know what to expect. Maybe something like:
one major per year with a list of planned features. A missing feature won't
necessarily block a major release, bugfix releases as needed.
> Thoughts? Other/better ideas?
First of all thanks for the valuable input and for starting the discussion. We
are already releasing a lot of stuff but we need to find a way to release the
majors more often.
How about moving to git after the 3.0 release? I'm not one of those guys which
are convinced that only a new tool can solve our issues, but it would have some
advantages compared to svn:
* working with feature branches would make it easier to pick/postpone certain
features for a release
* reviews would be possible without committing the source to the trunk first
* some unrelated side effect w.r.t. to the discussed release issue, it may
attract more new users as people are getting used to use git/github instead of
svn + patches.
Andreas
> BR
> Maruan
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org