| Re: [servlet-dev] Servlet 5.1 |
So unless there are any objections in the next 24h I will create a 5.0.x branch, and update master to target 5.1.StuartOn Wed, 9 Sep 2020 at 06:12, Mark Thomas <markt@xxxxxxxxxx> wrote:On 07/09/2020 13:55, arjan tijms wrote:
> Hi,
>
> Sounds good! Agree to SameSite as a major driver for the release, and
> let's see if we can pick up a small thing from the backlog.
+1
My time is somewhat limited at the moment but I'll try and do what i can
to help with the low hanging fruit - most likely some of the
clarification questions.
Mark
>
> Kind regards,
> Arjan
>
>
> On Mon, Sep 7, 2020 at 6:06 AM Stuart Douglas <sdouglas@xxxxxxxxxx
> <mailto:sdouglas@xxxxxxxxxx>> wrote:
>
> Hi Everyone,
>
> I would like to propose that we branch the current master into a
> 5.0.x branch to track any additional changes required for the 5.0
> release, and change the current master to target 5.1 so we can start
> to do some actual spec work.
>
> This also brings up the question of what exactly will go into 5.1,
> what is the time frame we are looking at, and what will be our
> planning/release process in general going forward?
>
> I was thinking in terms of planning and release timeframe we adopt
> an informal planning process based around group consensus. After a
> release has been done we send out an email asking for input on what
> should go into the next version, and what the timeframe would be.
> Once we have a general consensus we just make this publically
> available somewhere (github wiki maybe?), and start work. The aim of
> this planning process would be to set expectations based on
> timeframe and features, but it should not generally be used to to
> exclude any other additional work that is ready..
>
> My feeling is that 5.1 should work on a relatively quick release
> cycle, with the main goal being to get the SameSite cookie support,
> with everything else we can include just being a bonus (everything
> else in this case likely being working through the issue backlog and
> attempting to clarify things).
>
> Thoughts?
>
> Stuart
>
>
>
> _______________________________________________
> servlet-dev mailing list
> servlet-dev@xxxxxxxxxxx <mailto:servlet-dev@xxxxxxxxxxx>
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/servlet-dev
>
>
> _______________________________________________
> servlet-dev mailing list
> servlet-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
>
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev