[
https://issues.apache.org/jira/browse/JCRVLT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-433:
---
Description: It should validate that package properties' {{acHandling}} is
set to something
Konrad Windszus created JCRVLT-433:
--
Summary: Validator for acHandling
Key: JCRVLT-433
URL: https://issues.apache.org/jira/browse/JCRVLT-433
Project: Jackrabbit FileVault
Issue Type:
On 10/04/2020 15.50, Julian Reschke wrote:
On 10.04.2020 14:31, Ate Douma wrote:
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion ...
On 10/04/2020 15.50, Julian Reschke wrote:
On 10.04.2020 14:31, Ate Douma wrote:
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion ...
On 10.04.2020 14:31, Ate Douma wrote:
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion ...
Anyhow, I agree there might not be much *technical*
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JCR-4552:
---
Comment: was deleted
(was: How/why should 2.18 already go EOL?
That doesn't make sense, v2.16 is indicated
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion ...
Anyhow, I agree there might not be much *technical* reasons to keep
maintaining 2.18,
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion ...
Anyhow, I agree there might not be much *technical* reasons to keep
maintaining 2.18,
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080445#comment-17080445
]
Ate Douma edited comment on JCR-4552 at 4/10/20, 12:07 PM:
---
How/why should 2.18
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080445#comment-17080445
]
Ate Douma commented on JCR-4552:
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't
Huh?
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't you mistaking this with 2.10?
Thanks,
Ate
On 09/04/2020 14.04, Julian Reschke (Jira) wrote:
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hi all,
I'm planning to release 1.22.3 on Tuesday next week.
The list of open issues scheduled for 1.22.3 is empty:
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%1.22.3%20AND%20project%20%3D%20OAK%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
The candidate
12 matches
Mail list logo
