Re: Migration to Git
On 10/05/2019 22:11, Cantor, Scott wrote: On 5/10/19, 8:15 AM, "Boris Kolpackov" wrote: Hm, looking at admin/release-procedure.txt, step 15 in particular, suggest that it's at least not the whole process. There is no step 15, so you're looking at old notes I think. In any case, I suggest that we convert it to Git now and decide what extra steps, if any, are required later. We can, I'm just saying the site is then impossible to update until something else is done. Mentioned briefly a few months back, but we could take the Git migration as an opportunity to convert the old StyleBook XML to Markdown and move the docs to github pages, generated directly from git automatically. This would eliminate Java 6 from the release process, which was increasingly painful. The lack of maintained sources for StyleBook, as well as the lack of availability of OpenJDK6 or Sun/Oracle JDK6, make this problematic on contemporary systems. I would certainly be happy to do the conversion, if there was consensus for doing so. Regards, Roger - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Migration to Git
On 5/10/19, 8:15 AM, "Boris Kolpackov" wrote: > Hm, looking at admin/release-procedure.txt, step 15 in particular, > suggest that it's at least not the whole process. There is no step 15, so you're looking at old notes I think. > In any case, I suggest that we convert it to Git now and decide > what extra steps, if any, are required later. We can, I'm just saying the site is then impossible to update until something else is done. > 2. We may want to use X, X.Y, or X.Y.Z for release-series > branches. We currently call such branches as xerces-X.Y > but if you think about it, this 'xerces-' prefix is > tautological (we are already in the xerces-c repository). My project uses maint-X.Y for that, FWIW. -- Scott - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Migration to Git
Cantor, Scott writes: > On 4/29/19, 10:34 AM, "Boris Kolpackov" wrote: > > > The latter two are direct copies from the web/ and admin/ SVN directories. > > I believe that the web/ repository is actually directly published as > the web site, so there probably is additional work to do to change > how that's happening. I don't know the details of how it works, that > step to commit to svn was as far as I ever made it. Hm, looking at admin/release-procedure.txt, step 15 in particular, suggest that it's at least not the whole process. In any case, I suggest that we convert it to Git now and decide what extra steps, if any, are required later. > > I think we should try to migrate the release tags (the ones > > in the Xerces-C_X_Y_Z form). I also wouldn't mind converting > > them to the now well-established vX.Y.Z form. > > I would cast a mild vote of preference for just using X.Y.Z for > the tag names rather than embellishing them at all with any other > characters, but otherwise +1 I have two reasons to prefer vX.Y.Z over just X.Y.Z: 1. This is the convention that is promoted (and sometimes required, like in Go) in modern languages and package manager. As a result, it is well recognized by tooling (e.g., GitHub will automatically recognize a tag like this as a release). 2. We may want to use X, X.Y, or X.Y.Z for release-series branches. We currently call such branches as xerces-X.Y but if you think about it, this 'xerces-' prefix is tautological (we are already in the xerces-c repository). So, to summarize, vX.Y.Z has potential benefits without any drawbacks that I can think of. So why not? - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Migration to Git
Roger Leigh writes: > > xerces-cxx.git > > xerces-cxx-web.git > > xerces-cxx-admin.git > > Do we need "-cxx" as a suffix here, or would "-c" be better? Yes, good point. Our source distributions are called xerces-c, binary packages seem to also be called like that (e.g., Debian's, libxerces-c). So, yes, let's make it xerces-c.git, etc. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Migration to Git
On 29/04/2019 15:34, Boris Kolpackov wrote: The vote to migrate the Xerces-C++ repository from SVN to Git has passed and I would like to discuss the next step. Sorry for the delay in replying; I've been away on holiday for the last week. As well as through the Xerces-C++ SVN repository to see what we've got: http://svn.apache.org/viewvc/xerces/c/?root=Apache-SVN Based on that I would suggest that we have the following repositories: xerces-cxx.git xerces-cxx-web.git xerces-cxx-admin.git Do we need "-cxx" as a suffix here, or would "-c" be better? xalan-c retained the "-c", and it might be better for continuity to retain the "-c" since this was what xerces-c was traditionally using. For the first repository I propose the following straightforward mapping: heads/master <- trunk heads/xerces-2<- branches/xerces-2 heads/xerces-2.8 <- branches/xerces-2.8 heads/xerces-3.0 <- branches/xerces-3.0 heads/xerces-3.1 <- branches/xerces-3.1 This mapping looks perfect to me. I think we should try to migrate the release tags (the ones in the Xerces-C_X_Y_Z form). I also wouldn't mind converting them to the now well-established vX.Y.Z form. Agreed we should migrate the release tags as a requirement. So long as the tags are present in some form, I have no major preference regarding the naming scheme. Since git supports dots in tag names, I wouldn't be averse to vX.Y.Z, which is a bit more natural. Roger and everyone else, does this sound reasonable/doable? Definitely. Thanks for investigating the possibilities. Kind regards, Roger - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
