Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jstl-dev] Do we need a 2.0 branch for maintenance in the future?

Hi,

Ok I've spent some more time on this and my current take is the following:

1) I'm not quite sure why we don't have a 2.0.0 branch currently. I'm not familiar enough with how the release process works to know how this is normally handled.

2) Does it make sense to create a branch that contains all the commits from " Commits on Dec 16, 2020" and before since these all look to make sense to be included in a 2.0.1 if we were to ever create such a maintenance release:   https://github.com/eclipse-ee4j/jstl-api/commits/master ? Then there are only a few spec doc updates that I made (Commits on Aug 3, 2021, and later) that would only remain in master (Tags 3.0.0 eventually).

3) Do we call this new branch 2.0.0 or do we call it 2.0.x?

4) If we do create a 2.0.0/2.0.x branch then going forward any changes to the project that make sense on master and 2.0.0/2.0.x would just need multiple PRs to ensure we keep both branches current when necessary.

I'm going to hold off on delivering anything else until we have some discussion around this and get it straightened out.

Thanks for the feedback in advance!

Regards,

Paul Nicolucci

On Wed, Sep 8, 2021 at 9:51 AM Paul Nicolucci <pnicolucci@xxxxxxxxx> wrote:
Hi,

Looking more closely at the commits in master the commit I pointed to would likely need to be included for 2.0.x but 2.0.x would not include everything previous to that commit we would likely need to look closer at the commits and the tags.

Regards,

Paul Nicolucci

On Wed, Sep 8, 2021 at 9:11 AM Paul Nicolucci <pnicolucci@xxxxxxxxx> wrote:
Hi all,

We currently as far as I can tell don't have a 2.0.0 branch. I believe the 2.0.0 release was done on master but we never created a 2.0.0 branch.

Now that we are moving onto EE10 and Tags 3.0 and there have been a number of things delivered to master I want to ensure we don't cause an issue here.

Can anyone give some feedback as to what we should do? Do we need to move everything from https://github.com/eclipse-ee4j/jstl-api/commits/maste before and including:


to a 2.0.x branch? Or is having our tags enough to create a branch in the future if we need to release a 2.0.1 release?

Thanks,

Paul Nicolucci

Back to the top