[Bioc-devel] CTCF annotation package's vignette not updating

[Mikhail Dozmorov]

It must be very simple, but I'm still unable to trigger the build -
confused by version numbering. CTCF had version 0.99.5 in BioC 3.15,
https://bioconductor.org/packages/3.15/data/annotation/html/CTCF.html.
According to guidelines
https://contributions.bioconductor.org/versionnum.html, its version should
be 1.0.0 in the next release, 3.16. But it shows 0.99.9,
https://bioconductor.org/packages/release/data/annotation/html/CTCF.html.
Incrementing "the z" part has no effect, even after waiting for Wednesday's
report update. Other attempts like setting the version to 1.0.0 fail with
"remote: Error: Illegal version bump" when pushing to the "RELEASE_3_16"
branch. Which version number should I set to trigger the build?

Thanks,
Mikhail

On Mon, Oct 31, 2022 at 7:22 AM Kern, Lori <Lori.Shepherd using roswellpark.org>
wrote:

> Please remember that once accepted the packages are only built and
> propagated on a particular schedule and not on demand.  Annotation packages
> that are in git are updated once a week. The schedule of the builds of
> different packages can be found:
>
> http://bioconductor.org/checkResults/
>
> Vince is also correct.  You will still be able to update 3.16 but after
> tomorrow it would have to be done on the RELEASE_3_16 branch and master
> (3.17) branch.
>
> Cheers,
>
> Lori Shepherd - Kern
>
> Bioconductor Core Team
>
> Roswell Park Comprehensive Cancer Center
>
> Department of Biostatistics & Bioinformatics
>
> Elm & Carlton Streets
>
> Buffalo, New York 14263
> ------------------------------
> *From:* Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of
> Vincent Carey <stvjc using channing.harvard.edu>
> *Sent:* Sunday, October 30, 2022 9:13 PM
> *To:* Mikhail Dozmorov <mikhail.dozmorov using gmail.com>
> *Cc:* bioc-devel <bioc-devel using r-project.org>
> *Subject:* Re: [Bioc-devel] CTCF annotation package's vignette not
> updating
>
> Maybe I am wrong Mikhail but I think you have about 6 months to enhance the
> documentation of your package in 3.16.
>
> On Sun, Oct 30, 2022 at 7:54 PM Mikhail Dozmorov <
> mikhail.dozmorov using gmail.com>
> wrote:
>
> > Hello,
> > I'm trying to update documentation for the
> >
> https://secure-web.cisco.com/1p7VBteo2CRqcBZV-zNncaSH__4Q_rsUE7Tn2Jkq-yeqpCers_iPa5A4EytZziK_btn-kss-FCaAzY0CSPldbZubwnGgPQgU04BMpStqnTNklfw-_ddCnIOgtYwUAN6qdYRlypSYHUwSyBtC6gWj1hXZNcs55UpZ06-GtOnl0Lj9HrD_1VTmnUwEd5Q4iw4n-1jo6Z_u2Mfz-XXVjbbdRDbyVRbcybt2rJuElNK_pBimikAbulhNN-cB7Qi-FU22CPGSd2aflxOQ9NbzZ8zsTw5vmru5HNLzAizCcaBesTCiYcIgbNaEhmmQR4MHK060c/https%3A%2F%2Fbioconductor.org%2Fpackages%2Fdevel%2Fdata%2Fannotation%2Fhtml%2FCTCF.html
> > package so it can be shown in the 3.16 release. Pushed to bioc master
> > twice, with version bump. But the build is not triggered
> >
> https://secure-web.cisco.com/1sBV614NyVTESrurr0us0eF9hlgOxwbnKgjdZcAZHH3VbS8lsHGGEBUiZTaHOxgv8Fv2pVah4r-j1Roi7k0KRBrVF6DeQMeM43DlY5Ua4ovtWWhIWA6iy2CLp7SCH2VMVeL2h_jHVb8hOvDVA37A4Uz7QjD_tb7UWK5L4pemedIxxWDpoCQzaueRv4O-fjjz2gB4eqI8IrXNibaWEXrT0F0K7-QcTFZLpSsVP1OFHSCZKQw1rIA2vOjMSxZqEZlftwz_3SW507U8Z6rxaklHUWNOrX_SQK8F4x20XwQctLWVDW9RO2o2_pHumKAErweRB/https%3A%2F%2Fbioconductor.org%2FcheckResults%2F3.16%2Fdata-annotation-LATEST%2FCTCF%2F
> > It
> > may be due to the 3.16 release schedule or something very simple, but I'm
> > trying to meet the October 31 1:30 pm EST deadline and running out of
> ideas
> > what to do to update the package.
> > Thanks,
> > Mikhail
> >
> >         [[alternative HTML version deleted]]
> >
> > _______________________________________________
> > Bioc-devel using r-project.org mailing list
> >
> https://secure-web.cisco.com/1mueWKL3AMBjbkUJbDAqpWGLMWD-5Jsb_WUCt5eZZyzaY9qAg0iypSVjgckFNG0n3vlDSi5njIeMnl3aDgga-H4koSxK-E0Om-GewGInXGSWP8lQROFryCUI29Rds3DBhKrKKIyGrWI_3ZIHJynixzUzhU1pMpa3Kz1NIcEoCMvGXPfHCmBCCQa2A011_wb7rqUXGvevN9fYOBQBj6ILBcyBWfDAw2MA6GG9UOVa8tkotsOI4wWiZ8zkNj5lTx16Qa0KFb4JI1dvPyjye-WtMQBXCfFAOSKEGkHVjZJYJN3WP36NiiuDr7A0jY9JYfu5R/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel
> >
>
> --
> The information in this e-mail is intended only for th...{{dropped:25}}