Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Branching and maintenance
Scott and all, 

The TCK work being accomplished, such as the detailed-knowledge transfer and all the other TCK-related INFRA-related activities, is pretty amazing. Everyone here is just wonderful, that much care and attention to TCK solutions and consumption +  brainstorming show the light at the end of the tunnel 💪💙

This week,
  1.  The Jakarta EE TCK Playlist is a reality, yeay!  Bravo to everyone joining the TCK calls and enabling the recordings to exist. 
  2. via the git issues, we are working closely with Hudson' (EF) support via the collateral repo issues to export the 9/13 recording, Scott🤗.  
  3. Already 2 TCK recordings are a part of the new playlist. 


On Thu, Nov 19, 2020 at 10:52 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:


On 11/19/20 4:33 AM, Alwin Joseph wrote:
>>
>> Or slightly more consistent
>>
>> Jakarta EE version    Platform TCK version   Branch Name
>> ------------------    --------------------   ------------
>> 8                     8.0.0, 8.0.1, ...      8.0.x
>> 9                     9.0.0, 9.0.1, ...      9.0.x
>> 9.1                   9.1.0, 9.1.1, ...      9.1.x
>
> +1 for ^

I started a wiki page
https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Branch-naming for
recording this decision.

Sort of related to maintenance, in the last community Platform TCK call
on Nov 11 [1], we had a demo of how easy (quick quick) it is to
add/update Github pages and I do plan to spend some time on moving most
wiki content over to that.  I won't move the TCK status page until we
are used to updating github pages instead.

Essentially, it will work like:

1.  The Platform wiki will have a link to
https://eclipse-ee4j.github.io/jakartaee-tck/ for opening the top most
landing page.  Open that to view other content.

2.  The Platform wiki will also have a link to
https://github.com/eclipse-ee4j/jakartaee-tck/tree/gh-pages which allows
anyone to interactively edit a page and either create a pull request or
Platform TCK project committers can save changes directly in the browser.

I'm thinking that we could have different folders that represent the
different EE versions.

Thanks to Amelia for reminding me that we all voted to make this change.
  :-)

Now that we have a live demo [1] that shows how to edit Github pages, I
think that it is a good time to switch from the wiki to Github pages.
IMO, this will also help us in other ways, including improving our
"question + answers" page to all anyone to add a question or content.

If you would like to watch the demo, it is near the end of the video
call linked in [1] (just under `Nov 13` see `Video recording submitted
for processing` link.

Scott

[1] https://t.co/c444XenQ7v?amp=1

Back to the top