The AFP has now forked for the 2015 release as well. The process is as follows:
- new submissions still go into afp-2014 and will be merged/ported manually. If you have a new submission and can hold off for a few weeks to submit a 2015 version instead, that will make things easier for us, but is not required. - the standard AFP repository for developers continues to tracks the standard isabelle development repository. Any changes from now on will not show up in the 2015 release. - the afp-2015 fork tracks the Isabelle release candidates and should not see any major action any more before the release If you have changes to afp-devel that really should go into the 2015 release, please let me know, I can manually port over single commits. Cheers, Gerwin > On 19 Apr 2015, at 9:01 pm, Makarius <makar...@sketis.net> wrote: > > We are now past the fork point for the Isabelle2015 release. One informal and > one formal release candidate have already been published earlier; more will > be coming soon. > > Here is a summary of the status of the Isabelle development process: > > * https://bitbucket.org/isabelle_project/isabelle-release/ is where the > final release preparations happen before roll-out in approx. > 4 weeks (or more). > > The starting point is > > https://bitbucket.org/isabelle_project/isabelle-release/commits/9d8a0a6781c3 > > * http://isabelle.in.tum.de/repos/isabelle is back in post-release mode > right now (changeset b11401808dac). Anything pushed there is for the > next release after Isabelle2015. > > * AFP needs to be understood wrt. isabelle-release within the next few > days, until Gerwin has made a fork of afp-devel vs. afp-2015 and > announced it publicly. > > * mira tests isabelle, not isabelle-release > > * isatest tests isabelle-release > > * isabelle-users is the place to discuss Isabelle2015-RC versions > > * isabelle-dev is the place to discuss ongoing post-release development > > > The isabelle-release repository has no public push access. Any changes that > are relevant for the release need to be sent to me via email (produced by "hg > export" or "hg bundle"). Changesets need to be prepared from a current state > of isabelle-release, not the ongoing post-release development, and applied to > only one of the two repository branches. > > Changes to the actual code base should be limited to really important things. > Changes to documentation can be taken lightly -- we've had relatively few > updates on the manuals this time and there are still a few weeks left to > improve on the text. (I will try to revisit the Isabelle/jEdit and > implementation manuals shortly.) > > During the forked state of the two repositories, big upheaveals on the > isabelle repository should be avoided, so that the isabelle-release branch > can be merged back cleanly after several weeks; but it is better to publish > small changes now than to stockpile them for a long time. > > > Makarius > _______________________________________________ > isabelle-dev mailing list > isabelle-...@in.tum.de > https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments. _______________________________________________ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
