Skip to content

Please roll 'master' to 1.14.11 #5808

Description

@eddelbuettel

With the repo at @Head ie

$ git ls | head -1
* 3e590f84 - (HEAD -> master, parentrepo/master, origin/master, origin/HEAD) workaround pkgdown bug by copy rather link to avoid dead links (#5804) (2 days ago) <Jan Gorecki>
$ 

we get

> library(data.table)
data.table 1.14.9 IN DEVELOPMENT built 2023-12-08 14:36:41 UTC using 6 threads (see ?getDTthreads).  Latest news: r-datatable.com
> 

which means (thanks to the new release !!) that as soon as I run update.packages() I loose DT() and many new friends 😀

Activity

  1. self-assigned this
    on Dec 8, 2023
  2. jangorecki commented on Dec 8, 2023

    @jangorecki
    Member

    resolved in git, running release pipeline so our R repository will be refreshed as well

  3. jangorecki commented on Dec 8, 2023

    @jangorecki
    Member

    note that problem you are reporting here will not be repeating, as we will use 1.14.99 from now on.

  4. jangorecki commented on Dec 8, 2023

    @jangorecki
    Member

    published

    data.table::update_dev_pkg()
    #R data.table package has been updated to 9225c169042a6032c7bb21ffa4ee74b6219934db (1.14.99)
    data.table::update_dev_pkg()
    #R data.table package is up-to-date at 9225c169042a6032c7bb21ffa4ee74b6219934db (1.14.99)
  5. eddelbuettel commented on Dec 8, 2023

    @eddelbuettel
    ContributorAuthor

    Ah yes even better. I like that .99 'ahead' of all possible stable release patch updates.

    A beauty:

    > library(data.table)
    data.table 1.14.99 IN DEVELOPMENT built 2023-12-08 15:21:13 UTC using 6 threads (see ?getDTthreads).  Latest news: r-datatable.com
    > 
  6. jangorecki commented on Dec 8, 2023

    @jangorecki
    Member

    Previous versioning system was pretty good, but when we started to have more frequent patch releases, rather than actual releases, it started to be a bit unpractical, like upgrading documentation in master about new features in 1.14.2, to 1.14.4, then to 1.14.6 and so on. Having this distinction (release/patch) resolves that issue.

  7. added this to the 1.15.0 milestone on Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions