from the downstrream perspective, the releases page is great because you
can get XML for it... so if anyone asks for an -announce@ list in the
future -- as i have asked myself in the past -- you can just say "watch the
XML". our semi-automated tooling will be able to keep track of PCRE
releases now, which is great!
...but even better, i see you're tagging the releases. so i can choose
whether to have the tooling `git merge` _or_ take a new tarball... awesome!
i know this move was probably a PITA for you, but this is super helpful for
anyone downstream trying to stay up to date. thanks for this!
just one thing (especially until your new github page climbs up the search
engine rankings): i assume updating pcre.org to point to github rather than
svn (and a sourceforge mirror!) is already on your to-do list? :-)
On Sun, Aug 22, 2021 at 1:32 AM Lucas Trzesniewski via Pcre-dev <
pcre-dev@???> wrote:
> That's great! Now I guess you just need to get used to GitHub, but just to
> clear any doubts: the releases page lets you upload anything you want for a
> given release (which corresponds to a given commit you tag), and you can
> receive messages by mail for any new activity that happens on your
> repository (new messages, issues or PRs) as long as you're watching the
> repository (and you are since it's yours). Maybe you also need to enable
> e-mail notifications in your profile, I'm not sure if they are enabled by
> default. All discussions are public so you don't need a GitHub account to
> read them, though you need one to participate.
>
> Regards,
> Lucas Trzesniewski
>
> Le dim. 22 août 2021 à 09:44, Philip Hazel <philip.hazel@???> a
> écrit :
>
> > Thank you for your comments. In fact, I had just come to the same
> > conclusion myself about splitting the project.
> >
> > GitHub provides a Releases page for each project, where you can create a
> > release associated with a git tag.
> > This page lets you upload your own binaries for each release.
> >
> > I have set up a repo on GitHub (PhilipHazel:pcre2) and managed to import
> > the SVN data, including the commit history. This is where future
> > development will happen (at present, I've just added some holding
> comments
> > into some of the doc files). I needed the good luck you sent - and the
> help
> > of several people when I was being totally clueless, but it is now done.
> >
> > I must learn more about the Releases feature, because I don't think I
> have
> > yet understood what "create release" actually does. If I can build my own
> > tarballs and just upload them, along with the signatures, that would be
> > great. The alternative of using a GitHub site has been pointed out.
> >
> > As for the mailing list, I like having postings just pop up in my inbox
> > rather than having to go to GitHub to look at Discussions, though I will
> > investigate that possibility. People without GitHub accounts need to have
> > access to whatever is set up. I'm now thinking of using a Google Group.
> >
> > Regards,
> > Philip
> >
> >
> --
> ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
>
